[GH-ISSUE #2408] chromium: cannot launch without --password-store=basic #1608

Closed
opened 2026-05-05 08:15:47 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @Futureknows on GitHub (Feb 16, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2408

Chromium won't launch in Firejail and passes error below.
Temporary workaround is appending --password-store=basic to Chromium command line.

$ firejail chromium-browser
Reading profile /usr/local/etc/firejail/chromium-browser.profile
Reading profile /usr/local/etc/firejail/chromium.profile
Reading profile /usr/local/etc/firejail/globals.local
Reading profile /usr/local/etc/firejail/chromium-common.profile
Reading profile /usr/local/etc/firejail/disable-common.inc
Reading profile /usr/local/etc/firejail/disable-devel.inc
Reading profile /usr/local/etc/firejail/disable-interpreters.inc
Reading profile /usr/local/etc/firejail/disable-programs.inc
Reading profile /usr/local/etc/firejail/whitelist-common.inc
Reading profile /usr/local/etc/firejail/whitelist-var-common.inc
Parent pid 25883, child pid 25884

Child process initialized in 1077.77 ms
Warning: an existing sandbox was detected. /usr/bin/chromium-browser will run without any additional sandboxing features
[45:45:0216/133437.956156:ERROR:vaapi_wrapper.cc(343)] This build of Chromium requires VA-API version 1.3, system version: 1.4
[45:45:0216/133437.977308:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
Originally created by @Futureknows on GitHub (Feb 16, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2408 Chromium won't launch in Firejail and passes error below. Temporary workaround is appending `--password-store=basic` to Chromium command line. ``` $ firejail chromium-browser Reading profile /usr/local/etc/firejail/chromium-browser.profile Reading profile /usr/local/etc/firejail/chromium.profile Reading profile /usr/local/etc/firejail/globals.local Reading profile /usr/local/etc/firejail/chromium-common.profile Reading profile /usr/local/etc/firejail/disable-common.inc Reading profile /usr/local/etc/firejail/disable-devel.inc Reading profile /usr/local/etc/firejail/disable-interpreters.inc Reading profile /usr/local/etc/firejail/disable-programs.inc Reading profile /usr/local/etc/firejail/whitelist-common.inc Reading profile /usr/local/etc/firejail/whitelist-var-common.inc Parent pid 25883, child pid 25884 Child process initialized in 1077.77 ms Warning: an existing sandbox was detected. /usr/bin/chromium-browser will run without any additional sandboxing features [45:45:0216/133437.956156:ERROR:vaapi_wrapper.cc(343)] This build of Chromium requires VA-API version 1.3, system version: 1.4 [45:45:0216/133437.977308:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process. ```
gitea-mirror 2026-05-05 08:15:47 -06:00
  • closed this issue
  • added the
    duplicate
    label
Author
Owner

@SkewedZeppelin commented on GitHub (Feb 17, 2019):

Can you try
firejail /usr/bin/chromium-browser

<!-- gh-comment-id:464402853 --> @SkewedZeppelin commented on GitHub (Feb 17, 2019): Can you try `firejail /usr/bin/chromium-browser`
Author
Owner

@chiraag-nataraj commented on GitHub (Feb 17, 2019):

@Futureknows Which version of chromium do you have?

<!-- gh-comment-id:464455265 --> @chiraag-nataraj commented on GitHub (Feb 17, 2019): @Futureknows Which version of `chromium` do you have?
Author
Owner

@Futureknows commented on GitHub (Feb 17, 2019):

71.0.3578.98.
It appears to have resolved after I applied solution from 2258.
I am guessing it may have been whitelist ~/.password-store

<!-- gh-comment-id:464513748 --> @Futureknows commented on GitHub (Feb 17, 2019): 71.0.3578.98. It appears to have resolved after I applied solution from [2258](https://github.com/netblue30/firejail/issues/2258#issuecomment-439724079). I am guessing it may have been `whitelist ~/.password-store`
Author
Owner

@chiraag-nataraj commented on GitHub (Feb 17, 2019):

I am guessing it may have been whitelist ~/.password-store

I don't know what it was, but unless you use pass as your password manager and want chromium to have access to it, that's not really doing anything.

<!-- gh-comment-id:464517743 --> @chiraag-nataraj commented on GitHub (Feb 17, 2019): > I am guessing it may have been `whitelist ~/.password-store` I don't know what it was, but unless you use `pass` as your password manager and want `chromium` to have access to it, that's not really doing anything.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1608
No description provided.