konsole - cannot edit current profile of terminal-super-user.

Hello.
First install on a new laptop.
After first reboot, I cannot save color or font size of terminal-super-user.

Konsole does not have permission to save this profile to:
"/usr/share/konsole/Root Shell.profile"
To be able to save settings you can either change the permissions of the profile configuration file or change the profile name to save the settings to a new profile.

No problem with the install user.

user_install@ASUS-G731GV-JC:~> uname -a
Linux ASUS-G731GV-JC 4.12.14-lp151.28.36-default #1 SMP Fri Dec 6 13:50:27 UTC 2019 (8f4a495) x86_64 x86_64 x86_64 GNU/Linux


NAME="openSUSE Leap"
VERSION="15.1"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.1"
PRETTY_NAME="openSUSE Leap 15.1"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"


Any help is welcome.

You didn’t post what you attempted to do, and the security context you attempted to perform that action.

KDE Profiles
https://docs.kde.org/trunk5/en/applications/konsole/profiles.html

Creating a new Konsole profile (if you’re not able to edit the existing)
https://userbase.kde.org/Konsole#Profile_Management

TSU

If you read my post you will see that the system try to store the configuration in “/usr/share/konsole/Root Shell.profile”

Or kde user konsole profile is stored in /home/user/.local/share/konsole
And kde root konsole user profile is stored in /root/.local/share/konsole which has nothing to do with /usr/share/konsole/Root Shell.profile
Secondly, root normally has rw access every where, there is no reason that it cannot write .

ASUS-G731GV-JC:~ # ls -al /usr/share/konsole
total 84
drwxr-xr-x   2 root root  4096 Jan 22 19:48 .
drwxr-xr-x 284 root root 12288 Jan 22 22:54 ..
-rw-r--r--   1 root root  1006 Feb 28  2019 BlackOnLightYellow.colorscheme
-rw-r--r--   1 root root  1023 Feb 28  2019 BlackOnRandomLight.colorscheme
-rw-r--r--   1 root root   999 Feb 28  2019 BlackOnWhite.colorscheme
-rw-r--r--   1 root root   975 Feb 28  2019 BlueOnBlack.colorscheme
-rw-r--r--   1 root root   991 Feb 28  2019 Breeze.colorscheme
-rw-r--r--   1 root root  1107 Feb 28  2019 DarkPastels.colorscheme
-rw-r--r--   1 root root   972 Feb 28  2019 GreenOnBlack.colorscheme
-rw-r--r--   1 root root   961 Feb 28  2019 Linux.colorscheme
-rw-r--r--   1 root root   957 Feb 28  2019 RedOnBlack.colorscheme
-rw-r--r--   1 root root   217 Mar 13  2019 Root Shell.profile
-rw-r--r--   1 root root   976 Feb 28  2019 Solarized.colorscheme
-rw-r--r--   1 root root  1000 Feb 28  2019 SolarizedLight.colorscheme
-rw-r--r--   1 root root   976 Feb 28  2019 WhiteOnBlack.colorscheme
-rw-r--r--   1 root root  5893 Feb 28  2019 default.keytab
-rw-r--r--   1 root root  3190 Feb 28  2019 linux.keytab
-rw-r--r--   1 root root  2610 Feb 28  2019 solaris.keytab


I have not seen that for decades.

I experimented with this. And, yes, it seems to be a problem. I’m not sure whether to call it a bug or a misfeature.

To produce: Select “Terminal Super User Mode” from the menu. Then attempt to change the settings.

Alternatively, start an ordinarly “konsole”. Then go to “Settings → Manage Profiles”, and attempt to change the profile for “Root Shell.profile”. You cannot change it and you cannot delete it.

So I tried something different.


cd .local/share/konsole
cp /usr/share/konsole/'Root Shell.profile'  .

I then did a logout followed by a login. That’s to clear any cached session data.

Then, if I open konsole and go to “Settings → Manage Profiles” there are two profiles showing with the name “Root Shell”. One of them can be changed, and one of them cannot be changed.

If I now select “Terminal Super User Mode” from the menu, that now used the profile that I can change.

I have an usb key with copy of /home/user so I copied the relevant files.
This problem does not occur on 15.0

I am opening a bug report :
1161817 – Cannot edit konsole super-user profile .

So I experimented with Leap 15.0. You are right, that it does not occur. But what happens there is about what I suggested. When you attempt to update the “Root Shell” profile, it is copied to “.local/share/konsole” and updated there.

I am opening a bug report :
1161817 – Cannot edit konsole super-user profile .

Fair enough. But it is probably an issue for “bugs.kde.org” rather than for the openSUSE bugzilla. And they might consider it a feature, rather than a bug.

Maybe I’ll check in Tumbleweed, and see what happens there.

It should be the same, I can reproduce the problem on Leap 15.1 with the latest konsole 19.12.1 (same version as in Tumbleweed).

I filed an upstream bug report on bugs.kde.org, let’s see what they say.
There are discussions upstream to maybe ship a default profile again (installed system-wide), that would also be affected then.

Yes, I noticed that. Thanks.

The change does seem to have occurred between Leap 15.0 (konsole 17.12.3) and Leap 15.1 (konsole 18.12.3).

It seems to me that if there is a profile in “/usr/share/konsole” and a profile with the same name in “$HOME/.local/share/konsole”, then konsole should only use the latter. But, at present, it shows both with “manage profiles”. And that happens even in Leap 15.0.

Yes, that’s how it was in the past, and also how color schemes are handled.

But, at present, it shows both with “manage profiles”. And that happens even in Leap 15.0.

Indeed, and apparently that’s actually one of the reasons why the functionality to modify system-wide profiles has been removed.

Behaviour in Tumbleweed: Select Root Shell profile, click Edit, change name to Root Shell Profile, Apply and a third profile is created for the active user. This FYI

Yes, if you change the name, a new (user-specific) profile with the new name is created. That’s intentional behavior since the ability to modify/override the system-wide profile has been removed, and the error dialog (quoted in the OP) actually mentions that:

Konsole does not have permission to save this profile to:
“/usr/share/konsole/Root Shell.profile”
To be able to save settings you can either change the permissions of the profile configuration file or change the profile name to save the settings to a new profile.