[opensuse-factory] TW 20180314 - gdm can't start plasma session on Wayland
I see the following in the logs when this happens: Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Starting up... Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Could not start D-Bus. Can you call qdbus-qt5? Can anyone else confirm this? -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Roger Whittaker <roger@disruptive.org.uk> [03-17-18 15:46]:
I see the following in the logs when this happens:
Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Starting up... Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Could not start D-Bus. Can you call qdbus-qt5?
Can anyone else confirm this?
no, but I have, https://bugzilla.opensuse.org/show_bug.cgi?id=1020363 reboot to runlevel 3, multi-user.session rm -f /usr/lib/systemd/user/sockets.target.wants/dbus.socket systemctl isolate graphical should get you going again. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Mar 17, 2018 at 05:09:35PM -0400, Patrick Shanahan wrote:
* Roger Whittaker <roger@disruptive.org.uk> [03-17-18 15:46]:
I see the following in the logs when this happens:
Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Starting up... Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Could not start D-Bus. Can you call qdbus-qt5?
Can anyone else confirm this?
no, but I have, https://bugzilla.opensuse.org/show_bug.cgi?id=1020363
reboot to runlevel 3, multi-user.session rm -f /usr/lib/systemd/user/sockets.target.wants/dbus.socket systemctl isolate graphical
should get you going again.
Thanks for this, but this seems to be a different issue. Without that file, I still see the same behaviour. I'll investigate further. -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Roger Whittaker <roger@disruptive.org.uk> [03-17-18 17:25]:
On Sat, Mar 17, 2018 at 05:09:35PM -0400, Patrick Shanahan wrote:
* Roger Whittaker <roger@disruptive.org.uk> [03-17-18 15:46]:
I see the following in the logs when this happens:
Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Starting up... Mar 17 19:37:03 jabberwock /usr/lib/gdm/gdm-wayland-session[2070]: startplasmacompositor: Could not start D-Bus. Can you call qdbus-qt5?
Can anyone else confirm this?
no, but I have, https://bugzilla.opensuse.org/show_bug.cgi?id=1020363
reboot to runlevel 3, multi-user.session rm -f /usr/lib/systemd/user/sockets.target.wants/dbus.socket systemctl isolate graphical
should get you going again.
Thanks for this, but this seems to be a different issue. Without that file, I still see the same behaviour.
I'll investigate further.
if you tried to access runlevel 5 before removing the file, it will still fail. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/17/2018 02:44 PM, Roger Whittaker wrote:
Can anyone else confirm this?
Yes. Okay, I have not checked logs. But I am unable to start a plasma-wayland session with "gdm". The "gdm" menu is showing three entries named "Plasma". Two of them work, and give me an X11 Plasma session. The third one does not work, and just reloads the login screen after a second or so. I have been assuming that this menu entry is supposed to start Plasma-wayland. I have been seeing this for as long as I have been testing it (I think around a year), and on several computers. It also happens on Leap 15.0. However, if I switch to "sddm", then plasma-wayland starts up as it should. It is probably worth starting a new bug report. Patrick Shanahan wrote:
reboot to runlevel 3, multi-user.session rm -f /usr/lib/systemd/user/sockets.target.wants/dbus.socket systemctl isolate graphical
I tried that. It did not help. I booted to multi-user by appending "3" to the end of the grub "linuxefi" line. I removed the indicated file, then switched to graphical mode. Still the same problem. I tested this on only one system. This seems to be a different bug from the one that Patrick has reported. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Mar 17, 2018 at 08:32:21PM -0500, Neil Rickert wrote:
On 03/17/2018 02:44 PM, Roger Whittaker wrote:
Can anyone else confirm this?
Yes.
Okay, I have not checked logs. But I am unable to start a plasma-wayland session with "gdm".
[...]
http://bugzilla.suse.com/show_bug.cgi?id=1085772 -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Neil Rickert -
Patrick Shanahan -
Roger Whittaker