| 2022-04-26 20:06:43 |
Aaron Rainbolt |
bug |
|
|
added bug |
| 2022-04-26 20:08:39 |
Aaron Rainbolt |
tags |
|
jammy snapd |
|
| 2022-04-26 20:43:10 |
Aaron Rainbolt |
description |
It has been reported on the Lubuntu Discourse forum that there are strange Snap errors that occur when booting Lubuntu 22.04 on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to dump the RAM and upload it, but I could probably reproduce the issue in a VM with 1 GB of RAM and upload that VM's RAM for debugging. |
It has been reported on the Lubuntu Discourse forum that there are strange Snap errors that occur when booting Lubuntu 22.04 on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to snapshot the VM and upload the snapshot file, but I could probably reproduce the issue in a VM with 1 GB of RAM, snapshot that, and then upload it.
It has been reported on the Lubuntu Discourse forum that there are strange Snap errors that occur when booting Lubuntu 22.04 on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to snapshot the VM and upload the snapshot file, but I could probably reproduce the issue in a VM with 1 GB of RAM, snapshot that, and then upload it. |
|
| 2022-04-26 20:45:04 |
Aaron Rainbolt |
description |
It has been reported on the Lubuntu Discourse forum that there are strange Snap errors that occur when booting Lubuntu 22.04 on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to snapshot the VM and upload the snapshot file, but I could probably reproduce the issue in a VM with 1 GB of RAM, snapshot that, and then upload it.
It has been reported on the Lubuntu Discourse forum that there are strange Snap errors that occur when booting Lubuntu 22.04 on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to snapshot the VM and upload the snapshot file, but I could probably reproduce the issue in a VM with 1 GB of RAM, snapshot that, and then upload it. |
It has been reported on the Lubuntu Discourse forum that there are strange Snap errors that occur when booting Lubuntu 22.04 on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to snapshot the VM and upload the snapshot file, but I could probably reproduce the issue in a VM with 1 GB of RAM, snapshot that, and then upload it. |
|
| 2022-04-26 23:31:03 |
Aaron Rainbolt |
summary |
snapd fails to start or behaves strangely on slow systems |
Live session, snapd fails to start or behaves strangely on slow systems |
|
| 2022-04-26 23:31:55 |
Aaron Rainbolt |
description |
It has been reported on the Lubuntu Discourse forum that there are strange Snap errors that occur when booting Lubuntu 22.04 on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to snapshot the VM and upload the snapshot file, but I could probably reproduce the issue in a VM with 1 GB of RAM, snapshot that, and then upload it. |
It has been reported on the Lubuntu Discourse forum that, when booting into a live session using the Lubuntu 22.04 ISO, there are strange Snap errors that occur on certain hardware. This usually manifests itself as a "Failed to start Snap daemon" error, and since Firefox has been distributed as a snap in Ubuntu 22.04, this results in an inability to use Firefox within the live session. (The full thread is here: https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246)
From my own testing, I have found that booting both Lubuntu 22.04 and Ubuntu 22.04 ISOs in very slow VMs (QEMU with no KVM) usually results in snapd failures (and Firefox doesn't load), while booting the same ISOs in fast VMs (virt-manager, QEMU/KVM) reveals no problems - no snapd errors, Firefox launches just fine.
Steps to reproduce:
1: Ensure that qemu-system-x86_64 is installed, and that you have a Lubuntu 22.04 ISO available.
2: In a terminal, cd to the directory containing the Lubuntu 22.04 ISO.
3: Run the following command: "qemu-system-x86_64 -cpu kvm64 -m 4G ./lubuntu-22.04-desktop-amd64.iso"
4: Select "Try or Install Lubuntu", and wait for the VM to boot. It will take a long time, since KVM is purposefully left off.
5: Once the live session has booted, press Ctrl+Alt+T to bring up a terminal.
6: Type "firefox" and press Enter. It is very likely that the command will fail, though the particular error you get may vary.
7: Type "nano /var/log/syslog" and press Enter. Search for "Failed to start Snap". You will almost certainly find the "Failed to start Snap daemon" error.
Expected result: Firefox should launch in step 6, no Snap errors should be present in step 7.
Actual result: Firefox fails to launch in step 6, Snap errors are found in step 7.
Extra info:
This bug appears to be hardware-dependent. This is my setup:
HP Z220 SFF Workstation
Intel Xeon processor E3-1225v2
16 GB of A-TECH RAM (DDR3, 1600MHz, no ECC)
Lubuntu 22.04 ISO is located on a 12TB WD Easystore USB drive. ISO checks as good using sha256sum.
Host OS is Ubuntu Studio 21.10.
When booting the Lubuntu 22.04 ISO in virt-manager (QEMU/KVM), everything works as expected - Firefox launches, no Snap errors are found in the log. **This bug is not reproducible for me on a fast VM.**
This problem is **not** unique to Lubuntu - I have also booted Ubuntu 22.04 in pure QEMU (no KVM), and found similar errors. In the Ubuntu 22.04 test, the window that allows me to select "Try Ubuntu" never appears - instead, an error message showed up saying that Ubuntu had experienced an internal error. I was able to switch to a TTY, and check /var/log/syslog - there were three "Failed to start Snap daemon" errors in the log.
Booting up both Lubuntu 22.04 and Ubuntu 22.04 images in virt-manager (QEMU/KVM) with slow graphics (VGA instead of QXL) still allowed Firefox to launch without issues.
The particular error you get in step 6 may vary. In one test, I was told that Firefox was not installed. In another test, I received this error message:
error: error running snapctl: cannot invoke snapctl operation commands (here "is-connected") from outside of a snap
ERROR: not connected to the gnome-3-38-2004 content interface.
Both of these tests were performed using Lubuntu 22.04 in pure QEMU (no KVM).
I have not yet tested either Lubuntu 22.04 or Ubuntu 22.04 on bare metal, but on the Lubuntu Discourse thread linked above, multiple users experienced problems on bare metal similar to the ones I'm experiencing, while other users were not able to reproduce the issues on bare metal. I intend to test these images on a relatively slow Chromebook (Dell Chromebook 3120) to see if I can reproduce the issue there.
I have the QEMU instance from one of my failed tests still open and paused, so if you need info from the logs from a known-bad boot, I have them. My Internet connection is metered, and I gave the failed test VM 4 GB of RAM, so I don't want to snapshot the VM and upload the snapshot file, but I could probably reproduce the issue in a VM with 1 GB of RAM, snapshot that, and then upload it. |
|
