Am 11.11.2013 23:31, schrieb Michael Stapelberg:
> Hi Julien,
> 
> Julien Puydt <julien.pu...@laposte.net> writes:
>> I was having issues with my computer lately:
>> - I wasn't able to mount USB keys anymore in thunar ;
>> - I wasn't able to shutdown/restart/hibernate anymore in xfce ;
>> - even when logged out, lightdm didn't allow shutdown/restart/hibernate.
>>
>> I searched around, and found bug #728361 against lightdm, where someone
>> mentioned kicking out libpam-systemd was fixing the lightdm problem.
>>
>> In fact all three problems listed above are fixed by removing
>> libpam-systemd, so this package breaks several unrelated things.
> In case you are not running logind, libpam-systemd should not do
> anything:
> 
>         /* Make this a NOP on non-logind systems */
>         if (!logind_running())
>                 return PAM_SUCCESS;
> 
> Can you check if /run/systemd/seats/ exists on your machine?
> 
> Also, can you outline the steps to reproduce this problem in a clean
> Debian wheezy VM please?

It's not a problem in libpam-systemd/systemd, it works as intended.

The issue is, that lightdm 1.8 no longer registers a ConsoleKit session
if it finds an active logind.
That means, from a CK pov the is is inactive/non-local.
E.g. policykit in unstable/testing still uses CK as backend. As a
result, all actions which require an active session are denied.

The XFCE/lightdm maintainers need to decide if they want to use
systemd-logind or stick with the obsolete CK.
If the former, they'll need to do the switch to logind in a coordinated
way, updating all affected components in the right order.

There is nothing really in libpam-systemd which needs to be fixed and
this bug should just be closed.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to