Version: 1.0.1 (using KDE KDE 3.5.5) Installed from: Debian stable Packages OS: Linux Following up to Eike Hein's comments in #141760, the log path may change automatically due to the change of the default log path from the standard location to ~/logs/, "causing confusion and disruption". This could be fixed by changing the default back, or if "additional code is written to survey the old dir and copy over its contents". This should affect upgrades from Debian stable unless fixed soon.
First of: I'm actually not sure this going to happen at all, as the legacy pre-0.19 preferences code may have actually written out all of the key=value pairs on application quit regardless of whether they were unchanged defaults or not. If the key does exist in konversationrc, a newer Konvi will continue to use the specified dir. My comments in #141760 were about a future change and KConfigXT behavior. > This could be fixed by changing the default back Which won't happen prior to the KDE4 port and is unlikely even then (but requires further discussion), as per #141760. > This should affect upgrades from Debian stable unless fixed soon. Even if committed to SVN today, we're not going to be able to release a new version in time to be put into unstable and migrate to testing before Etch goes stable, going by their current timetable, so this is moot. It's an unfortunate situation for sure, although we don't consider pre-1.0 behavior binding, as mentioned in #141760. And the relevant desktop-centric Debian derivatives (read: Kubuntu) have been shipping 1.0.x for some time now. Note that #141760 was marked as RESOLVED LATER. It will be reopened when we got 1.1 out of the door and branched the KDE 3.x codebase to branches/stable and switch trunk over to KDE4 development. We shall discuss whether to implement a change and how to go about it (copy over or avoid changing existing setups, etc.) then. Some code to handle even manual log dir changes in the prefs dialog painlessly would certainly be nice to have.