Bug#780781: systemd: if fsck is needed, systemd fails to start lighdm, network and other services

[Michael Biebl]

Control: tags -1 + moreinfo

Hi

On Thu, 19 Mar 2015 19:49:59 +0800 "gustavo panizzo \(gfa\)"
<gfa at zumbi.com.ar> wrote:
> Package: systemd
> Version: 215-12
> Severity: normal
> 
> if my laptop fails to resume (or next boot after a crash) systemd will fsck the filesystem, that's ok
> but after that it won't start ligtdm, networking and other services.
> i could manually start all services, but is just easier to reboot. 100%
> of the time the next boot will be ok.
> 
> i'm running reportbug after a failed resume and you can see not all
> services are up. i manually started networking so i can send this bug
> report.

Do you still run into this issue?
If so, I assume you are logging into the console?
Can you attach the output of systemctl status and journalctl -alb in
this case.

Thanks
Michael

-- 
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: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161221/ac5f7848/attachment.sig>