KDE desconfiguration on upgrade of kdelibs4

Bug #16559 reported by Daniel Estévez Sánchez
8
Affects Status Importance Assigned to Milestone
kdelibs (Ubuntu)
Fix Released
Medium
Andreas Mueller

Bug Description

Recently, new packages of kdelibs4 have gone into the hoary-security repository (version 4:3.4.0-0ubuntu3.1).
On upgrading this packages my system gets desconfigured. The kde style changes from default lipstik to plastik
and kubuntu kde specific configurations (such as opening new konquerors in tabs) disappear. It seems that the
kde configuration goes back to plain kde. For example, KPersonalizer will appear to new user, instead of
jumping into the already configured kubuntu default desktop.

kdelibs4-data can be safefully upgraded, but upgrading all the other kdelibs4 packages will result in
desconfiguration. I've also noted that when configuring kdelibs-data (both the old version and the new), it
tries to step into a file owned by knetworkconf, so knetworkconf must be uninstalled before kdelibs-data
reinstallation or upgrade.

Revision history for this message
Jonathan Riddell (jr) wrote :

Do you have the file /etc/kderc ?

Revision history for this message
Daniel Estévez Sánchez (genghis-khan) wrote :

(In reply to comment #1)
> Do you have the file /etc/kderc ?
>

Yes. Its contents are:
---------
[Directories]
userProfileMapFile=/etc/kde-user-profile

[Directories-default]
prefixes=/usr/share/kubuntu-default-settings/kde-profile/default/
----------

But now my system is working as before because I purged and installed the old versions. ¿Do you mean that if I upgrade now
and put that kderc the sistem will work with the Kubuntu configuration?

Revision history for this message
Daniel Frein (danielfrein) wrote :

/var/lib/dpkg/info/kdelibs4.preinst deletes /etc/kdmrc: in the upgrade section of the preinst
script there is a "rm -f /etc/kderc"
(see also bug 16337)

Revision history for this message
Andreas Mueller (amu) wrote :

removed it from preinstall for breezy.

Revision history for this message
Andreas Mueller (amu) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.