Bug#755904: libpam-systemd: error in log after upgrade

[Benoit Friry]

>>> After a reboot your problem will be gone.

No more error in log after reboot. Bug report can be closed.

>> Is there any other way to fix that without rebooting?
> 
> Unfortunately not. The new logind requires systemd as PID 1, which
> means you need to reboot.

Not a good news. :(

I used the opportunity of rebooting to test systemd
(init=/bin/systemd). I hope next upgrade will not need rebooting.

(First impression is rather bad: boot is slower, boot messages are
unreadable, and password prompt to luksOpen is hidden.)

Many thanks,
Benoit