Bug 186111 - Konsole profile settings are not saved
Summary: Konsole profile settings are not saved
Status: RESOLVED DUPLICATE of bug 184959
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 09:50 UTC by Karim Ryde
Modified: 2011-08-02 18:46 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karim Ryde 2009-03-04 09:50:39 UTC
Version:           2.2 (using 4.2.00 (KDE 4.2.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.27-11-generic

Changing settings in Konsole are not saved. Each time I restart Konsole settings and profile are reverted to default.
I changed tabs at the bottom and history to unlimited then clicked on Apply and Ok.
Comment 1 Konstantin Kucher 2009-03-12 21:19:46 UTC
I can confirm this bug on KDE 4.2.1 in Debian.

This bug is obviously connected to these ones:
https://bugs.kde.org/show_bug.cgi?id=183244
https://bugs.kde.org/show_bug.cgi?id=184959
Comment 2 Jan Ekholm 2009-11-17 09:18:48 UTC
I can confirm this on 4.3.2. It's been present in the entire KDE 4 series and for me it's a fairly annoying bug. I use profiles heavily to log in to various systems, start various services in own tabs etc and it's a bit of a hassle to always have to go via "Settings -> Manage profiles" and click in the "Show in Menu" column.
Comment 3 Ray Evans 2010-02-06 00:23:30 UTC
I can reproduce this with konsole 2.3.3 on Fedora 12 x64 using KDE 4.3.5.   I attempt to change any of the profile settings, particularly the scrollback setting.  Save to current profile and close.  The scrollback setting is lost.
Comment 4 Uwe Drechsel 2010-09-29 09:20:47 UTC
Still there in openSUSE 11.3 with KDE 4.5.1
Comment 5 Jekyll Wu 2011-08-02 18:46:56 UTC

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