Bug 168402 - Settings lost across restarts when quit by KDE session logout
Summary: Settings lost across restarts when quit by KDE session logout
Status: RESOLVED WORKSFORME
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
: 173498 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-05 11:29 UTC by Alan Braslau
Modified: 2011-12-03 06:37 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Braslau 2008-08-05 11:29:30 UTC
Version:           unknown (using 4.1.00 (KDE 4.1.0), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.25

Deselecting the "keep window open when loosing focus" option works properly until quitting yakuake (logout). Upon restart, the setting is reset to the default (keep window open) value.
Comment 1 Eike Hein 2008-08-05 15:05:26 UTC
What version of Yakuake are you using, and how do you set the setting specifically (as there are multiple means)?
Comment 2 Alan Braslau 2008-08-05 15:42:32 UTC
Version 2.9.2 (this information did not get automatically included, I see, using the report bug feature...)

It is set via "Configure Yakuake..." settings pop-up menu, Behavior frame
or by selecting the option on the Quick Option menu, with the same result.

The bug seems to have appeared with a recent update, as I never noticed this problem before.
Comment 3 Eike Hein 2008-08-05 15:45:10 UTC
Can't say I can reproduce it. KDE apps save their config on quit, so it seems like your Yakuake is getting killed on logout somehow rather than probably being quit as the session manager should normally do.
Comment 4 Eike Hein 2008-08-05 15:45:22 UTC
s/probably/properly/
Comment 5 Alan Braslau 2008-08-05 15:57:22 UTC
Indeed, KDE 4.1.00 does not appear to be entirely stable handling background processes (see various bug reports concerning kdelibs, konqueror, kmail, ... such as bug 167826 and duplicates).

Would it not be safer/saner to save config options upon change rather than on exit? 
Comment 6 Eike Hein 2008-08-05 16:12:36 UTC
That has other downsides, such as spinning up the disk every time an option changes, which makes laptop users unhappy.
Comment 7 Alan Braslau 2008-08-05 17:57:55 UTC
OK, but how often does one change options?

It has always been my belief to aim to develop robust code, of course taking performance issues into account.

I confirm: "killall yakuake" (or the quit button) then restarting yakuake correctly handles the option settings. The problem appears to be shunted (until I change an setting). However, there appears to be some funny behavior (inconsistencies) between the different ways of setting options. Some further rationalization may still need to be done.

So should this bug be assigned to the session manager (or be put on hold to see if it persists)?
Comment 8 Eike Hein 2008-08-05 18:07:14 UTC
I don't think it's useful for the session manager bug list at this point.
Comment 9 A. Mosteo 2008-10-16 10:49:06 UTC
I'm seeing this in KDE 4.1.2, Kubuntu 8.10 packages, Yakuake version 2.9.3.
Comment 10 Eike Hein 2008-10-25 11:51:41 UTC
*** Bug 173498 has been marked as a duplicate of this bug. ***
Comment 11 Jedd 2009-04-10 00:05:58 UTC
Just to confirm - this bug manifests on Debian unstable, KDE 4.2.2 packages, which include yakuake 2.9.4

*No settings* are retained, not just 'happily slide away when you lose focus'.

Oh, btw, is the 'use the konsole settings' option gone for good?  I was kinda fond of that option.
Comment 12 Eike Hein 2009-04-10 14:22:22 UTC
That option is gone for good, but sort of equivalent to using the same profile in Konsole and Yakuake. Please note that the option was implemented in the Konsole KPart component which Yakuake merely embeds; the terminal area and its context menu are not part of the Yakuake code base.
Comment 13 Jekyll Wu 2011-12-03 06:37:30 UTC
This report is quite old, and I can't reproduce the reported problem using yakuake-2.9.8 in KDE SC 4.8 beta1. Feel free to reopen if this problem still happens in recent version.