mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2841] Firejail breaks fcitx input on Firefox #1779
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1779
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jwittlincohen on GitHub (Jul 8, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2841
I'm using firejail 0.9.5.8 on Debian Buster (10.0). Using the default profiles, firejail breaks fcitx input methods in both Firefox 67.0.4 and Chrome 75, by which I mean, entering the key combination to switch inputs (Ctrl + Space) does nothing. If I run either browser without firejail confinement, Ctrl + Space will switch to Pinyin input and allow me to type in Simplified Chinese.
I found a workaround for Chrome by searching this Github, namely adding "ignore nodbus" to google-chrome.local. However, "ignore nodbus" does not resolve the issue for Firefox and I'm not sure what else to try. I've provided the distribution-provided Firefox profile(s) and my local profile below.
firefox-common.profile (untouched from Debian install)
firefox-common.local
@rusty-snake commented on GitHub (Jul 8, 2019):
Since no one commenting here with an idea, I suggest you to try if one of the following works:
BTW:
ignore nou2fshould no be necessary except you setbrowser-disable-u2f yesin firejail.config. (Or is this default on debian, I know that there is some hardening on the default config in the debian package.)@jwittlincohen commented on GitHub (Jul 8, 2019):
Thanks for the suggestion! I can confirm that both
ignore protocolandignore nodbusare required for fcitx on Firefox.As for
nou2f, it is definitely required to use a Yubikey on Debian. The distribution provided firefox-common.profile and chromium-common.profile specifiesnodbusand?BROWSER_DISABLE_U2F: nou2fwhich breaks FIDO2/U2F support. I only began investigating the issue because I couldn't use my Yubikey in Firefox or Chrome with firejail. I might create a bug report on the Debian tracker for this issue. FIDO2/U2F Security keys enhance security by providing a strong second factor that thwarts phishing attacks. I don't see a good reason for firejail to break U2F security keys if it's possible to limit access to other USB devices while allowing U2F keys.Edit: I just checked https://github.com/netblue30/firejail/blob/master/etc/firefox-common.profile and it also has
?BROWSER_DISABLE_U2F: nou2f@zoenglinghou commented on GitHub (Jan 19, 2021):
@jwittlincohen sorry for bringing it up again. I tried putting
ignore protocolandignore nodbusin~/.config/firejail/firefox-common.localbutfcitxis not working (while directory whitelists in~/.config/firejail/firefox.localwork). Am I missing something here?Much appreciated ❤️
@rusty-snake commented on GitHub (Jan 19, 2021):
https://github.com/netblue30/firejail/wiki/Frequently-Asked-Questions#how-can-i-enable-fcitx (result from #3732)
@zoenglinghou commented on GitHub (Jan 19, 2021):
Yep, that just works! Thank you!
@ple1n commented on GitHub (Mar 24, 2023):
just a note, this solved my problem
its env equivalent in profile