diff options
| author | Tor Hedin Brønner <torhedinbronner@gmail.com> | 2019-10-14 11:36:35 +0200 |
|---|---|---|
| committer | Tor Hedin Brønner <torhedinbronner@gmail.com> | 2019-10-14 13:08:51 +0200 |
| commit | 5924bab20b8bc5470b8e22b02c6655183150f86b (patch) | |
| tree | 52e3918c67ef1cb9b9f38f9d8a60230c0d1ce42f /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 1f7b1cf5813fc7cb75dbe438b9aa35a3000bfca9 (diff) | |
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).
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions