That sounds like you did everything right (I’ve not used nero in over a decade so I have to assume it’s still okay)
You’ll need to file a bug report for us to explore further, to do this you should
boot your Lubuntu 22.04 ISO on your hardware where this is occurring, retry to create the issue and if it happens, then do the following
open a terminal (Ctrl+Alt+Tor via menu) and type
ubuntu-bug snapd
Follow the prompts (logging into launchpad if you’re not logged in) as this will provide us & upstream Ubuntu with more details that we can check out. It might require us to write the ISO to DVD media & confirm, if it’s a timing issue (my suspicion but only one possible cause) it’d need to be explore, but the answer maybe we had a note on the next release media (22.04.1) that firefox will not run in live sessions when booted from DVD media, but then again they may decide something different (increasing wait time or other), but it could show something else to where my mind has gone as to possible causes - we’ll have to wait and see.
Please post the bug report URL here (I’ll likely see it when posted, but they can be missed)
ps: I actually wrote this message last night (my local time), but I was hoping for an answer on what package to file bug report against as we cannot use firefox… I didn’t get a response to my query, so I’ve used snapd… Note: the package maybe changed after filing if I’ve given a wrong package
We want details from your logs, so unless you’re going to page through system logs slowly (which would take hours of filming) we don’t have sufficient detail to confirm what you’ve already provided.
The alternative is for someone else to re-create the issue, then they file the bug report so we can explore their filed report.
Details are needed of your hardware, firmware, components, & boot messages etc… details of your installation media & internal validation on running system where issue occurs… all of which are obtained via the ubuntu-bug command to file a bug report, OR if the bug is filed on a browser using this link THEN later the command apport-collect (with bug ID from the prior bug created) from terminal when it’s in the position which I described in my prior comment.
The ubuntu-bug does everything, where as the apport-collect is used to get the required details from a browser reported bug report; but it’s the same process. I think the single step ubuntu-bug is easier.
I understand. You need a detailed bug report as to why the “Failed Snap Daemon” shows up on the screen. I was assuming a video of the error showing up on my PC screen would be good enough.
I don’t like how complicated it is to do things in Linux. That bug reporting system looks too complicated to me to use regarding my level of software skills. Maybe I will try it out or not. Sorry.
You normally would enter ubuntu-bug snapd in a terminal; which will start some processes off, that will gather detail then request permission to open the browser so you can login & the gathered details can then be uploaded. The largest hassle here to me, is the creation of an account on launchpad.
The browser however is firefox , which isn’t running for you… so you’ll be forced to use the file-online (that can be done on another box which is it’s major benefit) then run the apport-collect on your actual box… That would still require you to give permission so upload can occur; which is done via firefox so a problem here too.
Whilst I don’t consider the command ubuntu-bug or apport-collect difficult, you’ll have issues currently given your issue is with firefox, and that won’t be very user-friendly (the tools jumping to firefox was intended to make it easier for end-users, but given that’s the current issue - its making it harder here!)…
If I get the chance, I’ll write Lubuntu 22.04 LTS to a DVD & give it a try; then maybe I can be the “someone else” in my prior message.
Thanks for your issue report, and replies to my questions.
I wrote the Lubuntu 22.04 LTS image to a DVDR. Booted it up on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
and beyond taking ages to boot (which I’d remembered) it being noisy (this box is usually only tested with thumb-drives), it eventually booted. On opening firefox there is the delay which occurs now on first run due to snap package (the snap image on media is squashfs which needs to be unompressed*) then I get the firefox window and a “Welcome to Firefox”.
To look at what your actual issue, at least to me, a bug report is needed so we have more specific details we can examine. Presently from my just-run test, the likely issue to me is back to media write (mostly as I use thumb-drives which aren’t the most reliable media being made to cost & failures occur)
Yes it’s slow to load; I didn’t time it; but that is expected as it’s assumed these days thumb-drive media is used; and the only checks performed for those still using DVDs is that it boots, runs and can install - even if slow.
I could not replicate that issue
firefox is present when ISO is written to thumb-drive, or DVDR and booted.
I did get a reply to this… It was after midnight my local time and I just turned the box off without noticing it’d come…
<ogra> the apport fix is already pending to point you to the same url as "snap info firefox" when calling ubuntu-bug
<ogra> also try starting it from a terminal, that might give some hints about potential issues
The last line contains the best clue; try running firefox from terminal and it may provide clues that allow us to help you. It may also provide details you can post into this discourse so we can help you too.
Sorry, I should have thought of that earlier; alas didn’t
Thanks for the hard work. Sorry I couldn’t be much help.
FWIW, I quit using USB thumb drives for making Linux boot drives years ago. More on this below:
I’ve been trying out Linux for about 8 years. The distros I tried would sometimes bug up or I run out of memory in the Live boot space. This would cause the USB to never stop blinking it’s activity LED. I had no choice but to press the reset button on the PC or turn the PC off by holding down the power button. I was afraid I would damage my USB by doing this. (Just like how you would yank out a USB drive while it’s still transferring files) So to prevent the possibility of damage to my hardware, I switched to using only burnt DVDs.
BTW, I forgot to mention, I used safe graphics mode too when I booted the new Lubuntu DVD.
I still use a CRT monitor and a number of Linux distros don’t like it, so I turn on safe graphics mode on the distros I test. However, I am impressed that the latest Linux releases I tried yesterday are actually making it to the Live boot desktop! I tried the newest PCLinuxOS, Xubuntu as well as Lubuntu. All three successfully made it.
That’s quite surprising seeing out of the selection of old Ubuntu 20.04 LTS based distros, and Arch and Debian distros I tried last year, Only Lubuntu 20.04 made it to the Live boot desktop. Thank you Linux community for improving hardware support!
P.S. I am using Firefox on the new PCLinuxOS to type this. It’s working well, but… when I tested the new Xubuntu, it’s web browser is broken, but there is no error message beforehand. It only gives me an error message when I click the icon and it won’t launch the browser. Maybe it’s related to the snap daemon failure on Lubuntu…
I’ve booted the DVDR I created in post 11 of this thread on the same old box, but this time using safe graphics mode
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
and firefox is running for me (both when started via qterminal or menu)
I actually booted the box twice with one session getting a black screen. On the black screen boot I just switched to text terminal, killed Xorg & the machine sent me back to sddm or the greeter, I logged in as “lubuntu” and it worked fine from then on. I checked for squashfs (media errors) and there were none (alas I do see errors on access cdrom/sr0), but this old video card has known issues with nouveau on recent kernels (esp. with GNOME, KDE, recently MATE…), so I’d need to check for issues on other boxes/video cards before I was willing to treat it as a bug (and need a run without I/O errors on dev sr0)
@computerdude92 Are you sure that your ISO is good? This sounds like something a damaged download could easily cause.
To check your ISO from Linux using a SHA256 checksum:
Open the folder that your Lubuntu 22.04 image is located in.
Open a terminal window within this folder. You can usually do this by right-clicking in a blank area of the folder, and clicking “Open Terminal” or something. The option might also be hiding underneath a “Tools” menu or something along those lines.
Once the terminal is open, type this command:
sha256sum ./lubuntu-22.04-desktop-amd64.iso
This command will generate a very long string that ought to look exactly like this:
Carefully compare the string generated by the above command with the string posted here. If so much as one character is off, your ISO is damaged. If this is the case, delete the ISO, download it again, and check it using this procedure. Once you have a good ISO, you can burn a new DVD and try again.
Also make sure to use a “Verify written data” feature (or whatever equivalent your DVD burning software provides) to ensure that the data on your DVD isn’t corrupted - a wonky DVD will cause just as bad of problems as a bad ISO download (maybe even worse). It also may be a good idea to close all open programs before writing the DVD, and maybe even set the writing speed to 1x - this will make the writing process take time and eternity, but it will also make the process more reliable.
If even a good DVD with a good ISO isn’t working, you may want to try using a USB drive. It might be possible that your hardware’s DVD drive has some incompatibility that’s making things go haywire, and using a USB drive may make things work. I seriously doubt this is the problem, but I’ve had weirder things happen, so it’s worth a shot if all else fails.
Okay I said I’d drag a desktop out and run my bootable DVD of Lubuntu 22.04 and here’s the results.
Desktop is all Intel inside.
Always have excellent results with all Intel inside desktops.
Okay DVD install kinda slow but not painful.
Start to finish 20 minutes to 30 minutes.
The errors.
Failed to start Dispatcher daemon for systemd-networkd.
Failed to start Snap Daemon.
Failed to start Disk Manager.
Failed to start Snap Daemon.
Okay no lockups or blank screen and the cursor was showing activity so let it keep running.
I let the installer do the install after I entered the needed name rank and serial number.
Install completed after a system reboot I updated and rebooted and all is working well.
If you download as a torrent, it has built in checks for file integrity. You can and should still verify it, but it should be exactly the same as the source file.
Ah, yes, I forgot about that. I don’t use torrents since I’ve seen a lot of stories about how ISPs have gotten mad at people for using them since they consider the peer-to-peer clients to be servers. I used to use torrents for downloading Linux variants all the time, and they were awesome.
I’m confused as to what the cause may be since I’ve actually gotten 2 successful working installs on 2 different desktops.
One of them AMD and Nvidia graphics which have always been somewhat problematic from my experience.
The other desktop all Intel inside and have never been problematic with Linux from my experience.
It’s possible that it could be bad iso downloads but 4 of them.
I find it hard to believe that 4 iso downloads could be bad but I guess it’s possible although highly unlikely.
I’ll log here for potential historic debugging purposes. I did get 3 of these messages (I think it was last three; missing the thermal) though order wasn’t identical in one boot on my hp dc7700. If I recall correctly it was the boot where I found dev sr0 errors in the log, and the fact that I could see errors that may explain issues I tended to discount issues on that boot.
I smiled at this; on my dc7700 it sure seemed painful to me… but much of that was the noise; which is why I usually used different boxes for DVD testing (dc7900, d755, d780.)… the sound reminding me of the calamaresfloppy issue but I had no floppy I could eject to instantly silence the box
I rarely find I have bad downloads… but it’s possible. I’ll provide the Ubuntu link for checking your ISO, but I’d just perform what’s found in the Lubuntu manual as it’s easier.
I do find however the write to media fails too often (about 5-8% of the time using sandisk thumb-drives for me, higher on other brands), as thumb-drives/media are made to cost or consumable items. It’s why I always scan logs looking for clues as to causes (squashfs errors, media validation completing on recent release, IO errors etc) using a text terminal.
