nixpkgs/nixos/modules/system
Tor Hedin Brønner 5924bab20b nixos/plymouth: do not order plymouth-quit after display-manager
GDM now specifies ordering between `plymouth-quit` and `display-manager`:
9be5321097c16

This causes an ordering cycle between GDM and plymouth-quit which can result in
systemd breaking GDM:
```
plymouth-quit.service: Job display-manager.service/start deleted to break
                       ordering cycle starting with plymouth-quit.service/start
```

Not sure how often this triggers, as I've run my system with plymouth and
9be5321097c16 without any issues. But I did catch a VM doing this.

NOTE: I also tried to remove the ordering in GDM to see if plymouth managed to
live longer, but it didn't seem to help. So I opted to stick as close to
upstream (upstream GDM specifies ordering, but plymouth does not).
2019-10-14 13:08:51 +02:00
..
activation Revert "Merge #67232: machinectl compliant NixOS installation" 2019-10-07 20:56:59 +02:00
boot nixos/plymouth: do not order plymouth-quit after display-manager 2019-10-14 13:08:51 +02:00
etc Revert "Merge pull request #54980 from danbst/etc-relative" (#56507) 2019-02-28 07:48:40 +02:00