Even after the updates of today (with the new kernel and the gnome-shell crash fix) the boot splash is getting stuck most of the time (certainly 3 out of 4 tries).
Only switching to the nvidia 340 blob fixes that (then it boots reliably, not showing Plymouth at all).
I don't think that it is a Plymouth bug, but GDM crashing when trying to bring up Wayland.
Since it crashes that early I don't think that it is related to mutter or gnome-shell at all. Or does GDM use mutter these days?
[S]Does apport leave a crash log in /var/crash/ with Ubuntu freezing or crashing that early?[/S] EDIT: Nope, no crash log in /var/crash/ at all :(
Even after the updates of today (with the new kernel and the gnome-shell crash fix) the boot splash is getting stuck most of the time (certainly 3 out of 4 tries).
Only switching to the nvidia 340 blob fixes that (then it boots reliably, not showing Plymouth at all).
I don't think that it is a Plymouth bug, but GDM crashing when trying to bring up Wayland.
Since it crashes that early I don't think that it is related to mutter or gnome-shell at all. Or does GDM use mutter these days?
[S]Does apport leave a crash log in /var/crash/ with Ubuntu freezing or crashing that early?[/S] EDIT: Nope, no crash log in /var/crash/ at all :(
A regression in X? In Mesa?