Bug#844785: systemd prevents polkit from working properly

[Adam Bolte]

On 20/11/16 15:13, Raphaël Halimi wrote:
> Control: retitle -1 systemd-shim not fully compatible with systemd
> 232 Control: affects -1 policykit-1 policykit-1-gnome mate-polkit
>
> Le 20/11/2016 à 04:21, Adam Bolte a écrit : Right. I retitled the bug
> to more precisely describe the problem, and added affected packages
> (at least the ones I tried...

Thanks! That's a great idea.


> Yeah, that's basically what I did, except with systemd 231-10.

I saw 231-10, but wasn't sure it ever made it to testing (possibly
suggesting a problem with it). I could be mistaken, but I never had it
installed on my machine at least, and I do upgrade reasonably often.


> I then pinned systemd with a preferences file, and now apt is
> holding libpam-systemd and libsystemd0 too, but accepted to upgrade
> udev and libudev1 (I initially thought that there would be a
> versioned dependency between the two sets, but that's not the case).
> So in fact, only those three packages (four in case of multi-arch)
> have to be downgraded to restore the system to a functional state.

Thanks for reporting. I'll just pin those packages for now too then.

Cheers,
Adam




signature.asc
Description: OpenPGP digital signature

Bug#844785: systemd prevents polkit from working properly

[Raphaël Halimi]

Control: retitle -1 systemd-shim not fully compatible with systemd 232
Control: affects -1 policykit-1 policykit-1-gnome mate-polkit

Le 20/11/2016 à 04:21, Adam Bolte a écrit :
> It took about an hour to find this bug report, since I was looking for
> changes related to consolekit, polkit, pam, etc. I've been using using
> sysvinit-core to avoid systemd issues (systemd doesn't even boot for me
> for some reason I don't care to investigate), so it didn't immediately
> occur to me to look at possible systemd libraries changes. I wouldn't be
> surprised if a lot of people hitting this don't know to look here.

Right. I retitled the bug to more precisely describe the problem, and
added affected packages (at least the ones I tried, I guess lxsession
(which provides lxpolkit) is affected too, but I didn't actually try it,
so I'll let that to someone who actually did, and can confirm that LXDE
loses functionality as well).

I'm worried though, because systemd-shim is orphaned now.

> As a work-around, look through the log to get the systemd-related
> packages which were upgraded:
> 
> $ grep 232-3 /var/log/dpkg.log | grep ' status installed ' | \
>   cut -d ' ' -f 5 | sort | uniq
> libpam-systemd:amd64
> libsystemd0:amd64
> libsystemd0:i386
> libudev1:amd64
> libudev1:i386
> libudev-dev:amd64
> systemd:amd64
> udev:amd64
> 
> Then head over to http://snapshot.debian.org/package/systemd/231-9/ and
> download the debs for each of the above. Check the hashes, and install:
> 
> # dpkg -i *.deb
> 
> Reboot, and now you can shutdown via lightdm, mount drives, etc as normal.

Yeah, that's basically what I did, except with systemd 231-10. I then
pinned systemd with a preferences file, and now apt is holding
libpam-systemd and libsystemd0 too, but accepted to upgrade udev and
libudev1 (I initially thought that there would be a versioned dependency
between the two sets, but that's not the case). So in fact, only those
three packages (four in case of multi-arch) have to be downgraded to
restore the system to a functional state.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#844785: systemd prevents polkit from working properly

[Adam Bolte]

It took about an hour to find this bug report, since I was looking for
changes related to consolekit, polkit, pam, etc. I've been using using
sysvinit-core to avoid systemd issues (systemd doesn't even boot for me
for some reason I don't care to investigate), so it didn't immediately
occur to me to look at possible systemd libraries changes. I wouldn't be
surprised if a lot of people hitting this don't know to look here.

On Sat, 19 Nov 2016 09:35:32 -0300 Felipe Sateler 
wrote:
> Because you use sysvinit, this means the systemd-shim compatibility
> layer is not working for 232. I'm reassigning so that it can be fixed.

Confirming this all seems accurate. I too am using systemd-shim (which
was not updated in a while.

As a work-around, look through the log to get the systemd-related
packages which were upgraded:

$ grep 232-3 /var/log/dpkg.log | grep ' status installed ' | \
  cut -d ' ' -f 5 | sort | uniq
libpam-systemd:amd64
libsystemd0:amd64
libsystemd0:i386
libudev1:amd64
libudev1:i386
libudev-dev:amd64
systemd:amd64
udev:amd64

Then head over to http://snapshot.debian.org/package/systemd/231-9/ and
download the debs for each of the above. Check the hashes, and install:

# dpkg -i *.deb

Reboot, and now you can shutdown via lightdm, mount drives, etc as normal.

Cheers,
Adam



signature.asc
Description: OpenPGP digital signature

Bug#844785: systemd prevents polkit from working properly

[Felipe Sateler]

Control: reassign -1 systemd-shim 10-2

On 19 November 2016 at 00:18, Raphaël Halimi  wrote:
> Package: systemd
> Version: 232-1
>
> Since systemd 232, lightdm's menu entries to
> shutdown/reboot/suspend/hibernate the system are grayed out.
>
> Furthermore, GNOME polkit authentication agent fails to start (I use
> openbox, with the agent normally started from
> ~/.config/openbox/autostart). When manually run in a terminal, it
> immediately exits with the error message:
>
> "polkit-gnome-1-WARNING **: Unable to determine the session we are in:
> No session for pid ..."
>
> Downgrading systemd/libsystemd0/libpam-systemd to version 231-10 fixes
> the problem (I also tried 232-1 and 232-2, but they didn't work either).

Because you use sysvinit, this means the systemd-shim compatibility
layer is not working for 232. I'm reassigning so that it can be fixed.


-- 

Saludos,
Felipe Sateler

Bug#844785: systemd prevents polkit from working properly

[Raphaël Halimi]

Sorry, I forgot to mention that I use sysv init.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#844785: systemd prevents polkit from working properly

[Raphaël Halimi]

Package: systemd
Version: 232-1

Since systemd 232, lightdm's menu entries to
shutdown/reboot/suspend/hibernate the system are grayed out.

Furthermore, GNOME polkit authentication agent fails to start (I use
openbox, with the agent normally started from
~/.config/openbox/autostart). When manually run in a terminal, it
immediately exits with the error message:

"polkit-gnome-1-WARNING **: Unable to determine the session we are in:
No session for pid ..."

Downgrading systemd/libsystemd0/libpam-systemd to version 231-10 fixes
the problem (I also tried 232-1 and 232-2, but they didn't work either).

Sorry for the vague bug title (and the probably wrong binary package),
but it's the best I can do since I'm not at all familiar with the way
systemd/polkit/pam/lightdm/whatever interact with each other.

Also, I just spotted this bug today despite the fact that it was
introduced two weeks ago, because I rarely shutdown my sid box.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature