github-starred/firejail

Fork 0

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

[GH-ISSUE #1793] ktorrent: configuration does not persist #1215

New issue

Open

opened 2026-05-05 07:40:14 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 07:40:14 -06:00

Owner

Originally created by @zorates on GitHub (Mar 2, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1793

firejail version 0.9.52
ktorrent 5.1.0

Launching firejail ktorrent with the default profile in /etc/firejail/ktorrent.profile, changing some settings in ktorrent and clicking apply produces the following error on the console:

Qt Warning: Couldn't write "/home/myuser/.config/ktorrentrc" . Disk full?

No error when launching with the --noprofile argument however.

I checked ktorrent.profile and it contains the following lines:

noblacklist ${HOME}/.config/ktorrentrc
whitelist ${HOME}/.config/ktorrentrc

so it appears the file is properly whitelisted, but it still doesn't work.

Originally created by @zorates on GitHub (Mar 2, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1793 firejail version 0.9.52 ktorrent 5.1.0 Launching `firejail ktorrent` with the default profile in /etc/firejail/ktorrent.profile, changing some settings in ktorrent and clicking apply produces the following error on the console: > Qt Warning: Couldn't write "/home/myuser/.config/ktorrentrc" . Disk full? No error when launching with the `--noprofile` argument however. I checked ktorrent.profile and it contains the following lines: > noblacklist ${HOME}/.config/ktorrentrc > whitelist ${HOME}/.config/ktorrentrc so it appears the file is properly whitelisted, but it still doesn't work.

gitea-mirror added the

information_old

label 2026-05-05 07:40:14 -06:00

gitea-mirror commented

2026-05-05 07:40:17 -06:00

Author

Owner

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

G'day @zorates
Do you know what those settings are you changed in ktorrent?
Thanks!
Fred

@Fred-Barclay commented on GitHub (Mar 3, 2018): G'day @zorates Do you know what those settings are you changed in ktorrent? Thanks! Fred

gitea-mirror commented

2026-05-05 07:40:19 -06:00

Author

Owner

@zorates commented on GitHub (Mar 3, 2018):

For example the 'Default save location' or the the 'Maximum upload speed'.

I first ran ktorrent without firejail if that makes any difference, so the ktorrentrc file already existed and contained my initial setup. I then started running it in firejail, without any apparent issues, until I tried to change to above settings and notice that they don't survive a restart. This lead me to investigate the cause, which turned out to be firejail.

@zorates commented on GitHub (Mar 3, 2018): For example the 'Default save location' or the the 'Maximum upload speed'. I first ran ktorrent without firejail if that makes any difference, so the `ktorrentrc` file already existed and contained my initial setup. I then started running it in firejail, without any apparent issues, until I tried to change to above settings and notice that they don't survive a restart. This lead me to investigate the cause, which turned out to be firejail.

gitea-mirror commented

2026-05-05 07:40:21 -06:00

Author

Owner

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

I see the same with all KDE apps when I try to add whitelisting to their profiles, and Firefox has similar problems when it attempts to update the default browser in mimeapps.list (see #1355).

This might have to do with KDE and Firefox trying to run rename() on whitelisted files, which fails because whitelisted files are mount points inside the sandbox and can't be renamed or replaced. It could be a lack of imagination on my side, but I guess this is a rather hard limitation in the interaction between KDE apps (or Firefox) and Firejail.

Also means we can drop all mkfile instructions in KDE app profiles with whitelist (i.e. akregator, kcalc and ktorrent).

@smitsohu commented on GitHub (Mar 3, 2018): I see the same with all KDE apps when I try to add whitelisting to their profiles, and Firefox has similar problems when it attempts to update the default browser in mimeapps.list (see #1355). This might have to do with KDE and Firefox trying to run rename() on whitelisted files, which fails because whitelisted files are mount points inside the sandbox and can't be renamed or replaced. It could be a lack of imagination on my side, but I guess this is a rather hard limitation in the interaction between KDE apps (or Firefox) and Firejail. Also means we can drop all `mkfile` instructions in KDE app profiles with whitelist (i.e. akregator, kcalc and ktorrent).

gitea-mirror commented

2026-05-05 07:40:24 -06:00

Author

Owner

@rusty-snake commented on GitHub (Apr 1, 2020):

still an issue?

@rusty-snake commented on GitHub (Apr 1, 2020): still an issue?

gitea-mirror commented

2026-05-05 07:40:25 -06:00

Author

Owner

@smitsohu commented on GitHub (Apr 2, 2020):

Basically it is a limitation in the kernel. It can be addressed either there or in the relevant libraries, there is not much that Firejail can do (apart from dirty LD_PRELOAD hacks).

@smitsohu commented on GitHub (Apr 2, 2020): Basically it is a limitation in the kernel. It can be addressed either there or in the relevant libraries, there is not much that Firejail can do (apart from dirty LD_PRELOAD hacks).

gitea-mirror commented

2026-05-05 07:40:26 -06:00

Author

Owner

@rusty-snake commented on GitHub (Nov 9, 2020):

See https://github.com/netblue30/firejail/issues/3697#issuecomment-716468502 for a workaround.

@rusty-snake commented on GitHub (Nov 9, 2020): See https://github.com/netblue30/firejail/issues/3697#issuecomment-716468502 for a workaround.

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

No description provided.

Rows
Columns