In article <CAJYbmcYAXZqdK4KC9G=Niw87pfp+9bpGD3F5kZ1S+mtpnzDXrg__9150.06092186577$1392117510$gmane$o...@mail.gmail.com> you wrote: >> Sorry, but I fail to see the relation between dirmngr and polkit-kde-1, why >> does the use of su vs start-stop-daemon affects the hibernation?
> According to the description in the > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668890 su spawns login > shell where the start-stop-daemon doesn't. > This login shell that su spawns violates polkit policy > org.freedesktop.login1.hibernate-multiple-sessions when trying to hibernate > and it can be seen with loginctl. > loginctl shows: > SESSION UID USER SEAT > c1 112 dirmngr > c2 1000 durin seat0 Thanks, that makes it clearer. > I don't know if su works differently when using systemd and not sysvinit > and makes this problem appear only when using systemd. Ok, I don't see that behavior here (I'm not using systemd as init system but I have it installed), start-stop-daemon and /bin/su use the setuid syscall, but su uses pam, so, its related to the pam-session part. I still don't understand why is it different if you are using a systemd init system or not. -- "Anytime you have a fifty-fifty chance of getting something right, there's a 90 percent probability you'll get it wrong." -- The 50-50-90 rule Saludos /\/\ /\ >< `/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org