incompatible KDE library errors

[Phillip Lynn]

On Fri, 2011-04-29 at 13:27 +0000, Duncan wrote:
> Phillip Lynn posted on Fri, 29 Apr 2011 08:10:50 -0400 as excerpted:
> 
> > After updating my system two days ago I have been having errors when
> > running vlc, system settings to name a couple.  Below is some of what I
> > am seeing in my .xsession-errors file.  I am not sure where to continue
> > looking to try and correct these errors.  I have tried gnome and xcfe
> > desktop environments, and they are working with out errors.  It is only
> > when I am using KDE.
> 
> > kded(5360) Kded::loadModule:
> > Could not load library "kded_device_automounter" .
> > [ "The plugin 'kded_device_automounter'
> > uses an incompatible KDE library (4.6.2 (4.6.2))." ]
> 
> > kded(5360) Kded::loadModule:
> > Could not load library "kded_statusnotifierwatcher" .
> > [ "The plugin 'kded_statusnotifierwatcher'
> > uses an incompatible KDE library (4.6.2 (4.6.2))." ]
> 
> > kded(5360) Kded::loadModule:
> > Could not load library "kded_powerdevil" .
> > [ "The plugin 'kded_powerdevil'
> > uses an incompatible KDE library (4.6.2 (4.6.2))." ]
> 
> > kded(5360) Kded::loadModule:
> > Could not load library "kded_keyboard" .
> > [ "The plugin 'kded_keyboard'
> > uses an incompatible KDE library (4.6.2 (4.6.2))." ]
> 
> 
> You don't say which distribution you're using or how you updated, but it 
> appears that the update didn't complete.
> 
> 
> kded is the kde daemon.  Its job is to keep track of all the many text-
> based config files and the system status in general, and update the binary 
> system config cache (called sycoca, the first two letters of each...) when 
> something changes, thus letting the rest of kde know about it.
> 
> The errors you are seeing indicate that it's trying to load various 
> modules, and that they are using incompatible libraries -- the new kde 
> 4.6.2 versions.  This suggests that kded itself is an older version -- 
> that it either wasn't updated or that for whatever reason, it's staying 
> running and in memory when you quit kde and thus doesn't get loaded fresh 
> when you try to restart kde, thus triggering it to try to use the newer 
> modules while it's still the older version.
> 
> The simplest way to test the still in memory theory is a full reboot.  
> It's not really necessary if you know what you're doing -- how to trace 
> down, terminate and reload stale apps after an upgrade -- but for 
> "ordinary humans" and especially for trying to explain it thru a mailing 
> list, a reboot is still the surest way to ensure that what you're running 
> actually corresponds to the versions on disk, not a still-running version 
> from before the update.
> 
> If you've rebooted since the update and the problem persists, then either 
> kded itself wasn't properly updated, or one of the libraries it loads 
> wasn't properly updated.  Try this (your command may or may not have the 4 
> suffix) from a shell prompt:
> 
> kded4 --version
> 
> Mine returns (strange as it may seem, that $Id$ is literally what it says):
> 
> Qt: 4.7.2
> KDE Development Platform: 4.6.2 (4.6.2)
> KDE Daemon: $Id$
> 
> 
> If your kde development platform string reflects an earlier kde version, 
> you definitely have a problem, since you're supposed to be updated to 
> 4.6.2 now.  The Qt version might be a bit older tho.  Here on Gentoo, 
> kded4 belongs to the kdelibs package, and kdelibs-4.6.2 depends on 
> >=qt-4.7.0, so while I have 4.7.2, any qt 4.7 should be fine.
> 
> So I'd check to see what kdelibs version you have.  If it's not 4.6.2, you 
> found your problem.
> 


All,

  My system is back and running. I found I had several old kde rpms on
my system.  I ran "rpm -qa | grep kde | grep i686", then removed the old
KDE rpms. Still having problems, removed KDE, reinstalled KDE several
times was using yumex,  and the group KDE keep giving me an incorrect
install. I used "sudo yum groupinstall KDE" , then system installed
correctly.  

  Rebooted, still had a problem  KDE was really slow, unusable! Found a
post online about kde4.6 being slow, same problem I was having.  first
they said to kbuildsycoca4 --noincremental which I had done earlier this
morning.  So I did the second thing which was to run 
"rm -rf /var/tmp/kdecache-'usrname'".  After this I rebooted my system
and all appears to be working...  Thanks to those who replied with
suggestions.

Thanks,

Phillip Lynn

___________________________________________________
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.