[Bug 1020363] New: [Build 20170116] Restarting graphical target via systemd isolate stops session D-Bus
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 Bug ID: 1020363 Summary: [Build 20170116] Restarting graphical target via systemd isolate stops session D-Bus Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/335702/modules/multi_ users_dm/steps/26 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce@forge.provo.novell.com Reporter: marius.kittler@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- ## Observation The purpose of this test is to check how login managers work with many existing users on a system. Most login managers react on this by replacing the dropdown user selection menu by a text field. To do this, the existing X11/Wayland/Whatever is stopped. Then 100 users are created and then the graphical session is restarted. This doesn't work anymore: ``` systemctl isolate multi-user.target # create 100 users systemctl isolate graphical.target ``` When the graphical target is isolated an error message is shown: 'Unable to contact settings server, Failed to connect to socket /run/user/1000/bus' openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_on_xfce@64bit fails in [multi_users_dm](http://openqa.opensuse.org/tests/335702/modules/multi_users_dm/steps/26) ## Reproducible Fails since Build [20170111](http://openqa.opensuse.org/tests/333055) ## Expected result Last good: [20170110](http://openqa.opensuse.org/tests/332625) ## Further details The issue has been triggered by starting the session D-Bus via systemd: https://build.opensuse.org/package/rdiff/Base:System/dbus-1?linkrev=base&rev=236 It seems that pulseaudio and `spice-vdagent` are preventing the old session to close. When starting also pulseaudio via systemd and killing `spice-vdagent` before isolating the graphical target the issue doesn't occur. I think starting D-Bus via systemd is the right thing to as it allows usage of `busctl` for instance. It should be possible to reduce the problem by also starting pulseaudio via systemd. Not sure about `spice-vdagent`, though. Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?version=Tumbleweed&arch=x86_64&flavor=DVD&distri=opensuse&test=extra_tests_on_xfce&machine=64bit) It also fails for KDE: https://openqa.opensuse.org/tests/335701#step/multi_users_dm/26 ## Workaround Remove the symlink `/usr/lib/systemd/user/sockets.target.wants/dbus.socket` for the old behavior (session D-Bus no longer started via systemd). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 patrick shanahan <paka@wahoo.no-ip.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Xfce |Basesystem -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c11 patrick shanahan <paka@wahoo.no-ip.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(paka@wahoo.no-ip. | |org) | --- Comment #11 from patrick shanahan <paka@wahoo.no-ip.org> --- 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?
after booting to multi-user.target ● user-1000.slice - User Slice of paka Loaded: loaded (/run/systemd/transient/user-1000.slice; transient; vendor preset: disabled) Transient: yes Active: active since Mon 2017-05-08 08:13:02 EDT; 4min 20s ago Tasks: 7 (limit: 10813) CGroup: /user.slice/user-1000.slice ├─session-1.scope │ ├─2860 sshd: paka [priv] │ ├─2866 sshd: paka@pts/0 │ ├─2867 -bash │ ├─2913 su - │ └─2916 -bash └─user@1000.service └─init.scope ├─2863 /usr/lib/systemd/systemd --user └─2864 (sd-pam) May 08 08:13:02 toshiba systemd[2863]: pam_unix(systemd-user:session): session opened for user paka by (uid=0) May 08 08:13:02 toshiba systemd[2863]: Reached target Timers. May 08 08:13:02 toshiba systemd[2863]: Reached target Sockets. May 08 08:13:02 toshiba systemd[2863]: Reached target Paths. May 08 08:13:02 toshiba systemd[2863]: Reached target Basic System. May 08 08:13:02 toshiba systemd[2863]: Reached target Default. May 08 08:13:02 toshiba systemd[2863]: Startup finished in 62ms. May 08 08:13:08 toshiba su[2913]: (to root) paka on pts/0 May 08 08:13:08 toshiba su[2913]: pam_unix(su-l:session): session opened for user root by paka(uid=1000) May 08 08:13:08 toshiba su[2913]: pam_systemd(su-l:session): Cannot create session: Already running in a session and then changing into graphical.target and receiving "Could not sync environment to dbus.": ● user-1000.slice - User Slice of paka Loaded: loaded (/run/systemd/transient/user-1000.slice; transient; vendor preset: disabled) Transient: yes Active: active since Mon 2017-05-08 08:32:51 EDT; 1min 49s ago Tasks: 11 (limit: 10813) CGroup: /user.slice/user-1000.slice ├─session-1.scope │ ├─2806 sshd: paka [priv] │ ├─2814 sshd: paka@pts/0 │ ├─2815 -bash │ ├─2861 su - │ ├─2864 -bash │ └─4615 systemctl status user-1000.slice └─session-3.scope ├─4517 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-autheb1f7284-6342-4416-adbf-ba838cf0d060 --id 1 --start /usr/bin/startkde --user paka ├─4518 /bin/sh /usr/bin/startkde ├─4586 /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display /etc/X11/xinit/xinitrc ├─4587 /usr/bin/gpg-agent --sh --daemon --keep-display /etc/X11/xinit/xinitrc └─4612 xmessage -geometry 500x100 Could not sync environment to dbus. May 08 08:33:02 toshiba systemd[2809]: Stopped target Timers. May 08 08:33:02 toshiba systemd[2809]: Stopped target Paths. May 08 08:33:02 toshiba systemd[2809]: Stopped target Sockets. May 08 08:33:02 toshiba systemd[2809]: Closed D-Bus User Message Bus Socket. May 08 08:33:02 toshiba systemd[2809]: Reached target Shutdown. May 08 08:33:02 toshiba systemd[2809]: Starting Exit the Session... May 08 08:33:03 toshiba systemd[2809]: Received SIGRTMIN+24 from PID 2910 (kill). May 08 08:33:03 toshiba systemd[2810]: pam_unix(systemd-user:session): session closed for user paka May 08 08:33:22 toshiba sddm-helper[4517]: Starting: "/etc/X11/xdm/Xsession /usr/bin/startkde" May 08 08:33:22 toshiba sddm-helper[4518]: Adding cookie to "/home/paka/.Xauthority" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c12 --- Comment #12 from Simon Lees <simonf.lees@suse.com> --- (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? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c13 --- Comment #13 from patrick shanahan <paka@wahoo.no-ip.org> --- (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 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c14 --- Comment #14 from Simon Lees <simonf.lees@suse.com> --- (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. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c15 --- Comment #15 from Simon Lees <simonf.lees@suse.com> ---
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.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 Илья Индиго <ilya@ilya.pp.ua> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ilya@ilya.pp.ua -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c19 --- Comment #19 from patrick shanahan <paka@wahoo.no-ip.org> --- any movement on this? I keep finding the link: /usr/lib/systemd/user/sockets.target.wants/dbus.socket reinstalled, but only after not being able to log into the graphics screen. and the problem is on several boxes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 patrick shanahan <paka@wahoo.no-ip.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c21 --- Comment #21 from patrick shanahan <paka@wahoo.no-ip.org> --- this bug is a REAL problem for remote administration -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c23 --- Comment #23 from patrick shanahan <paka@wahoo.no-ip.org> --- reared it's ugly head again with updates from 2017-08-28 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 Stefan Brüns <stefan.bruens@rwth-aachen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.bruens@rwth-aachen.d | |e -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 Rodion Iafarov <riafarov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.opensuse.or | |g/show_bug.cgi?id=1063060 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c27 Foolish Ewe <foolishewe@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |foolishewe@hotmail.com --- Comment #27 from Foolish Ewe <foolishewe@hotmail.com> --- This bug recently hit me on OpenSuse Tumbleweed after an update. I followed Patrick Shanahans advice as to remove the troublesome /usr/lib/systemd/user/sockets.target.wants/dbus.socket file follows: 1) Boot to Linux, see plasma login screen 2) Hot key to a console, check to see if the offending file exists and remove it as follows: 2a) Log in as root 2b) ls /usr/lib/systemd/user/sockets.target.wants/dbus.socket 2c) rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket 3) Hot key back to the plasma window 4) Log in - Success As an added bonus, it corrected an issue in knetworkmanager that prevented me from connecting to the internet in OpenSuse. This is something I'd really like to see fixed. My most recent updates timings were (I recently downloaded mlocate and bluejeans, but the 10/25/2017 download was a sudo zypper up (I think I did it that way an not through yast) which triggered big update of over 1000 rpms, the initial install was on 10/22/2017): rpm -qa --last | head -20 mlocate-lang-0.26-23.2.noarch Sat 28 Oct 2017 08:54:24 PM PDT mlocate-0.26-23.2.x86_64 Sat 28 Oct 2017 08:54:24 PM PDT bluejeans-1.31.16-1.x86_64 Thu 26 Oct 2017 10:17:52 AM PDT x11-video-nvidiaG04-384.90-26.2.x86_64 Wed 25 Oct 2017 01:09:26 PM PDT nvidia-computeG04-384.90-26.2.x86_64 Wed 25 Oct 2017 01:09:24 PM PDT nvidia-glG04-384.90-26.2.x86_64 Wed 25 Oct 2017 01:09:22 PM PDT nvidia-gfxG04-kmp-default-384.90_k4.13.4_1-26.2.x86_64 Wed 25 Oct 2017 01:07:42 PM PDT transcode-1.1.7-4.13.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libswresample1-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libpostproc53-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libavformat56-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libavcodec56-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT texlive-pst-tree-2017.132.1.13svn43272-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pst-text-2017.132.1.00svn15878-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pst-slpe-2017.132.1.31svn24391-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pstricks-add-2017.132.3.83svn44281-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pst-blur-2017.132.2.0svn15878-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-powerdot-2017.132.1.5asvn38984-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT normalize-0.7.7-3.13.x86_64 Wed 25 Oct 2017 01:07:40 PM PDT libxvidcore4-1.3.4-3.12.x86_64 Wed 25 Oct 2017 01:07:40 PM PDT -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c28 patrick shanahan <paka@wahoo.no-ip.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-xfce@forge.provo.n |simonf.lees@suse.com |ovell.com | --- Comment #28 from patrick shanahan <paka@wahoo.no-ip.org> --- (In reply to Foolish Ewe from comment #27)
This bug recently hit me on OpenSuse Tumbleweed after an update. I followed Patrick Shanahans advice as to remove the troublesome /usr/lib/systemd/user/sockets.target.wants/dbus.socket file follows:
1) Boot to Linux, see plasma login screen 2) Hot key to a console, check to see if the offending file exists and remove it as follows: 2a) Log in as root 2b) ls /usr/lib/systemd/user/sockets.target.wants/dbus.socket 2c) rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket 3) Hot key back to the plasma window 4) Log in - Success
As an added bonus, it corrected an issue in knetworkmanager that prevented me from connecting to the internet in OpenSuse. This is something I'd really like to see fixed.
My most recent updates timings were (I recently downloaded mlocate and bluejeans, but the 10/25/2017 download was a sudo zypper up (I think I did it that way an not through yast) which triggered big update of over 1000 rpms, the initial install was on 10/22/2017): rpm -qa --last | head -20 mlocate-lang-0.26-23.2.noarch Sat 28 Oct 2017 08:54:24 PM PDT mlocate-0.26-23.2.x86_64 Sat 28 Oct 2017 08:54:24 PM PDT bluejeans-1.31.16-1.x86_64 Thu 26 Oct 2017 10:17:52 AM PDT x11-video-nvidiaG04-384.90-26.2.x86_64 Wed 25 Oct 2017 01:09:26 PM PDT nvidia-computeG04-384.90-26.2.x86_64 Wed 25 Oct 2017 01:09:24 PM PDT nvidia-glG04-384.90-26.2.x86_64 Wed 25 Oct 2017 01:09:22 PM PDT nvidia-gfxG04-kmp-default-384.90_k4.13.4_1-26.2.x86_64 Wed 25 Oct 2017 01:07:42 PM PDT transcode-1.1.7-4.13.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libswresample1-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libpostproc53-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libavformat56-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT libavcodec56-2.8.13-4.6.x86_64 Wed 25 Oct 2017 01:07:41 PM PDT texlive-pst-tree-2017.132.1.13svn43272-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pst-text-2017.132.1.00svn15878-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pst-slpe-2017.132.1.31svn24391-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pstricks-add-2017.132.3.83svn44281-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-pst-blur-2017.132.2.0svn15878-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT texlive-powerdot-2017.132.1.5asvn38984-32.1.noarch Wed 25 Oct 2017 01:07:40 PM PDT normalize-0.7.7-3.13.x86_64 Wed 25 Oct 2017 01:07:40 PM PDT libxvidcore4-1.3.4-3.12.x86_64 Wed 25 Oct 2017 01:07:40 PM PDT
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c29 patrick shanahan <paka@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #29 from patrick shanahan <paka@opensuse.org> --- happed again with update to 20171108 on four tw machines solution: rm -f /usr/lib/systemd/user/sockets.target.wants/dbus.socket -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c31 --- Comment #31 from patrick shanahan <paka@opensuse.org> --- happed again with update to 20171211 on four tw machines solution: rm -f /usr/lib/systemd/user/sockets.target.wants/dbus.socket -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c32 --- Comment #32 from patrick shanahan <paka@opensuse.org> --- since 15-12-2017, the presence of /usr/lib/systemd/user/sockets.target.wants/dbus.socket has not affected entering the graphical target. I don't know that the problem is solved, but it now does not appear to deny entering the graphical target. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c33 --- Comment #33 from Ludwig Nussel <lnussel@suse.com> --- Simon, this bug is referenced from openQA tests as breaking the multi users dm test. Any chance to move this forward? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c34 --- Comment #34 from patrick shanahan <paka@opensuse.org> --- (In reply to patrick shanahan from comment #32)
since 15-12-2017, the presence of /usr/lib/systemd/user/sockets.target.wants/dbus.socket has not affected entering the graphical target.
I don't know that the problem is solved, but it now does not appear to deny entering the graphical target.
But it is back 04-01-2017 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c39 --- Comment #39 from patrick shanahan <paka@opensuse.org> --- is this bug ever going to be resolved? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c40 --- Comment #40 from Marius Kittler <marius.kittler@suse.com> --- I still think starting the user D-Bus daemon via systemd is the right thing to do.
It seems that pulseaudio and `spice-vdagent` are preventing the old session to close. When starting also pulseaudio via systemd and killing `spice-vdagent` before isolating the graphical target the issue doesn't occur.
So if my initial observation is still valid we could easily fix this by starting pulsaudio via systemd. This would at least reduce the problem to `spice-vdagent`. I'm not sure about it, but apparently it is just a KVM/qemu guest thing so it is not really important. In openQA we could workaround the issue just by quitting it manually before the isolation. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c41 --- Comment #41 from patrick shanahan <paka@opensuse.org> --- (In reply to patrick shanahan from comment #34)
(In reply to patrick shanahan from comment #32)
since 15-12-2017, the presence of /usr/lib/systemd/user/sockets.target.wants/dbus.socket has not affected entering the graphical target.
I don't know that the problem is solved, but it now does not appear to deny entering the graphical target.
But it is back 04-01-2017
that should read 4 jan 2018 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c42 --- Comment #42 from patrick shanahan <paka@opensuse.org> --- again today on three Tumbleweed boxes. placated by: rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c44 --- Comment #44 from patrick shanahan <paka@opensuse.org> --- again today on three Tumbleweed boxes. placated by: rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket over a year now and a "confirmed" problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c45 --- Comment #45 from patrick shanahan <paka@opensuse.org> --- updated Tumbleweed to 20180613 and problem again today on three Tumbleweed boxes. placated by: rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket over a year now and a "confirmed" problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c46 --- Comment #46 from Simon Lees <simonf.lees@suse.com> --- (In reply to patrick shanahan from comment #45)
updated Tumbleweed to 20180613 and problem again today on three Tumbleweed boxes. placated by: rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket
over a year now and a "confirmed" problem.
Yes but upstream has put the file there for a reason and until I have time to investigate why its there i'm not going to remove it until i'm sure something else is not going to break. Furthermore there is a documented work around in this ticket of starting and stopping the display-manager service to drop in and out of a graphical system, which is the recommended way on openSUSE anyway. So yes its on my todo list but it was below my list for SLE-15 / Leap 15 which is why I haven't spent much time on it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c47 --- Comment #47 from Marius Kittler <marius.kittler@suse.com> ---
i'm not going to remove it until i'm sure something else is not going to break
The reason I added this unit file to the D-Bus package over a year ago actually was fixing the following issues: * `busctl --user` wasn't working. * The user-session D-Bus service to control systemd user services wasn't working. So removing the unit file will break these things again very likely. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020363 http://bugzilla.opensuse.org/show_bug.cgi?id=1020363#c48 --- Comment #48 from Marius Kittler <marius.kittler@suse.com> --- And yes, I reported this issue and introduced the change which caused this issue at the same time. I mainly added this ticked because we've found this bug via openQA. However, I still think starting the user D-Bus daemon via systemd is the right thing to do. So - to fix the problem - I would further investigate why pulseaudio and `spice-vdagent` are preventing the old session to close. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com