github-starred/firejail

Fork 0

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

[GH-ISSUE #1789] Konsole forgets theme #1212

New issue

Closed

opened 2026-05-05 07:39:53 -06:00 by gitea-mirror · 8 comments

gitea-mirror commented

2026-05-05 07:39:53 -06:00

Owner

Originally created by @idnovic on GitHub (Feb 26, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1789

Konsole forgets the console theme. Not the gui. I am talking about the terminal itself.

I do not know how to explain why it happens or when.
But unter "settings - profiles" new profiles get created "Profile 1" "Profile 2" etc
They increase in the numbering.

The bug is that I configured a theme and it gets ignored.
I tryed to fix it by editing the theme config files in the filesystem (home)
/home/idnovic/.local/share/konsole/

I deleted the other profiles. I can not regenerate the error now.

Originally created by @idnovic on GitHub (Feb 26, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1789 Konsole forgets the console theme. Not the gui. I am talking about the terminal itself. I do not know how to explain why it happens or when. But unter "settings - profiles" new profiles get created "Profile 1" "Profile 2" etc They increase in the numbering. The bug is that I configured a theme and it gets ignored. I tryed to fix it by editing the theme config files in the filesystem (home) `/home/idnovic/.local/share/konsole/` I deleted the other profiles. I can not regenerate the error now.

gitea-mirror

2026-05-05 07:39:53 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 07:39:58 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Feb 26, 2018):

We don't provide a profile for Konsole, which profile are you using? And if you did create a profile for it, its settings are blacklisted by default by disable-common.inc.

@SkewedZeppelin commented on GitHub (Feb 26, 2018): We don't provide a profile for Konsole, which profile are you using? And if you did create a profile for it, its settings are blacklisted by default by [disable-common.inc](https://github.com/netblue30/firejail/blob/master/etc/disable-common.inc#L57).

gitea-mirror commented

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

Author

Owner

@idnovic commented on GitHub (Feb 26, 2018):

my bad, I think it happend if I open konsole over dolphin.
Yes just tested it. The new Konsole window lost the settings again.
Well I think the dolphin profile is responsible.

Does it make sense to allow .local/share/konsole/ ?? reading for dolphin
The new konsole window is not sandboxed but opened over dolphin it forgets the settings.

@idnovic commented on GitHub (Feb 26, 2018): my bad, I think it happend if I open konsole over dolphin. Yes just tested it. The new Konsole window lost the settings again. Well I think the dolphin profile is responsible. Does it make sense to allow `.local/share/konsole/` ?? reading for dolphin The new konsole window is not sandboxed but opened over dolphin it forgets the settings.

gitea-mirror commented

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

Author

Owner

@idnovic commented on GitHub (Feb 26, 2018):

and now the normally opened konsole window lost its theme too.
The konsole window opened over dolphin must have set the "new" theme

@idnovic commented on GitHub (Feb 26, 2018): and now the normally opened konsole window lost its theme too. The konsole window opened over dolphin must have set the "new" theme

gitea-mirror commented

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

Author

Owner

@smitsohu commented on GitHub (Feb 26, 2018):

If you go to /etc/firejail/disable-common.inc and change blacklist ${HOME}/.local/share/konsole to read-only ${HOME}/.local/share/konsole, does it fix your issue?

IMHO read-only should actually be sufficient from a security perspective.

@smitsohu commented on GitHub (Feb 26, 2018): If you go to /etc/firejail/disable-common.inc and change `blacklist ${HOME}/.local/share/konsole` to `read-only ${HOME}/.local/share/konsole`, does it fix your issue? IMHO `read-only` should actually be sufficient from a security perspective.

gitea-mirror commented

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

Author

Owner

@idnovic commented on GitHub (Feb 26, 2018):

No it does not.
It seems my default profile does not get loaded. I can select it in the options as default profile and nothing happends (the single only profile).
If I now click on < Settings - Switch profile - my profile > it loads the profile.

maybe their is an configuretion file stored somewhere else.

@idnovic commented on GitHub (Feb 26, 2018): No it does not. It seems my default profile does not get loaded. I can select it in the options as default profile and nothing happends (the single only profile). If I now click on < Settings - Switch profile - my profile > it loads the profile. maybe their is an configuretion file stored somewhere else.

gitea-mirror commented

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

Author

Owner

@idnovic commented on GitHub (Feb 26, 2018):

I choose "run in single instance" in the options of konsole. Still opens an other instance.
Theme is fine for the time beeing.

@idnovic commented on GitHub (Feb 26, 2018): I choose "run in single instance" in the options of konsole. Still opens an other instance. Theme is fine for the time beeing.

gitea-mirror commented

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

Author

Owner

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

If konsole is launched through dolphin, it runs inside the dolphin sandbox. This makes all custom profiles inaccessible, because they are stored in ~/.local/share/konsole which is blacklisted.

The konsole default profile is defined in ~/.config/konsolerc. It seems that if konsole can't find this default profile in (blacklisted) ~/.local/share/konsole, it partially resets ~/.config/konsolerc, leading to described behavior.

The loss of konsole settings can be prevented by read-only ~/.config/konsolerc, should it not be sufficient to switch from blacklist ~/.local/share/konsole to read-only ~/.local/share/konsole.

Thank you for the bug!

@smitsohu commented on GitHub (Mar 1, 2018): If konsole is launched through dolphin, it runs inside the dolphin sandbox. This makes all custom profiles inaccessible, because they are stored in `~/.local/share/konsole` which is blacklisted. The konsole _default_ profile is defined in `~/.config/konsolerc`. It seems that if konsole can't find this default profile in (blacklisted) `~/.local/share/konsole`, it partially resets `~/.config/konsolerc`, leading to described behavior. The loss of konsole settings can be prevented by `read-only ~/.config/konsolerc`, should it not be sufficient to switch from `blacklist ~/.local/share/konsole` to `read-only ~/.local/share/konsole`. Thank you for the bug!

gitea-mirror commented

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

Author

Owner

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

It is fixed for me with your suggested edits.
Thank you. You can close this now after you fixed it in the source code 👍

@idnovic commented on GitHub (Mar 2, 2018): It is fixed for me with your suggested edits. Thank you. You can close this now after you fixed it in the source code :+1:

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

No description provided.

Rows
Columns