Am Montag, 22. Juli 2013, 16:17:53 schrieb Michael Biebl: > Am 22.07.2013 16:11, schrieb Martin Steigerwald: > > Am Montag, 22. Juli 2013, 15:32:39 schrieb Michael Biebl: > >> Am 22.07.2013 10:45, schrieb Martin Steigerwald: > >>> Authentification is required for hibernating the system while other > >>> users > >>> are logged in. > >> > >> What's the output of ck-list-sessions and loginctl? > > > > Hmmm, dirmngr. > > > > merkaba:~> apt-show-versions | grep dirmngr > > dirmngr:amd64/sid 1.1.0-3 uptodate > > > > > > > > merkaba:~> loginctl > > > > SESSION UID USER SEAT > > > > c1 120 dirmngr > > c2 1000 martin seat0 > > > > 2 sessions listed. > > > > merkaba:~> ck-list-sessions > > > > Session5: > > unix-user = '0' > > realname = 'root' > > seat = 'Seat1' > > session-type = '' > > active = FALSE > > x11-display = '' > > x11-display-device = '' > > display-device = '/dev/pts/0' > > remote-host-name = '' > > is-local = TRUE > > on-since = '2013-07-22T14:09:31.717064Z' > > login-session-id = '4294967295' > > > > Session2: > > unix-user = '1000' > > realname = 'Martin Steigerwald' > > seat = 'Seat1' > > session-type = '' > > active = TRUE > > x11-display = ':0' > > x11-display-device = '/dev/tty7' > > display-device = '' > > remote-host-name = '' > > is-local = TRUE > > on-since = '2013-07-22T11:25:40.817811Z' > > login-session-id = '4294967295' > > Especially the output of consolekit is relevant, since that is currently > still used. As you have both a root and a user login, the policykit > checks work as designed. > So I'm closing the bug report.
Well, that might be technical correct, but it doesn´t solve my issue as an user. I want no confirmation dialog *and* dirmngr is dependency of kdepim module which I like to keep installed completely. Before I didn´t have the confirmation dialog. So from my user point of view this is well, probably not really a regression, but a change I did not ask for. As a user I do not care how the check is designed, I want it gone. It just doesn´t make any sense to me on a *laptop* with one keyboard attached. Especially as both sessions are on *one* seat, thus if I understand a seat correctly *one* combination of input devices and display which is usually used by *one* user. Any suggestion on how to get rid of it? I am also willing to carry this upstream if necessary. Cause usability wise this just doesn´t make any sense for a laptop. Not at all. IMO. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
signature.asc
Description: This is a digitally signed message part.
