Bug 458835

Summary:	Configuration files created with the create new profile button are not saved
Product:	[Applications] konsole	Reporter:	horace <horce1024>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	asturm, matrixfueller
Priority:	NOR
Version:	22.08.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description horace 2022-09-07 12:23:36 UTC

Configuration files created with the create new profile button are not saved


STEPS TO REPRODUCE
1. Click the settings button and then click the create new profile button to create a new profile.
2. Click the default profile button, then set the font and font size as you like, click the apply button to save the settings, and then click the ok button. At this point, click on the settings button to see the switch profile option, which has a read only profile and a new profile, and then exit the konsole.
3. Open konsole again, you can see that there is only a read only configuration file, no new configuration file.

OBSERVED RESULT
There is only one read-only configuration file.

EXPECTED RESULT
There is the previously added configuration file, which is two configuration files.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: archlinux 5.19.7
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION

Comment 1 Enno Gotthold 2022-10-22 15:21:16 UTC

I can confirm that this is also present in openSUSE Tumbleweed. Thus it is not limited to Arch.

Additionally I found out that this seems to affect more users: https://www.reddit.com/r/kde/comments/wmksd3/konsole_losing_profiles/

In a Majaro forum there is a workaround known but I don't find it very "usable": https://forum.manjaro.org/t/konsole-profiles-are-recovering/123639

Comment 2 Enno Gotthold 2022-10-22 15:27:23 UTC

A possible reason (I am no KDE dev though) could be that an important env variable is not set:

> echo ${XDG_DATA_HOME}/konsole
/konsole

Comment 3 Enno Gotthold 2022-10-22 15:30:11 UTC

(In reply to Enno Gotthold from comment #2)
> A possible reason (I am no KDE dev though) could be that an important env
> variable is not set:
> 
> > echo ${XDG_DATA_HOME}/konsole
> /konsole

Okay according to https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html this should be allowed, however if not taken care of by the code this could still be a possible error cause.

Comment 4 horace 2022-11-02 02:27:57 UTC

(In reply to Enno Gotthold from comment #3)
> (In reply to Enno Gotthold from comment #2)
> > A possible reason (I am no KDE dev though) could be that an important env
> > variable is not set:
> > 
> > > echo ${XDG_DATA_HOME}/konsole
> > /konsole
> 
> Okay according to
> https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
> this should be allowed, however if not taken care of by the code this could
> still be a possible error cause.

Yes, can you get in touch with the developer of kconsole? This does affect the experience, after all, it does this every time I open the terminal. I've gone back to gnome for a while waiting for them to fix this bug.

Comment 5 Andreas Sturmlechner 2023-01-06 13:33:22 UTC


*** This bug has been marked as a duplicate of bug 457028 ***