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

[gustavo panizzo (gfa)]

On Wed, Dec 21, 2016 at 06:15:25PM +0100, Michael Biebl wrote:
> 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?
yes, that's (was) correct

> Can you attach the output of systemctl status and journalctl -alb in
> this case.
I'm sorry but I no longer have access to that laptop, also I'm using
xdm now and it never failed (even after fsck)

feel free to close, as the issue was long time ago

thanks



-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa