Bug 251062 - KPart unable to effectively set a profile as the default profile
Summary: KPart unable to effectively set a profile as the default profile
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: kpart (show other bugs)
Version: 2.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-13 11:51 UTC by Julien Humbert
Modified: 2011-10-05 06:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.8
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 Julien Humbert 2010-09-13 11:51:25 UTC 
Version:           2.9.7 (using KDE 4.5.1) 
OS:                Linux

Creating and set a new profile as default with Yakuake seems to be not saved, at restart, it is the old one that is still used, but altough, using Konsole to set the new default one, works, and starting Yakuake after works.

Reproducible: Always

Steps to Reproduce:
1. Launch Yakuake
2. Open up the config menu and choose "configure profiles" (Gérer les profils)
3. Create a new one
4. Hit the button to set it as default
5. Restart Yakuake

Actual Results:  
The old profile is used.

Expected Results:  
Yakuake should use the new one.

OS: Linux (x86_64) release 2.6.34.4-0.1-desktop
Compiler: gcc
Comment 1 Eike Hein 2010-09-13 13:29:09 UTC 
Reassigning to Konsole as the profile stuff is entirely handled in that codebase.
Comment 2 Jekyll Wu 2011-10-05 06:33:10 UTC 
    Always read/write the 'DefaultProfile' entry from/into 'konsolerc'.
    
    That means the default profile is shared among konsole and all host
    apps of konsole kpart. That is not ideal enough, but much better than
    current inconsistent read/write for the 'DefaultProfile' entry.
    
    BUG:251062
    FIXED-IN: 4.8