02-07-2020, 01:42 AM
(02-06-2020, 02:38 AM)danielt Wrote: I saw some of the comments about broken graphics.
I haven't seen these before so I fired up a fresh install on an SD card and that worked just fine.
However when I rebooted back into my daily driver and the display manager (gdm) wouldn't start. Once it had crashed enough times for systemd to give up restarting it I was able to get over to a console and run an apt upgrade. The package list didn't look very promising (well... a new libreoffice is nice but I didn't expect that to fix anything). However after a reboot all seems to be well again.
Does the problem reproduce reliably. In other words does anyone think the upgrade has fixed it or do you think I spot it again in a couple of days time?
Not sure if you're referring to the issues with X failures at startup or perhaps something else like hardware acceleration.
As far as the X startup issues go, it seems I can reliably reproduce them with clean installs from sha aa7b393. It appears to only appear when certain desktops are selected in tasksel. Gnome runs fine. LXDE, XFCE, Cinnamon and Mate all induce X crashes.
Interestingly, KDE Plasma and LXQT don't crash, but don't start up either: instead we see a black screen with a movable mouse cursor.
In all crashing X cases, the log reports a seg fault with OsLookupColor+0x188 as the only stack frame, with the message
"unw_get_proc_info failed: no unwind info found [-10]".
This trace is absent from the KDE Plasma and LXQT cases, which instead mention an error line reading
"Failed to open authorization file "/var/run/sddm/{<some-guid>}": No such file or directory"
..where <some-guid> is an actual guid, though the curly braces appear literally.