Yet another failed KDE release?

Anne Wilson annew at kde.org
Thu Mar 21 19:11:48 GMT 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21/03/13 16:22, Myriam Schweingruber wrote:
> Did you try removing the configuration files from the previous 
> installation? It might just be cruft lying around causing this,
> and since configuration files are very individual it is very hard
> to preserve those without any glitches from time to time. KDE
> upgrade don't remove them to avoid people loosing their setups, but
> sometimes it is just a good idea to move those old files out of the
> way and try with a default configuration

People often complain that it takes too much time to re-configure
everything, but it isn't really necessary.  If you rename config
files, instead of deleting them, you can easily copy back relevant
parts, such as email identities.  And who knows?  You might even be
surprised to find some things that date back years and you had
forgotten about them.  It could be quite an enlightening exercise.

Anne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFLW2oACgkQj93fyh4cnBczNwCff+TBaTLckZ+RhHCaU+utiP/0
MK8An1WgwR/fTO7+/mJ3dOCBLhDpsZNi
=BkrC
-----END PGP SIGNATURE-----
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.




More information about the kde mailing list