Page MenuHomeSolus

Last update broke display manager
Closed, ResolvedPublic

Description

Hi

I'm using Solus with gnome-shell and the 3.24 update broke my display manager. This is my 'pro' laptop so i revert to gnome 3.22 and last known working state.
I was using gnome with X11 and from what I see it now tries to use wayland as default.

avril 18 10:08:23 jtjnrc2 /usr/libexec/gdm-wayland-session[826]: Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
avril 18 10:08:23 jtjnrc2 /usr/libexec/gdm-wayland-session[826]: Activating service name='org.freedesktop.systemd1'
avril 18 10:08:23 jtjnrc2 /usr/libexec/gdm-wayland-session[826]: Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
avril 18 10:08:24 jtjnrc2 gnome-shell[852]: Can't initialize KMS backend: could not find drm kms device
avril 18 10:08:24 jtjnrc2 gnome-session-binary[829]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
avril 18 10:08:24 jtjnrc2 gnome-session-binary[829]: Unrecoverable failure in required component org.gnome.Shell.desktop
avril 18 10:08:24 jtjnrc2 gnome-session[829]: gnome-session-binary[829]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
avril 18 10:08:24 jtjnrc2 gdm[761]: GdmDisplay: display lasted 0,724785 seconds

Also here is a lspci output

00:00.0 Host bridge: Intel Corporation Device 1904 (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Device 1916 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Device 1903 (rev 08)
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)
00:16.3 Serial controller: Intel Corporation Device 9d3d (rev 21)
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d14 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Device 9d1a (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d48 (rev 21)
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)
00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Device 156f (rev 21)
01:00.0 Network controller: Intel Corporation Device 24f3 (rev 3a)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 525a (rev 01)

I can't really dig through the error right now so if anyone as an idea. :)

Event Timeline

avril 18 10:08:24 jtjnrc2 gnome-shell[852]: Can't initialize KMS backend: could not find drm kms device

Nothing to do with the display manager - this is the error. What graphics do you have?

Chiming in since I'm also experiencing this issue. I'm using nothing but integrated Intel graphics, no dedicated GPU whatsoever. Which is weird because all other mentions of this error online mention using multiple graphics solutions.

Please confirm your installed version of GDM

gdm, version: 3.20.1, release: 20

Nothing to do with the display manager - this is the error. What graphics do you have?

Intel HD Graphics 520 (Skylake GT2) with i5 6300

Agreed, this is not the display manager fault, this is why I gave a lspci output, but it seems to be triggered by a call gdm-x-wayland is doing.
Still didn't try to manually relaunch with gdm-x-session as this was like: ' Oh, your not MS computer doesn't work, maybe it's time to have refactor this thing"
Anyways, be able to test more things in a few hours.

Can't confirm gdm version cuz I rollback but gdm, version : 3.20.1, release : 20 proposed.

OK so force it to login as GNOME on Xorg session

sd added a subscriber: sd.Apr 18 2017, 7:30 PM

I'm running into this issue as well with an Intel HD Graphics 620 (Kabylake GT2) laptop. It used to work fine for me but this latest update seems to have broken it.

Xorg works, but I hope to use wayland since it handles my hidpi display better (particularly when attaching a non-hidpi external display).

I was wanting to try out Wayland to see if it was stable enough for use when I ran into this issue. I can get XWayland running in a nested instance of gnome-shell but I haven't been able to work around this issue yet.

When forcing to use Xorg session , Gnome manage to launch properly. The error is still there when it tries to launch wayland and failed, then x-session.
I only have a small bug when the laptop is docked and the display forward to a dual screen setup. Only the login screen background appears.

JoshStrobl closed this task as Resolved.Aug 5 2017, 2:11 AM
JoshStrobl claimed this task.
JoshStrobl added a subscriber: JoshStrobl.

Marking as resolved as we've since dropped Wayland support until it is more mature.