![]() ![]() Nowadays most users have bad A$$ computers such as your fleet of computers. In the olden days users used Lubuntu because of the low system hardware requirements to compensate for using low powered computers. I think has hit the nail on the head with the timing issue. My desktops are old as in 2010 / 2008 dual core processors with 4.0 GB ddr2 and ddr3 memory and mechanical hard your computers appear to be new with i7 processors and 32 Gb of memory and most likely SSDs which is why you have no errors. Unfortunately, my Internet is metered, and I gave the VM 4 GB of RAM, so I probably can’t upload a RAM dump, but I can try to replicate the issue again with a 1 GB RAM VM, and if things go haywire, I can probably dump the RAM and upload it. I did leave the VM running for quite a while after getting it to glitch, so hopefully I’ve not already messed it up. I’ve left the QEMU instance from the third test open and paused, so if you want to peek into the guts of a VM with a wonky Snap system and an unlaunchable Firefox, now’s your chance. (I originally said to use PCManFM-QT here, but since this VM is running using pure emulation, it’s sloooooow, and using nano is quicker.) You may be told that Firefox is not installed, or it might give you an error. Hit Ctrl+Alt+T to get a terminal, and type firefox. Once you get to the desktop, click inside the VM window, navigate to the Application Menu, and hover over “Internet”. It will take quite a while, since KVM acceleration is purposefully left off here.Ĥ. ISO checks as good using sha256sum.ġ: Open a terminal, and cd your way to the ISO location. Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. I thought to look at /var/log/syslog on this third test, and sure enough, Snap failed to start at some point in the boot process.ġ6 GB of A-TECH RAM (DDR3, 1600MHz, no ECC) Trying to run it in a terminal gave me the following error:Įrror: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snapĮRROR: not connected to the gnome-3-38-2004 content interface. The next test, Firefox appeared, but I didn’t have the presence of mind to try and launch it… The third test, Firefox appeared, but this time I actually tried and launch it… and it didn’t launch. Attempting to run it in the terminal resulted in a notice that Firefox wasn’t installed. OK, so the behavior here is very, very weird - on one test, Firefox was just gone, just like the original post described. ![]() I REPRODUCED THE BUG IN A VM!!! Looks like it is indeed a timing issue, just like said. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |