Bug#727645: polkit-kde-1: requires root password for hibernate, wrongly reports other users are logged on
Hi!
Am Freitag, 25. Oktober 2013, 15:27:20 schrieb Johannes Rohr:
> On Fr, Okt 25, 2013 at 01:38:45 +0300, Sami Erjomaa wrote:
> > Hi,
> >
> > I have this same problem and I encountered it after I started using
> > systemd.
> I also started using systemd recentlcy and I suspected that this might
> be related.
>
> > For me the dialog shows org.freedesktop.login1.hibernate-multiple-sessions
> > as the reason.
> >
> > My understanding is that it is dirmngr that causes this.
> >
> > loginctl shows:
> > SESSION UID USER SEAT
> > c1 112 dirmngr
> > c2 1000 durin seat0
> >
> > if I kill dirmngr the dialog requesting root password doesn't pop up.
>
> I'll try next time if I can reproduce this.
Please see:
#717731
upower: authentification is required for hibernating while other users are
logged in
http://bugs.debian.org/717731
#717554
systemd: authentification is required for hibernating while other users are
logged in
http://bugs.debian.org/717554
So this is still unsolved. I am not using / testing systemd for that reason
since months.
Please test the solution / workaround Michael proposed in:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717554#32
I tried:
merkaba:~> cat /etc/polkit-1/localauthority/50-
local.d/org.freedesktop.upower.pkla
[Suspend/hibernate permissions]
Identity=unix-group:sudo
Action=org.freedesktop.upower.hibernate;org.freedesktop.upower.suspend
ResultAny=yes
ResultInactive=yes
ResultActive=yes
with my users in sudo group and still got the annoying error and it didn´t
work for me.
Then I gave upon it.
I do think asking a user for password confirmation on hibernation after he just
triggered the action just due to a background service having opened another
session is broken. It may make sense if mutiple real users are logged in at
the same time on *different* seats. But even then I don´t get why a password
should be required. A dialog telling that other users might still be using the
machine would be enough IMHO. Or the other user that might still be logged in
might be asked. Anyway: For any single-seat setup asking the user for
confirmation just doesn´t make sense.
But well, I argued this already in the other bug reports.
Maybe its a good idea to merge the bug reports regarding that issue. Actually
I expect more of these to come if other people try systemd with KDE and do not
look for duplicates. It will happen with any systemd and full KDE setup.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Reply to: