I’m a Christian and software engineer; I create random graphics projects and websites. Feel free to ask me for help with programming, or about my faith!

  • 4 Posts
  • 53 Comments
Joined 3 years ago
Aquileo | cake
Cake day: June 12th, 2023

Aquileo | help-circle






  • For anyone who is still confused about what causes this: Firefox launches copies of itself when creating new website instances (usually when loading a website that has not already been loaded). Because of this, if it is updated in the background (through any means; I usually see this after a manual system update), Firefox has to restart when you try and load a new site because it cannot create any compatible copies of itself, since the old version is the one that is still running and the copies would use the new (updated) version.

    The solution is to only update when Firefox is closed, or restart it when it asks.









  • KiranWells@pawb.socialtoLinux@lemmy.ml*Permanently Deleted*
    Aquileo | link
    Aquileo | fedilink
    Aquileo | arrow-up
    10
    ·
    3 years ago

    My computer was taking too long to start up, which I interpreted as failing to boot, but in hindsight was probably just my hard drive being slow. So, I booted into recovery mode, and ran an update. At one point, apt said “there are unnecessary packages” and would I like to remove them? I figured that apt knew better than I did (after all, maybe a package dropped a dependency), so I said yes.

    It was after I noticed the very large number of packages that I suspected I messed up. Turns out, apt uninstalled the entire desktop environment, and network manager, so I had to boot into a USB drive with Network Manager installed, chroot into my main drive, and reinstall plasma. As a bonus, I think I missed the main group for the plasma desktop and only installed only most of it, so some of my extensions just didn’t work anymore.