* 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