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

[Michael Biebl]

Am 24.07.2014 22:59, schrieb 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.)

If you want a verbose boot, you can remove "quiet" from the kernel
command line.

Can you boot with "systemd.log_level=debug" on the kernel command line
and send me the output of "journalctl -alb".

Do you have any mount points in /etc/fstab which are not accessible
during boot?
Systemd has a 90 secs timeout for those.









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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140724/61b31c3b/attachment-0002.sig>