You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug and expected behavior
If the current host X11 session is not display 0 (when the "DISPLAY" env variable is not set to ":0"), some gui applications that are running within firejail do not accept keyboard input. If X11 is running with DISPLAY id 0, then things work as expected.
No profile and disabling firejail
What changed calling firejail --noprofile /path/to/program in a terminal?
Nothing changes for the same applications, they still do not accept keyboard input.
What changed calling the program by path (check which <program> or firejail --list while the sandbox is running)?
Running the program without firejail works as expected.
Reproduce
Steps to reproduce the behavior:
Start host X11 without using DISPLAY id 0 startx -- :1
Start a gui application with firejail firejail chromium or firejail firefox
or firejail vivaldi-stable
Attempt to type in the gui application
Environment
Linux distribution and version (ie output of lsb_release -a, screenfetch or cat /etc/os-release)
ArchLinux x86_64
Firejail version (output of firejail --version) exclusive or used git commit (git rev-parse HEAD)
firejail version 0.9.62.4
Additional context
Some other gui applications accept keyboard input (such as alacritty, xterm,
kitty, kid3-qt, gimp, audacity), and some do not (such as gnucash, vivaldi,
firefox, chromium) when the DISPLAY env is not 0.
Checklist
The upstream profile (and redirect profile if exists) have no changes fixing it.
The program has a profile. (If not, request one in # 1139)
Programs needed for interaction are listed in the profile.
A short search for duplicates was performed.
If it is a AppImage, --profile=PROFILENAME is used to set the right profile.
EDIT: I forgot to mention this does occur in the case where there are multiple Linux X11 sessions on the same computer. The first will have DISPLAY set to ":0", and the latter session will have a different id. It is in this situation where this problem can occur.
The text was updated successfully, but these errors were encountered:
Bug and expected behavior
If the current host X11 session is not display 0 (when the "DISPLAY" env variable is not set to ":0"), some gui applications that are running within firejail do not accept keyboard input. If X11 is running with DISPLAY id 0, then things work as expected.
No profile and disabling firejail
firejail --noprofile /path/to/program
in a terminal?Nothing changes for the same applications, they still do not accept keyboard input.
which <program>
orfirejail --list
while the sandbox is running)?Running the program without firejail works as expected.
Reproduce
Steps to reproduce the behavior:
startx -- :1
firejail chromium
orfirejail firefox
or
firejail vivaldi-stable
Environment
lsb_release -a
,screenfetch
orcat /etc/os-release
)ArchLinux x86_64
firejail --version
) exclusive or used git commit (git rev-parse HEAD
)firejail version 0.9.62.4
Additional context
Some other gui applications accept keyboard input (such as alacritty, xterm,
kitty, kid3-qt, gimp, audacity), and some do not (such as gnucash, vivaldi,
firefox, chromium) when the DISPLAY env is not 0.
Checklist
--profile=PROFILENAME
is used to set the right profile.debug output
EDIT: I forgot to mention this does occur in the case where there are multiple Linux X11 sessions on the same computer. The first will have DISPLAY set to ":0", and the latter session will have a different id. It is in this situation where this problem can occur.
The text was updated successfully, but these errors were encountered: