[Bug 846914] New: 13.1 RC1 - when hibernating, the system requests root's password.
https://bugzilla.novell.com/show_bug.cgi?id=846914 https://bugzilla.novell.com/show_bug.cgi?id=846914#c0 Summary: 13.1 RC1 - when hibernating, the system requests root's password. Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: carlos.e.r@opensuse.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- 13.1 RC1 with XFCE - when hibernating, the system requests root's password. This is a laptop, so this should never happen. It asks for the root password, because it says another user is logged in - which is false. And when the password is given, it fails with popup message. A second attempt does not ask for the password, and succeeds... cer@Minas-Anor:~> loginctl list-sessions SESSION UID USER SEAT 2 1000 cer seat0 5 488 lightdm seat0 6 1000 cer seat0 3 sessions listed. cer@Minas-Anor:~> loginctl show-session -al 2 Id=2 Timestamp=Sun 2013-10-20 00:38:35 CEST TimestampMonotonic=33175076 VTNr=7 Seat=[unprintable] TTY= Display=:0 Remote=no RemoteUser= RemoteHost= Service=lightdm Scope=session-2.scope Leader=992 Audit=2 Type=x11 Class=user Active=no State=closing IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 User=[unprintable] Name=cer cer@Minas-Anor:~> cer@Minas-Anor:~> loginctl show-session -al 5 Id=5 Timestamp=Sun 2013-10-20 00:44:33 CEST TimestampMonotonic=390647494 VTNr=7 Seat=[unprintable] TTY= Display=:0 Remote=no RemoteUser= RemoteHost= Service=lightdm-greeter Scope=session-5.scope Leader=1672 Audit=5 Type=x11 Class=user Active=no State=closing IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 User=[unprintable] Name=lightdm cer@Minas-Anor:~> loginctl show-session -al 6 Id=6 Timestamp=Sun 2013-10-20 00:44:38 CEST TimestampMonotonic=395653938 VTNr=7 Seat=[unprintable] TTY= Display=:0 Remote=no RemoteUser= RemoteHost= Service=lightdm Scope=session-6.scope Leader=1701 Audit=6 Type=x11 Class=user Active=yes State=active IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 User=[unprintable] Name=cer cer@Minas-Anor:~> ------ cer@Minas-Anor:~> loginctl list-sessions SESSION UID USER SEAT 2 1000 cer seat0 5 488 lightdm seat0 6 1000 cer seat0 31 1000 cer 4 sessions listed. cer@Minas-Anor:~> loginctl session-status 2 2 - cer (1000) Since: Sun 2013-10-20 00:38:35 CEST; 24h ago Leader: 992 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user State: closing Unit: session-2.scope └─1196 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session cer@Minas-Anor:~> loginctl session-status 5 5 - lightdm (488) Since: Sun 2013-10-20 00:44:33 CEST; 24h ago Leader: 1672 Seat: seat0; vc7 Display: :0 Service: lightdm-greeter; type x11; class user State: closing Unit: session-5.scope ├─1687 dbus-launch --autolaunch 7eba17d2cdb9561656f0964e5255ce5e --binary-syntax --close-stde... ├─1688 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ├─1690 /usr/lib/at-spi2/at-spi-bus-launcher ├─1694 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-addres... └─1697 /usr/lib/at-spi2/at-spi2-registryd --use-gnome-session cer@Minas-Anor:~> loginctl session-status 6 6 - cer (1000) Since: Sun 2013-10-20 00:44:38 CEST; 24h ago Leader: 1701 (lightdm) Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user State: active Unit: session-6.scope ├─1701 lightdm --session-child 26 33 ├─1713 /usr/bin/gnome-keyring-daemon --daemonize --login ├─1715 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc ├─1788 /usr/bin/dbus-launch --sh-syntax --close-stderr --exit-with-session /etc/X11/xinit/xin... ├─1789 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ├─1792 xfce4-session .. ├─1930 /usr/bin/python /usr/share/system-config-printer/applet.py ├─1933 xscreensaver -no-splash cer@Minas-Anor:~> loginctl session-status 31 31 - cer (1000) Since: Sun 2013-10-20 20:12:20 CEST; 5h 0min ago Leader: 8606 (sshd) Remote: 192.168.1.14 Service: sshd; type tty; class user State: active Unit: session-31.scope ├─ 8606 sshd: cer [priv] ├─ 8610 sshd: cer@pts/4 ├─ 8611 -bash ├─13250 loginctl session-status 31 └─13251 less cer@Minas-Anor:~> (the ssh session I have open now to obtain this text) Whatever the cause, the problem for the user is that I get prompted for the root password to hibernate my own laptop. This will not do. Think: the user in the seat can power off the machine pushing the big red button on the case. Why ask for root's password to hibernate, if we can power it off anyway? Worse, depending on the settings, the password prompt can appear _behind_ the logout dialog. Please remove that password prompt or make it optional, so that we can remove it ourselves. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c1
Guido Berhörster
13.1 RC1 with XFCE - when hibernating, the system requests root's password.
This is a laptop, so this should never happen.
It asks for the root password, because it says another user is logged in - which is false.
There is a leftover dbus process from a session, did you log in at 00:38:35 then log out and log in again at 00:44:38?
cer@Minas-Anor:~> loginctl list-sessions SESSION UID USER SEAT 2 1000 cer seat0 5 488 lightdm seat0 6 1000 cer seat0
3 sessions listed. cer@Minas-Anor:~> loginctl show-session -al 2 Id=2 Timestamp=Sun 2013-10-20 00:38:35 CEST TimestampMonotonic=33175076 VTNr=7 Seat=[unprintable] TTY= Display=:0 Remote=no RemoteUser= RemoteHost= Service=lightdm Scope=session-2.scope Leader=992 Audit=2 Type=x11 Class=user Active=no State=closing IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 User=[unprintable] Name=cer cer@Minas-Anor:~>
cer@Minas-Anor:~> loginctl show-session -al 5 Id=5 Timestamp=Sun 2013-10-20 00:44:33 CEST TimestampMonotonic=390647494 VTNr=7 Seat=[unprintable] TTY= Display=:0 Remote=no RemoteUser= RemoteHost= Service=lightdm-greeter Scope=session-5.scope Leader=1672 Audit=5 Type=x11 Class=user Active=no State=closing IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 User=[unprintable] Name=lightdm cer@Minas-Anor:~> loginctl show-session -al 6 Id=6 Timestamp=Sun 2013-10-20 00:44:38 CEST TimestampMonotonic=395653938 VTNr=7 Seat=[unprintable] TTY= Display=:0 Remote=no RemoteUser= RemoteHost= Service=lightdm Scope=session-6.scope Leader=1701 Audit=6 Type=x11 Class=user Active=yes State=active IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 User=[unprintable] Name=cer cer@Minas-Anor:~>
Whatever the cause, the problem for the user is that I get prompted for the root password to hibernate my own laptop. This will not do.
Think: the user in the seat can power off the machine pushing the big red button on the case. Why ask for root's password to hibernate, if we can power it off anyway?
No, this is the system default and local user has not always access to the power button, e.g. on a multiseat box. The above is a bug, there is a dbus process left behind keeping a second session alive.
Worse, depending on the settings, the password prompt can appear _behind_ the logout dialog.
Please remove that password prompt or make it optional, so that we can remove it ourselves.
It is optional, feel free to configure it in policykit as you like. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c2
Guido Berhörster
cer@Minas-Anor:~> loginctl session-status 2 2 - cer (1000) Since: Sun 2013-10-20 00:38:35 CEST; 24h ago Leader: 992 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user State: closing Unit: session-2.scope └─1196 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
On login the display manager starts xfce4-session which then exec's dbus-launch with /usr/bin/dbus-launch --sh-syntax --exit-with-session /etc/X11/xinit/xinitrc which in turn should wrap the session. Any idea how the above could happen so that the session bus daemon gets left behind despite the --exit-with-session? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c3
--- Comment #3 from Carlos Robinson
(In reply to comment #0)
13.1 RC1 with XFCE - when hibernating, the system requests root's password.
This is a laptop, so this should never happen.
It asks for the root password, because it says another user is logged in - which is false.
There is a leftover dbus process from a session, did you log in at 00:38:35 then log out and log in again at 00:44:38?
It happens as well on a fresh boot. Look: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted 1 488 lightdm seat0 2 1000 cer seat0 1 - lightdm (488) Since: Mon 2013-10-21 21:27:34 CEST; 2min 55s ago Leader: 800 Seat: seat0; vc7 Display: :0 Service: lightdm-greeter; type x11; class user State: closing Unit: session-1.scope ├─949 dbus-launch --autolaunch 7eba17d2cdb9561656f0964e5255... ├─983 /bin/dbus-daemon --fork --print-pid 5 --print-address... ├─985 /usr/lib/at-spi2/at-spi-bus-launcher ├─989 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibi... └─992 /usr/lib/at-spi2/at-spi2-registryd --use-gnome-sessio... 2 - cer (1000) Since: Mon 2013-10-21 21:27:51 CEST; 2min 42s ago Leader: 1107 (lightdm) Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user State: active Unit: session-2.scope ├─1107 lightdm --session-child 12 19 ├─1123 /usr/bin/gnome-keyring-daemon --daemonize --login ├─1125 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xse... ├─1198 /usr/bin/dbus-launch --sh-syntax --close-stderr --ex... ├─1199 /bin/dbus-daemon --fork --print-pid 5 --print-addres... ├─1202 xfce4-session ├─1205 /usr/lib/xfce4/xfconf/xfconfd ├─1211 xfwm4 --display :0.0 --sm-client-id 290a4257b-928d-4... ├─1214 Thunar --sm-client-id 24b517214-b259-41ed-bdcf-3dc2a... ├─1216 xfce4-panel --display :0.0 --sm-client-id 254fe4f6f-... ├─1217 xfsettingsd --display :0.0 --sm-client-id 23fac851f-... ├─1219 syndaemon -i 2.0 -K -R ├─1220 xfdesktop --display :0.0 --sm-client-id 24f983452-4e... ├─1221 xfce4-terminal --geometry=111x18 --display :0.0 --ro... ├─1224 /usr/lib/gvfs/gvfsd ├─1228 gkrellm --sm-client-id 2aa7e9bfa-a56f-4882-a675-6ef0... ├─1230 /usr/lib/gvfs//gvfsd-fuse -f /run/user/1000/gvfs ├─1233 xterm -xtsessionID 210713e44-69d2-45a4-baad-c770edaa... ├─1235 /usr/lib64/tumbler-1/tumblerd ├─1238 /usr/lib/xfce4/panel/wrapper /usr/lib64/xfce4/panel/... ├─1240 /usr/lib/xfce4/panel/wrapper /usr/lib64/xfce4/panel/... ├─1241 /usr/lib/xfce4/panel/wrapper /usr/lib64/xfce4/panel/... ├─1249 xterm -xtsessionID 237f1db8d-1219-4e09-9a07-8615d64b... ├─1255 xfce4-power-manager --restart --sm-client-id 293bdd9... ├─1258 /usr/lib/xfce4/notifyd/xfce4-notifyd ├─1270 gnome-pty-helper ├─1273 bash ├─1274 bash ├─1288 bash ├─1347 /usr/lib/tracker-miner-fs ├─1356 /usr/lib/GConf/2/gconfd-2 ├─1359 /usr/lib/gvfs/gvfs-udisks2-volume-monitor ├─1367 /usr/lib/polkit-gnome-authentication-agent-1 ├─1382 /usr/lib/tracker-store ├─1393 /usr/lib/gvfs/gvfs-mtp-volume-monitor ├─1396 nm-applet ├─1400 /usr/lib/gvfs/gvfs-goa-volume-monitor ├─1403 /usr/lib/goa-daemon ├─1419 /usr/bin/python /usr/share/system-config-printer/app... ├─1425 xscreensaver -no-splash ├─1434 /usr/lib/gvfs/gvfs-afc-volume-monitor ├─1441 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor ├─1443 pk-update-icon ├─1458 /usr/lib/gvfs/gvfsd-trash --spawner :1.10 /org/gtk/g... ├─1463 rccexternal ├─1467 rccexternal ├─1478 tailf /var/log/messages ├─1558 /usr/lib/tracker-extract └─1590 loginctl session-status 2 Please remember that this is a laptop. I can push the big button or remove the battery. You can do nothing to impede that. Nor in my desktop. Do you remember the outcry that happened when the daughter of Mr Linus could not connect to a printer at school without being root? This is similar. The person that carries a laptop should be able to power off and hibernate, no questions asked.
Please remove that password prompt or make it optional, so that we can remove it ourselves.
It is optional, feel free to configure it in policykit as you like.
Where is that in YaST is the policykit module? :-| Or where is the exact hack published? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c4
--- Comment #4 from Guido Berhörster
(In reply to comment #1)
(In reply to comment #0)
13.1 RC1 with XFCE - when hibernating, the system requests root's password.
This is a laptop, so this should never happen.
It asks for the root password, because it says another user is logged in - which is false.
There is a leftover dbus process from a session, did you log in at 00:38:35 then log out and log in again at 00:44:38?
It happens as well on a fresh boot. Look:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
1 488 lightdm seat0 2 1000 cer seat0
Yeah, the greeter session should be gone after login. I have a fresh RC1 installation and can reproduce this.
Please remember that this is a laptop. I can push the big button or remove the battery. You can do nothing to impede that. Nor in my desktop.
Do you remember the outcry that happened when the daughter of Mr Linus could not connect to a printer at school without being root? This is similar. The person that carries a laptop should be able to power off and hibernate, no questions asked.
Well, discussions about default settings need to happen on the factory list, this is not the right place.
Please remove that password prompt or make it optional, so that we can remove it ourselves.
It is optional, feel free to configure it in policykit as you like.
Where is that in YaST is the policykit module? :-|
Or where is the exact hack published?
You can place overrides in /etc/polkit-default-privs.local and then run /sbin/set_polkit_default_privs. The privileges you're looking for are org.freedesktop.login1.hibernate-multiple-sessions and org.freedesktop.login1.suspend-multiple-sessions, see the man pages for polkit-default-privs, set_polkit_default_privs, and polkit for details. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c5
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c6
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c7
--- Comment #7 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c8
--- Comment #8 from Frederic Crozat
Commit looks trivial enough for inclusion in 13.1, if 208 is not going to 13.1. http://cgit.freedesktop.org/systemd/systemd/commit/?id=c68ba912c347a79885bb0...
Frederic?
I would prefer to get 208 in 13.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c9
--- Comment #9 from Guido Berhörster
Another option is to add session optional pam_systemd.so class=greeter to lightdm-greeter greeter file...
I'll do so, but that only solves half of the problem. See the original report, any idea why these dbus processes are left behind by the greeter and user sessions? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c10
--- Comment #10 from Hrvoje Senjan
(In reply to comment #7)
Another option is to add session optional pam_systemd.so class=greeter to lightdm-greeter greeter file...
I'll do so, but that only solves half of the problem. See the original report, any idea why these dbus processes are left behind by the greeter and user sessions?
I'm not sure, as i tried to reproduce with Factory, and with KDE i don't get such issue. Then i tried with XFCE, and there only process left for a user after logout was gnome-keyring. After killing that one, session was no longer indicated with logind/ctl. (note that indeed the greeter was marked as alive with both DE's, and that was no longer the case after adding the class=greeter, which should be a standard, according to http://www.freedesktop.org/wiki/Software/systemd/writing-display-managers/) But since reporter uses ssh(?), could be fdo#39197. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c11
--- Comment #11 from Guido Berhörster
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c12
--- Comment #12 from Carlos Robinson
) But since reporter uses ssh(?), could be fdo#39197.
I used ssh the first time. on Comment 3 you can see a fresh boot without ssh. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c13
--- Comment #13 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c14
--- Comment #14 from Hrvoje Senjan
(In reply to comment #10)
) But since reporter uses ssh(?), could be fdo#39197.
I used ssh the first time. on Comment 3 you can see a fresh boot without ssh.
OK, that would be resolved with what was said in comment 7 and/or comment 11. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c15
--- Comment #15 from Carlos Robinson
OK, that would be resolved with what was said in comment 7 and/or comment 11.
For me the solution means disabling completely the policy. I can reboot or halt the machine without questions asked, but to hibernate I need permission - on my laptop! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c16
Guido Berhörster
@Guido, could i get some pointers as to how to try and reproduce? As my install is primary a KDE one, maybe i haven't got all of XFCE packages or something. (Also factory has systemd 208 & DBus 1.7.6 which might resolve this things. Well, at least systemd 208 should cure the symptoms of the report)
Best thing would probably be a RC1 install with Xfce as default in a vm, particularly since factory versions differ now. (In reply to comment #15)
(In reply to comment #14)
OK, that would be resolved with what was said in comment 7 and/or comment 11.
For me the solution means disabling completely the policy. I can reboot or halt the machine without questions asked, but to hibernate I need permission - on my laptop!
Please take this to the mailinglist, this is not the right place to argue about defaults. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c17
--- Comment #17 from Carlos Robinson
For me the solution means disabling completely the policy. I can reboot
or halt the machine without questions asked, but to hibernate I need
permission - on my laptop!
Please take this to the mailinglist, this is not the right place to argue about defaults.
I did already, and I'm waiting for responses. I'm simply stating here what I think the root issue is. I could create an usability bugzilla about the root issue, if you prefer... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c18
--- Comment #18 from Guido Berhörster
I could create an usability bugzilla about the root issue, if you prefer..
You can try opening a bug and assign to the security team since they are responsible for the policies. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c19
--- Comment #19 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c20
--- Comment #20 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c21
--- Comment #21 from Guido Berhörster
OK, tried now with the full XFCE pattern (with recommends) and lightdm-gtk-greeter (previously i tried with KDE one), and still didn't get a leftover DBus process. Now, in contrast to previous attempt, where keyring
It is apparently autolaunched by a gtk module, do you have at-spi2-atk-common at-spi2-atk-gtk2 at-spi2-core libatk-1_0-0 libatk-bridge-2_0-0 installed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c22
--- Comment #22 from Hrvoje Senjan
(In reply to comment #20)
OK, tried now with the full XFCE pattern (with recommends) and lightdm-gtk-greeter (previously i tried with KDE one), and still didn't get a leftover DBus process. Now, in contrast to previous attempt, where keyring
It is apparently autolaunched by a gtk module, do you have at-spi2-atk-common at-spi2-atk-gtk2 at-spi2-core libatk-1_0-0 libatk-bridge-2_0-0 installed? Yes, and i didn't get a single leftover DBus process for a user :-(
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c23
--- Comment #23 from Guido Berhörster
(In reply to comment #21)
(In reply to comment #20)
OK, tried now with the full XFCE pattern (with recommends) and lightdm-gtk-greeter (previously i tried with KDE one), and still didn't get a leftover DBus process. Now, in contrast to previous attempt, where keyring
It is apparently autolaunched by a gtk module, do you have at-spi2-atk-common at-spi2-atk-gtk2 at-spi2-core libatk-1_0-0 libatk-bridge-2_0-0 installed? Yes, and i didn't get a single leftover DBus process for a user :-(
Can you try a 13.1 Xfce default installation in kvm? With a freshly net-installed vm I consistently get this *after* login:
loginctl -al session-status 1 1 - lightdm (488) Since: Wed 2013-10-30 15:39:41 UTC; 6min ago Leader: 1430 Seat: seat0; vc7 Display: :0 Service: lightdm-greeter; type x11; class greeter State: closing Unit: session-1.scope ├─1840 dbus-launch --autolaunch 7eba17d2cdb9561656f0964e5255ce5e --binary-syntax --clos ├─1868 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session ├─1879 /usr/lib/at-spi2/at-spi-bus-launcher ├─1892 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print- └─1904 /usr/lib/at-spi2/at-spi2-registryd --use-gnome-session
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c24
--- Comment #24 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=846914
https://bugzilla.novell.com/show_bug.cgi?id=846914#c25
--- Comment #25 from Guido Berhörster
OK, there was a misunderstanding ;-) I thought the issue was a runaway user process, but you meant lightdm... (no idea how that one get's started, does it has some hardcoded command, etc, and finally, i saw everywhere that lightdm is logged as a user with logind). Note that with "pam solution", i did not have it logged.
Now, I'm not sure I understand you. What I meant was a leftover dbus process in the lightdm greeter session after the lightdm greeter has exited. lightdm itself is a daemon that gets started through /etc/init.d/xdm, the lightdm daemon then spawns a greeter as the unprivileged lightdm user, e.g. /usr/sbin/lightdm-gtk-greeter. Through a gtk accessibility module a dbus daemon then gets auto-launched but it does not exit once the greeter is gone, thus keeping the greeter session alive in closing state. Something similar seems to happen sometimes with user sessions as well, see session no. 2 in the initial report above for a leftover dbus daemon in the user session. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com