fix(image): silence Chromium keyring prompt on the kiosk#222
Merged
privaloops merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
Without --password-store=basic, Chromium tries to reach the GNOME or KDE keyring on first launch and pops a "Use your keyring to store passwords?" dialog — which the kiosk has no keyboard to dismiss with. Forcing the basic file-backed store skips the keyring lookup entirely. Cookies and any saved credentials end up in ~/.chromium/<profile>/Login\ Data, plain on disk, which is fine for a single-tenant arcade appliance.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
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.
Without --password-store=basic, Chromium tries to reach the GNOME or
KDE keyring on first launch and pops a "Use your keyring to store
passwords?" dialog — which the kiosk has no keyboard to dismiss with.
Forcing the basic file-backed store skips the keyring lookup
entirely. Cookies and any saved credentials end up in
~/.chromium//Login\ Data, plain on disk, which is fine for
a single-tenant arcade appliance.