ubuntu 22.04 fails starting wayland after update, left in tty1 (not but close to mtd device must be supplied (device name is empty))

Bug #1990723 reported by Mario
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Ubuntu 22.04 desktop fails loading graphical engine after a daily update on Sept 22 2022.

I am left on tty1. The "DISPLAY" environment variable seems not to be specified, I could guess the whole gtk/wayland engine fails in loading.
Running on i386, dell latitude e7450 with ssd and ubuntu22.04.1, kernel 5.15.0-48 generic, x86.

Similar to these:
https://ubuntuforums.org/showthread.php?t=2476796
https://www.reddit.com/r/Ubuntu/comments/wkuw63/cant_boot_mtd_device_must_be_supplied/

Apparently related to the bug reported here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622 "mtd device must be supplied (device name is empty)" but turns out they are not related.
It's not an issue with systemd: I followed the bug report and with the version of systemd 249-11-0ubuntu3.6 the message disappeared when booting.

Seems to me a major failure in loading the graphical engine.

*** UPDATE ***
It's probably not a bug, rather a failure on the human side (aka myself).

Solution: the whole gdm3 package was missing. A simple "sudo apt install gdm3" given while on tty1 fixed everything.

My best guess is that I closed the lid of my laptop exactly while a "sudo upgrade" was running (probably the one via graphical interface that runs in the background after you clicked on it).
The new package was first downloaded, then the old one removed, and at this very point I probably closed the lid of my laptop, leaving the OS without a graphical interface.

Take home message: do not suspend your pc while upgrading. Actually, now that the graphical interface is becoming more and more present, these kind of mistakes may pop out more and more.

Revision history for this message
Mario (mmariorrossi) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1990723/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Mario (mmariorrossi) wrote (last edit ):

It was not a bug, but a human mistake, see above.
I'll try to close it and mark it as fixed.

Revision history for this message
Mario (mmariorrossi) wrote :

I marked it like invalid.

description: updated
Changed in ubuntu:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.