[GH-ISSUE #2355] chromium/firefox: file open dialog takes 5 seconds to list the files (dbus) #1569

Closed
opened 2026-05-05 08:13:42 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @jdevelop on GitHub (Jan 20, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2355

firejail 0.9.56-1 on Arch Linux ( Linux devbox 4.20.3-arch1-1-ARCH #1 SMP PREEMPT Wed Jan 16 22:38:58 UTC 2019 x86_64 GNU/Linux) and chromium 71.0.3578.98-3

With /etc/firejail/chromium.local

ignore nodbus

I can open a file upload dialog just fine, however the list of the files is populated with a significant delay.

I run Chromium as:

#!/bin/bash

ARGS="--force-device-scale-factor=2.0"

/sbin/firejail --debug --profile=/etc/firejail/chromium.profile --join-or-start="chromium" /sbin/chromium $ARGS $*

and the content of /etc/firejail/chromium.profile:

# Firejail profile for chromium
# Description: A web browser built for speed, simplicity, and security
# This file is overwritten after every install/update
# Persistent local customizations
include /etc/firejail/chromium.local
# Persistent global definitions
include /etc/firejail/globals.local

noblacklist ${HOME}/.cache/chromium
noblacklist ${HOME}/.config/chromium
noblacklist ${HOME}/.config/chromium-flags.conf

mkdir ${HOME}/.cache/chromium
mkdir ${HOME}/.config/chromium
whitelist ${HOME}/.cache/chromium
whitelist ${HOME}/.config/chromium
whitelist ${HOME}/.config/chromium-flags.conf

# private-bin chromium,chromium-browser,chromedriver

# Redirect
include /etc/firejail/chromium-common.profile
Originally created by @jdevelop on GitHub (Jan 20, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2355 `firejail 0.9.56-1` on Arch Linux ( `Linux devbox 4.20.3-arch1-1-ARCH #1 SMP PREEMPT Wed Jan 16 22:38:58 UTC 2019 x86_64 GNU/Linux`) and `chromium 71.0.3578.98-3` With `/etc/firejail/chromium.local` ``` ignore nodbus ``` I can open a file upload dialog just fine, however the list of the files is populated with a significant delay. I run Chromium as: ``` #!/bin/bash ARGS="--force-device-scale-factor=2.0" /sbin/firejail --debug --profile=/etc/firejail/chromium.profile --join-or-start="chromium" /sbin/chromium $ARGS $* ``` and the content of `/etc/firejail/chromium.profile`: ``` # Firejail profile for chromium # Description: A web browser built for speed, simplicity, and security # This file is overwritten after every install/update # Persistent local customizations include /etc/firejail/chromium.local # Persistent global definitions include /etc/firejail/globals.local noblacklist ${HOME}/.cache/chromium noblacklist ${HOME}/.config/chromium noblacklist ${HOME}/.config/chromium-flags.conf mkdir ${HOME}/.cache/chromium mkdir ${HOME}/.config/chromium whitelist ${HOME}/.cache/chromium whitelist ${HOME}/.config/chromium whitelist ${HOME}/.config/chromium-flags.conf # private-bin chromium,chromium-browser,chromedriver # Redirect include /etc/firejail/chromium-common.profile ```
gitea-mirror 2026-05-05 08:13:42 -06:00
Author
Owner

@chiraag-nataraj commented on GitHub (Jan 20, 2019):

What happens if you re-enable nodbus?

<!-- gh-comment-id:455877992 --> @chiraag-nataraj commented on GitHub (Jan 20, 2019): What happens if you re-enable `nodbus`?
Author
Owner

@jdevelop commented on GitHub (Jan 20, 2019):

  • with nodbus enabled - chrome is frozen for 10-15 seconds, can't click anywhere, can't drag the dialog window, can't close it.
  • with nodbus disabled - chrome is operable, the file dialog shows no files for ~5 seconds, then renders the list of the files.
<!-- gh-comment-id:455878587 --> @jdevelop commented on GitHub (Jan 20, 2019): * with `nodbus` enabled - chrome is frozen for 10-15 seconds, can't click anywhere, can't drag the dialog window, can't close it. * with `nodbus` disabled - chrome is operable, the file dialog shows no files for ~5 seconds, then renders the list of the files.
Author
Owner

@chiraag-nataraj commented on GitHub (Jan 20, 2019):

Hmm, I see. Interestingly, nodbus works just fine on my system, but I'm on Debian...

Easiest way to debug is to copy the contents of /etc/firejail/chromium-common.profile into your local profile, comment everything out, and start uncommenting things until chromium breaks again.

<!-- gh-comment-id:455879089 --> @chiraag-nataraj commented on GitHub (Jan 20, 2019): Hmm, I see. Interestingly, `nodbus` works just fine on my system, but I'm on Debian... Easiest way to debug is to copy the contents of `/etc/firejail/chromium-common.profile` into your local profile, comment everything out, and start uncommenting things until `chromium` breaks again.
Author
Owner

@smitsohu commented on GitHub (Jan 20, 2019):

Maybe related to #2258

<!-- gh-comment-id:455884006 --> @smitsohu commented on GitHub (Jan 20, 2019): Maybe related to #2258
Author
Owner

@jdevelop commented on GitHub (Jan 20, 2019):

Well, in my case it does launch, no matter whether nodbus is enabled or not. There's something else going on.

<!-- gh-comment-id:455884190 --> @jdevelop commented on GitHub (Jan 20, 2019): Well, in my case it does launch, no matter whether `nodbus` is enabled or not. There's something else going on.
Author
Owner

@jdevelop commented on GitHub (Jan 20, 2019):

Just checked with the firefox - it behaves exactly the same, perhaps the issue is not related to chromium, but to the GTK file chooser dialog?

<!-- gh-comment-id:455884514 --> @jdevelop commented on GitHub (Jan 20, 2019): Just checked with the firefox - it behaves exactly the same, perhaps the issue is not related to chromium, but to the GTK file chooser dialog?
Author
Owner

@Fred-Barclay commented on GitHub (Jan 20, 2019):

Similar related to #2324 ?

<!-- gh-comment-id:455893545 --> @Fred-Barclay commented on GitHub (Jan 20, 2019): ~~Similar~~ related to #2324 ?
Author
Owner

@rusty-snake commented on GitHub (Sep 10, 2019):

@jdevelop still an issue?

<!-- gh-comment-id:529918061 --> @rusty-snake commented on GitHub (Sep 10, 2019): @jdevelop still an issue?
Author
Owner

@jdevelop commented on GitHub (Sep 10, 2019):

Absolutely not!

<!-- gh-comment-id:530128955 --> @jdevelop commented on GitHub (Sep 10, 2019): Absolutely not!
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#1569
No description provided.