New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gdm: 3.34.1 -> 3.36.3 #94656
gdm: 3.34.1 -> 3.36.3 #94656
Conversation
Do we actually have |
From the other changes, it might be nice to add |
Yeah, it should be available when
So sort of an accident, but means we don't need to keep plymouth in the closure I guess.
Looks like they simply make sure user sessions aren't launched on GDM's designated VT (7 in our case). Don't think that should affect us at all tbh as it's already fairly unlikely for GDM to launch a session on VT7 in the first place. |
Just want to mention we had an issue in lightdm where plymouth had to be hardcoded https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/display-managers/lightdm/default.nix#L95. Not sure if that will spark the same issue here though, but I think it's possible to be likely. |
I just tried this on my machine and it locks up with plymouth. So I think it needs to be hardcoded. |
d5632c7
to
2c9d28a
Compare
@worldofpeace I have hardcoded the path to plymouth binary within the |
@GrahamcOfBorg test gnome3 gnome3-xorg |
gdm is updated now. |
Motivation for this change
Version bump.
Changelog:
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)CC: @worldofpeace @jtojnar