-   Slackware (
-   -   Moving to Kde4 in Current (

TNWestTex 05-18-2009 02:38 PM

Moving to Kde4 in Current
I didn't try KDE4 while it was in testing and hadn't updated my -current installation in a few weeks. Installed all the 4.2.3 packages along with the qt upgrade but something is amiss. I saw a reference to a readme on the transition that was in testing but doesnt't seem to be in the hints or on a mirror anywhere. The reference link was dead.

ksysguard goes into an infinite loop with the pop-up that the connection to localhost is lost. Which doesn't make since as X is still working. The host terminal window gets the repeat message that "Launch helper exited with unknown return code 127" This is on a compute cluster that is not connected to the internet.

Several programs (konqueror, dolphin) do not get linked to needed .so files even though the files exist in /usr/lib/kde4.

I've used KDE4 on Fedora so am familiar with some of its structure but this has me stumped.

Robert McBroom

Ilgar 05-18-2009 02:59 PM

If you're using stuff from -current then you will need to upgrade all packages to the -current versions, not just the Qt/KDE ones.

willysr 05-18-2009 07:13 PM

You should read and first before upgrading to -Current :)

TNWestTex 05-19-2009 08:54 AM

Some people need Glasses
As I said the upgrade is incremental of packages to -current that have changed recently. KDE was at 3.5.10. /var/log/packages tracks FILE_LIST except for things like wireless drivers and bluetooth.

TNWestTex 05-20-2009 11:42 AM

Partial answer to my own post, in KDE4 konqueror and dolphin require the packages in the l tree soprano and phonon. Haven't found the missing package for ksysguard.

What doe the message
"the name was not provided by any .service files"
refer to?

All times are GMT -5. The time now is 12:22 PM.