[SOLVED] KDE 4.8.2 upgrade to 4.8.5 - Issues

[maathome]

Folks,

Anyone else have an issue with the KDE 4.8.2 upgrade to 4.8.5? Attempts to launch Konqueror result in an error message "plugin libkhtmlpart uses an incompatible KDE library (4.8.5 (4.8.5))". Also, severel widgets now appear as "Unknown widget"



Notes:

I used the KDE4 Meta package to initiate the upgrade.
I've verified that a new /usr/lib64/kcm_konqhtml.so has been installed.
I created a new user & removed said user's ~/.kde4 directory to force that to be created (trying to ensure no remnants remain).
I've ran kbuildsycoca4 & kbuildsycoca4 --noincremental several times.

I'd greatly appreciate any suggestions on -- where else to look / what else to try -- .

[doktor5000]

Did you logout and login or reboot after the update?

[maathome]

Many Times.

Thanks.

[maathome]

[SOLVED]

It quickly became apparent that this was not going to be something simple. Whether a library conflict, a missing/corrupted .desktoo file, or one of the .rc files. Who knows. I let this post sit for a couple of hours to let the gurus have a peek, then I did the honorable thing. I gave up.

I didn't mention it, but this was a user machine with /home on a separate partition. Boot from the installation media, format /boot & /, let the installer trundle, and at the end watch five hundred some odd packages get updated. Log on as the wife's account, rebuild the panel, and Bob's your uncle.

The lesson here (for a user box) is to always create a separate /home partition and don't forget that a full install/upgrade is only about an hour. While I'd have loved to understand/resolve the problem myself, KDE's big and complex and I could have been at it for days.

[doktor5000]

Question would be why you triggered the update selectively, and what repos you had configured. As this is a normal update,
there's no need to trigger it manually. Also for such a huge problem complex you can't expect a finished solution within some hours
or even one day, i think that would be a bit unrealistic.

Another thing you could have tried (well, at least you can remember for next time you encounter a similar problem) is to login
via the xguest user or via a newly created user, to rule out possible problems with the existing KDE configuration.
But as it seems to have worked after a reinstallation, does not sound that likely it would have worked.

And normally the Mageia installer always creates a separate /home partition, IIRC.
But anyways, in the end you handled it rationally and saved a lot of troubleshooting time and a lot of nerves

[maathome]

doktor5000,

>>Question would be why you triggered the update selectively
I chose to make the KDE upgrade as I was going through the list of available updates. My thought was to grab that one first, (a meta package), log off/log on, then see what else was available.

>>what repos you had configured
Just the $MIRRORLIST

>>Also for such a huge problem complex you can't expect a finished solution within some hours
My hope was that someone had seen it before & I was time limited.

>>login via the xguest user or via a newly created user
I tried that.

>>And normally the Mageia installer always creates a separate /home partition
I'd forgotten that as I always go the custom partitioning route.

Thanks for your thoughts. Greatly Appreciated.