github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #1791] keepassxc: cannot open database (memory-deny-write-execute) #1213

New issue
Closed
opened 2026-05-05 07:40:13 -06:00 by gitea-mirror · 10 comments
gitea-mirror commented 2026-05-05 07:40:13 -06:00
Owner
Copy link

Originally created by @qazip on GitHub (Mar 1, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1791

Hello,

Please check this issue in the KeepassXC repo: https://github.com/keepassxreboot/keepassxc/issues/1582

I've found that whenever KeepassXC is ran under firejail, it doesn't work. This is the output:

Reading profile /etc/firejail/keepassxc.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 18812, child pid 18813
Private /etc installed in 7.05 ms
Child process initialized in 106.20 ms
qt5ct: using qt5ct plugin

(keepassxc:8): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /run/user/1000/bus: Permission denied
qt5ct: D-Bus system tray: no
libGL error: failed to open drm device: No such file or directory
libGL error: failed to load driver: i965

My firejail's version is the following:

firejail version 0.9.52

Compile time support:
	- AppArmor support is enabled
	- AppImage support is enabled
	- bind support is enabled
	- chroot support is enabled
	- file and directory whitelisting support is enabled
	- file transfer support is enabled
	- git install support is disabled
	- networking support is enabled
	- overlayfs support is enabled
	- private-home support is enabled
	- seccomp-bpf support is enabled
	- user namespace support is enabled
	- X11 sandboxing support is enabled
Originally created by @qazip on GitHub (Mar 1, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1791 Hello, Please check this issue in the KeepassXC repo: https://github.com/keepassxreboot/keepassxc/issues/1582 I've found that whenever KeepassXC is ran under firejail, it doesn't work. This is the output: ``` Reading profile /etc/firejail/keepassxc.profile Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-devel.inc Reading profile /etc/firejail/disable-passwdmgr.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/whitelist-var-common.inc Parent pid 18812, child pid 18813 Private /etc installed in 7.05 ms Child process initialized in 106.20 ms qt5ct: using qt5ct plugin (keepassxc:8): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /run/user/1000/bus: Permission denied qt5ct: D-Bus system tray: no libGL error: failed to open drm device: No such file or directory libGL error: failed to load driver: i965 ``` My firejail's version is the following: ``` firejail version 0.9.52 Compile time support: - AppArmor support is enabled - AppImage support is enabled - bind support is enabled - chroot support is enabled - file and directory whitelisting support is enabled - file transfer support is enabled - git install support is disabled - networking support is enabled - overlayfs support is enabled - private-home support is enabled - seccomp-bpf support is enabled - user namespace support is enabled - X11 sandboxing support is enabled ```
gitea-mirror 2026-05-05 07:40:13 -06:00
  • closed this issue
  • added the
    bug
         label
gitea-mirror commented 2026-05-05 07:40:17 -06:00
Author
Owner
Copy link

@Vincent43 commented on GitHub (Mar 1, 2018):

You can try creating /etc/firejail/keepassxc.local file with noblacklist /run/user/*/bus line inside.

<!-- gh-comment-id:369741730 --> @Vincent43 commented on GitHub (Mar 1, 2018): You can try creating `/etc/firejail/keepassxc.local` file with `noblacklist /run/user/*/bus` line inside.
gitea-mirror commented 2026-05-05 07:40:19 -06:00
Author
Owner
Copy link

@Fred-Barclay commented on GitHub (Mar 2, 2018):

@qazip What version of firejail are you using?

<!-- gh-comment-id:369792139 --> @Fred-Barclay commented on GitHub (Mar 2, 2018): @qazip What version of firejail are you using?
gitea-mirror commented 2026-05-05 07:40:20 -06:00
Author
Owner
Copy link

@qazip commented on GitHub (Mar 2, 2018):

@Fred-Barclay, so sorry, I normally don't forget that. I've edited my post with my firejail version. It's 0.9.52.

<!-- gh-comment-id:369857305 --> @qazip commented on GitHub (Mar 2, 2018): @Fred-Barclay, so sorry, I normally don't forget that. I've edited my post with my firejail version. It's 0.9.52.
gitea-mirror commented 2026-05-05 07:40:22 -06:00
Author
Owner
Copy link

@Vincent43 commented on GitHub (Mar 2, 2018):

@qazip did you tried what I suggested?

<!-- gh-comment-id:369964842 --> @Vincent43 commented on GitHub (Mar 2, 2018): @qazip did you tried what I suggested?
gitea-mirror commented 2026-05-05 07:40:25 -06:00
Author
Owner
Copy link

@qazip commented on GitHub (Mar 2, 2018):

@Vincent43, I have now. It's still giving me the error:

Reading profile /etc/firejail/keepassxc.profile
Reading profile /etc/firejail/keepassxc.local
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 17583, child pid 17585
Private /etc installed in 5.13 ms
Child process initialized in 53.46 ms
qt5ct: using qt5ct plugin

(keepassxc:8): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-FyLuCtiUoy: Connection refused
qt5ct: D-Bus system tray: no
libGL error: failed to open drm device: No such file or directory
libGL error: failed to load driver: i965

My keepassxc.local only has noblacklist /run/user/*/bus, nothing else.

<!-- gh-comment-id:370050876 --> @qazip commented on GitHub (Mar 2, 2018): @Vincent43, I have now. It's still giving me the error: ``` Reading profile /etc/firejail/keepassxc.profile Reading profile /etc/firejail/keepassxc.local Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-devel.inc Reading profile /etc/firejail/disable-passwdmgr.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/whitelist-var-common.inc Parent pid 17583, child pid 17585 Private /etc installed in 5.13 ms Child process initialized in 53.46 ms qt5ct: using qt5ct plugin (keepassxc:8): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-FyLuCtiUoy: Connection refused qt5ct: D-Bus system tray: no libGL error: failed to open drm device: No such file or directory libGL error: failed to load driver: i965 ``` My keepassxc.local only has `noblacklist /run/user/*/bus`, nothing else.
gitea-mirror commented 2026-05-05 07:40:26 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Mar 2, 2018):

Failed to connect to socket /tmp/dbus-FyLuCtiUoy: Connection refused
should be fixed by commenting net none and blacklist /run/user/*/bus

libGL error: failed to open drm device: No such file or directory
is expected due to no3d

<!-- gh-comment-id:370069396 --> @SkewedZeppelin commented on GitHub (Mar 2, 2018): `Failed to connect to socket /tmp/dbus-FyLuCtiUoy: Connection refused` should be fixed by commenting `net none` and `blacklist /run/user/*/bus` `libGL error: failed to open drm device: No such file or directory` is expected due to `no3d`
gitea-mirror commented 2026-05-05 07:40:27 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (Mar 5, 2018):

@qazip another line that is known to cause problems is memory-deny-write-execute (see discussion in #1631).

Does firejail --ignore=memory-deny-write-execute keepassxc restore functionality?

<!-- gh-comment-id:370574278 --> @smitsohu commented on GitHub (Mar 5, 2018): @qazip another line that is known to cause problems is `memory-deny-write-execute` (see discussion in #1631). Does `firejail --ignore=memory-deny-write-execute keepassxc` restore functionality?
gitea-mirror commented 2026-05-05 07:40:28 -06:00
Author
Owner
Copy link

@elvetemedve commented on GitHub (Mar 6, 2018):

@smitsohu I'm running Arch Linux and have the same issue. Removing the memory-deny-write-execute option made it working again.

<!-- gh-comment-id:370753591 --> @elvetemedve commented on GitHub (Mar 6, 2018): @smitsohu I'm running Arch Linux and have the same issue. Removing the `memory-deny-write-execute` option made it working again.
gitea-mirror commented 2026-05-05 07:40:29 -06:00
Author
Owner
Copy link

@qazip commented on GitHub (Mar 6, 2018):

Yes indeed, that seems to work. It would be good if someone made a PR to keepassxc's profile.. Should I close this issue?

<!-- gh-comment-id:370767428 --> @qazip commented on GitHub (Mar 6, 2018): Yes indeed, that seems to work. It would be good if someone made a PR to keepassxc's profile.. Should I close this issue?
gitea-mirror commented 2026-05-05 07:40:30 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (Mar 6, 2018):

@qazip @elvetemedve Thanks, I think we can close the issue then.

It is already fixed for the upcoming release in 38e798e2d6.

<!-- gh-comment-id:370781831 --> @smitsohu commented on GitHub (Mar 6, 2018): @qazip @elvetemedve Thanks, I think we can close the issue then. It is already fixed for the upcoming release in 38e798e2d66a50a2de0bc4f257e75c7bd57142ea.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1213
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?