http://bugzilla.opensuse.org/show_bug.cgi?id=1063060 http://bugzilla.opensuse.org/show_bug.cgi?id=1063060#c19 --- Comment #19 from patrick shanahan <paka@opensuse.org> --- (In reply to Simon Lees from comment #18)
(In reply to patrick shanahan from comment #17)
sounds list the same as https://bugzilla.opensuse.org/show_bug.cgi?id=1020363 which still has not been addressed.
removal of /usr/lib/systemd/user/sockets.target.wants/dbus.socket before entering graphical.session appears to allow plasma session access. note, *before* attempting access to runlevel 5 after booting.
It seems reasonable user session would require a dbus socket, I don't think removing this is the correct answer long term. But I am not the worlds biggest systemd expert maybe there is another way it could be done.
dbus will start and create it's sockets w/o this re your comment #14 to but #1020363 Simon Lees 2017-05-09 01:13:57 UTC (In reply to patrick shanahan from comment #13)
(In reply to Simon Lees from comment #12)
(In reply to patrick shanahan from comment #11)
I would be happy to provide information. But I only just found the request for information by checking status of the report. Seems even though I an listed on the cc: list, I have not received any notice.(In reply to Simon Lees from comment #8)
Patrick I guess we need to debug your issue further to work out whats preventing dbus from closing in this case could you provide the output of "systemctl status user-XXX.slice" where XXX is your uid?
Thanks for the info, i'll try and replicate this tomorrow, its not what I was expecting to see. dbus isn't running in the multi-user.target (which is expected if nothing is using it) so nothing should be preventing it from running when the graphical target is started.
Just confirming you are running tumbleweed?
yes, 20170505
info may be skewed by having remote ssh access. I can alway trigger the failure that way. I can open a graphical session from an clean boot w/o any remote ssh sessions active.
did you want to see the output w/o the remote session?
ps: there is a problem with mail, I am not receiving and my addr is listed in cc
I can replicate the problem here so i'll chase it up with upstream to see what we can do about it. [reply] [−] Comment 15 Simon Lees 2017-05-12 03:00:33 UTC
From the following, it seems that the whole user session is closed when isolate is run which may lead to bigger issues then just with dbus
test@linux-gruo:~> dbus-monitor signal time=1494556806.294641 sender=org.freedesktop.DBus -> destination=:1.1 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.1" ..... test@linux-gruo:~> date Fri May 12 12:10:10 ACST 2017 test@linux-gruo:~> date Fri May 12 12:10:32 ACST 2017 < systemctl isolate graphical.target run from a different session> test@linux-gruo:~> dbus-monitor Failed to open connection to session bus: Failed to connect to socket /run/user/1001/bus: Connection refused test@linux-gruo:~> date Fri May 12 12:10:43 ACST 2017 test@linux-gruo:~> journalctl Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. ...... May 12 12:10:01 linux-gruo systemd[1554]: Reached target Timers. May 12 12:10:01 linux-gruo systemd[1554]: Starting D-Bus User Message Bus Socket. May 12 12:10:01 linux-gruo systemd[1554]: Reached target Paths. May 12 12:10:01 linux-gruo systemd[1554]: Listening on D-Bus User Message Bus Socket. May 12 12:10:01 linux-gruo systemd[1554]: Reached target Sockets. May 12 12:10:01 linux-gruo systemd[1554]: Reached target Basic System. May 12 12:10:01 linux-gruo systemd[1554]: Reached target Default. May 12 12:10:01 linux-gruo systemd[1554]: Startup finished in 66ms. May 12 12:10:06 linux-gruo systemd[1554]: Started D-Bus User Message Bus. May 12 12:10:06 linux-gruo dbus-daemon[1603]: Connection :1.1 (uid=1001 pid=1602 comm="dbus-monitor ") became a monitor. May 12 12:10:08 linux-gruo dbus-daemon[1603]: Monitoring connection :1.1 closed. May 12 12:10:33 linux-gruo systemd[1554]: Stopping D-Bus User Message Bus... May 12 12:10:33 linux-gruo systemd[1554]: Stopped target Default. May 12 12:10:33 linux-gruo systemd[1554]: Stopped D-Bus User Message Bus. May 12 12:10:33 linux-gruo systemd[1554]: Stopped target Basic System. May 12 12:10:33 linux-gruo systemd[1554]: Stopped target Timers. May 12 12:10:33 linux-gruo systemd[1554]: Stopped target Paths. May 12 12:10:33 linux-gruo systemd[1554]: Stopped target Sockets. May 12 12:10:33 linux-gruo systemd[1554]: Closed D-Bus User Message Bus Socket. May 12 12:10:33 linux-gruo systemd[1554]: Reached target Shutdown. May 12 12:10:33 linux-gruo systemd[1554]: Starting Exit the Session... May 12 12:10:33 linux-gruo systemd[1554]: Received SIGRTMIN+24 from PID 1661 (kill). May 12 12:10:33 linux-gruo systemd[1555]: pam_unix(systemd-user:session): session closed for user test -- You are receiving this mail because: You are on the CC list for the bug.