Version: 2.9.3 (using KDE 4.1.0) Installed from: SuSE RPMs I'd like to modify the default profile of Yakuake to match my preferences (e.g. font type/size, displaying of scroll bars or cursor blinking). I therefore select "Edit current profile" from the context menu and make the required changes, which are being applied immediately. However, yakuake "forgets" about these settings every time I restart KDE. It seems as if it does not save these settings at all. Starting yakuake from within a konsole window reveals the following error: yakuake(12412) Konsole::SessionManager::loadProfile: Could not load profile from "/home/lenz/.kde4/share/apps/konsole/.profile" (Which is correct - the file does not exist) I also tried to create a named profile using the "Manage Profiles" entry in the context menu. Interestingly it displays the name of my konsole profile *twice* there (but they are not available from the "Change Profile" menu entry in the yakuake context menu. Adding a new profile there does not help - it too is lost after I restart yakuake.
First of, the entire terminal area inside Yakuake along with any dialogs to manipulate terminal profiles are provided by the Konsole codebase which Yakuake embeds in the form of the Konsole KPart component, i.e. it may turn out that this bug will need to be reassigned to Konsole. Before that happens, however: It sounds to me like your Yakuake process might be getting killed rather than quit properly, causing the Konsole codebase not to flush its settings to disk. Could you investigate that avenue, along with the obvious ones like write permissions for the Konsole settings directory?
(Addendum: Yakuake also does not maintain its own profiles; the Konsole KPart accesses the same set of profiles as Konsole itself, and any changes to the default profile affect both applications.)
Maybe related to bug #167826, Eike?
I can't reproduce a Yakuake process running beyond quitting the app (either using the KAction or the D-Bus interface), but perhaps the reporter can tell us if that's the case on the problem system.
Eike, thanks a lot for the quick reply! Indeed, quitting yakuake properly instead of killing it seems to have caused it to save the settings properly - now it starts up with last configured settings and I now only see one instead of two profiles in the list. I somehow assumed that these settings are saved as soon as I "Applied" the settings I just changed... Maybe something to consider?
Hm well, KDE applications in general tend to flush their settings to disk on quit, rather than on preferences dialog dismissal. Plus: While I could indeed cause that to happen for Yakuake's own preferences dialog, Yakuake has no such control over the profile management dialogs shown by the Konsole KPart component, so this would need to be changed there.
I have a similar issue using yakuake 2.9.4 on Fedora 10. When closing yakuake and reopen it, all settings (like sizes, sticky, ...) are correctly saved. They're not when I close my KDE session. Sounds like yakuake does not quit properly while logout, but it should, I think. Any hint for this ? Is this a yakuake issue or a kde one ?
I experienced this problem on a freshly installed SuSE 11.1 with KDE 4.1.3 and yakuake 2.9.4. After reading this thread and doing a few experiments, the error seems to be a problem with Konsole rather than yakuake. At length, after a fresh reboot, I started yakuake, saw the profile reset to default, closed (quit) it, then started Konsole and edited my the profile there, afterward closing it normally. I then restarted yakuake and all was well. I restarted X, and the settings stuck. I had falsely, I think, assumed it was a yakuake problem because that's all I use for a terminal when KDE is running.
Same problems existed with konsole, hence, I'm pretty sure this is no yakuake problem.
Hm, reassigning then.
*** This bug has been confirmed by popular vote. ***
I have same problem with 2.9.6 on gentoo amd64
I had same problem. Yakuake forget my profile settings (which use as default one and etc). However changing same setting in Konsole, solved my problem. It's seems Yakuake depends on Konsole settings, and not for his own. Gentoo, amd64, KDE-4.3.95, Yakuake-2.9.6.
See comment #1 and #2.
In my case, Yakuake wrote new settings in yakuakerc, but didn't wanted to read from. Even now the "DefaultProfilet - default, but Yakuake keep loading other profile from konsolerc.
I did the same. Workarounded it by using Konsole to create a profile that suited my needs, then modified konsolerc and wrote its name in the "DefaultProfile=" field. Now it works fine. Not too user-friendly, but very Linux'y, though! Hope this gets fixed soon!