Add reboot to linux unlock script #23382
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dantecatalfamo
had a problem deploying
to
Docker Hub
GitHub Actions
Error
dantecatalfamo
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
dantecatalfamo
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#22437
There is a bug in Ubuntu 24.04's distribution of GDM that prevents it from starting correctly and displaying a prompt to the user if
/etc/nologinis present. This issue is not present on the current release of Fedora, meaning it is Ubuntu specific.The way we lock users out is by manually creating the
nologinfile and then masking thesystemd-user-sessionssystemd unit, which creates the file on shutdown and deletes it on startup. This will cause a PAM policy to fail and prevents anyone from logging in. When we unlock the system we delete thenologinfile, unmask thesystemd-user-sessionsunit, and manually run the binary that it should start.This process removes the cause of the GDM bug, but we need to reboot the machine to get GDM working again.
While I have not yet been able to determine the exact cause of the bug, this fix will prevent the user from being stuck with a black screen once the machine is unlocked.
This fix will not remedy GDM showing a black screen upon being locked, it only ensures that the user isn't stuck having to manually reboot the machine once it's unlocked.
We should check back on this soon to see if the bug gets been fixed upstream.
If some of the following don't apply, delete the relevant line.
changes/,orbit/changes/oree/fleetd-chrome/changes.See Changes files for more information.