Bug 460225 - Newly created proffile is lost when closing konsole. Also not possible to edit created profile.
Summary: Newly created proffile is lost when closing konsole. Also not possible to edi...
Status: RESOLVED DUPLICATE of bug 457028
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 22.08.1
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-11 05:50 UTC by Jan-Petter Vainionpää
Modified: 2023-01-06 13:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Petter Vainionpää 2022-10-11 05:50:31 UTC 
SUMMARY
***
Unable to edit created profile & profile disappears when terminating konsole
***


STEPS TO REPRODUCE
1. Settings -> Create Ne Profile 
2. Name new profile & Tweak your own settings
3. Appy & OK 
4. Settings -> Manage Profiles
5. Select previously created profile and try to edit it, not possible
6. Close konsole
7. Restart konsole
8. Settings -> Manage Profiles
9. Previously created profile is no longer there

OBSERVED RESULT
I was not able to re-edit previously created profile. It seemed to be read-only though it did not say so.
And profile was lost in reboot

EXPECTED RESULT
I should be able to edit my previously created profile and created profile should be there also after restarting konsole.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.10
KDE Plasma Version: 5.25.5 
KDE Frameworks Version: Version 5.98.0
Qt Version: Version 5.15.6 (built against 5.15.6)

ADDITIONAL INFORMATION
Comment 1 Paul Worrall 2022-10-11 09:33:09 UTC 
I was able to reproduce this, but after trying a few things (launching Konsole from within Konsole and from Krunner) I can no longer reproduce it.  Marking as confirmed on the basis it can be reproduced.
Comment 2 Andreas Sturmlechner 2023-01-06 13:34:02 UTC 

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