github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #2974] meld.profile missing access to dconf #1860

New issue

Closed

opened 2026-05-05 08:31:48 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 08:31:48 -06:00

Owner

Originally created by @felixwiemuth on GitHub (Sep 22, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2974

Meld uses dconf to store its settings. I had to add
noblacklist ${HOME}/.config/dconf to meld.local so that settings can be applied and persisted.

Originally created by @felixwiemuth on GitHub (Sep 22, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2974 Meld uses dconf to store its settings. I had to add `noblacklist ${HOME}/.config/dconf` to `meld.local` so that settings can be applied and persisted.

gitea-mirror closed this issue

2026-05-05 08:31:49 -06:00

gitea-mirror commented

2026-05-05 08:31:51 -06:00

Author

Owner

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

For my it's working without that fix. Normaly dconf is accessed over dbus.

which firejail version and distro are you on?

firejail: git, OS: Fedora 30.
meld.local:

ignore private-bin
ignore private-tmp

include whitelist-var-common.inc

net none
protocol unix

@rusty-snake commented on GitHub (Sep 22, 2019): For my it's working without that fix. Normaly dconf is accessed over dbus. which firejail version and distro are you on? firejail: git, OS: Fedora 30. meld.local: ``` ignore private-bin ignore private-tmp include whitelist-var-common.inc net none protocol unix ```

gitea-mirror commented

2026-05-05 08:31:52 -06:00

Author

Owner

@felixwiemuth commented on GitHub (Sep 22, 2019):

Arch Linux, firejail 0.9.60.

I guessed that dbus could be a problem as well, is it using /tmp to communicate? Because then one actually would nede the ignore private-tmp.

However, now it suddenly works even without additions in meld.local, even though before this change (noblacklist ${HOME}/.config/dconf) made it work...

@felixwiemuth commented on GitHub (Sep 22, 2019): Arch Linux, firejail 0.9.60. I guessed that dbus could be a problem as well, is it using /tmp to communicate? Because then one actually would nede the `ignore private-tmp`. However, now it suddenly works even without additions in `meld.local`, even though before this change (`noblacklist ${HOME}/.config/dconf`) made it work...

gitea-mirror commented

2026-05-05 08:31:53 -06:00

Author

Owner

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

BTW: grep "^blacklist \${HOME}/.config/dconf" /etc/firejail/* , dconf is never blacklisted.

@rusty-snake commented on GitHub (Sep 22, 2019): BTW: `grep "^blacklist \${HOME}/.config/dconf" /etc/firejail/* `, dconf is never blacklisted.

gitea-mirror commented

2026-05-05 08:31:54 -06:00

Author

Owner

@Vincent43 commented on GitHub (Sep 22, 2019):

@felixwiemuth modern dbus is usually using /run/user/$UID/bus to communicate

@Vincent43 commented on GitHub (Sep 22, 2019): @felixwiemuth modern dbus is usually using `/run/user/$UID/bus` to communicate

gitea-mirror commented

2026-05-05 08:31:56 -06:00

Author

Owner

@felixwiemuth commented on GitHub (Sep 24, 2019):

Thanks for the comments, probably it is difficult to identify what the actual issue was here.

Some additional observations:

Same issue in a firejail --private sandbox (this suggests that it actually could have been some sandboxing issue)
When deleting ~/.config/dconf/user the file is recreated when starting meld and changing settings

If there are no more ideas for now I guess this can be closed.

@felixwiemuth commented on GitHub (Sep 24, 2019): Thanks for the comments, probably it is difficult to identify what the actual issue was here. Some additional observations: - Same issue in a `firejail --private` sandbox (this suggests that it actually could have been some sandboxing issue) - When deleting `~/.config/dconf/user` the file is recreated when starting meld and changing settings If there are no more ideas for now I guess this can be closed.

gitea-mirror referenced this issue

2026-05-05 10:13:39 -06:00

[PR #1860] [MERGED] syntax fixup #4095

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#1860

No description provided.

Rows
Columns