Yet another failed KDE release?

Mirosław Zalewski miniopl at
Fri Mar 22 11:13:13 GMT 2013

On Fri, Mar 22, 2013 at 8:08 AM, Nikos Chantziaras <realnc at> wrote:
> The biggest issue is that with each new release, there's more glitches
> while the old ones are still there.  

On 22/03/2013 at 11:38, Myriam Schweingruber <myriam at> wrote:
> And make sure you ALWAYS test with a new user or move the old config files
> elsewhere when you do a major upgrade.

Myriam, this is exactly Nikos point. Old config files laying around causes 
various issues with KDE SC. By encouraging him to triage bugs on fresh config, 
you admit that.

I think that this is huge drawback of KDE SC. As user, I am forced to recreate 
my carefully crafted configuration from scratch with each major update. Do I 
remember what exactly did I change and where? No, I have better things to do. 
Starting from fresh config, I only discover that something I am used to does 
not work. Then I go into System settings and try to find relevant option. 
Recreating configuration is not matter of two or three hours; it's matter of 
days during which my work is not effective, because I am constantly disturbed 
with changes I have to make.

Or I can save myself some hustle and start from fresh config, but copy some old 
files over. But this way I am forced to dive into KDE SC internals and 
understand purpose of each file (to be able to judge whether I should copy it 
or not). Do I want to? No, I have other things to do.

Honestly, why can't KDE SC support seamless update from previous major 
release? Is it too much work to rewrite config files whose format has changed?
Best regards
Mirosław Zalewski
This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list