-   Suse/Novell (
-   -   KDE 4.1.1 - there's nothing on the desktop, nothing works. (

lordmorgul23 09-18-2008 08:02 AM

KDE 4.1.1 - there's nothing on the desktop, nothing works.
I've recently updated KDE to 4.1.1. Yesterday I forgot to plug my laptop in - and it turned itself off, while I wasn't home. So, after switching it back on, I logged in to my KDE... and there's nothing. Just a checkered grey-and-white board instead of the wallpaper. The only thing working is the alt-f2 runner, but it won't start anyhing - konsole, dolphin, opera, absolutely nothing. So I logged in to text-mode, removed ~/.kde4 - and tried to log back in. And there's still nothing. I reinstalled all KDE4 packages, including plasma and QT libs. And nothing changed - there's only the white-and-grey wallpaper, with the runner and task manager working.
Now I'm on Fluxbox, but I'd prefer to go back to KDE4. Any ideas?

ronlau9 09-19-2008 08:16 AM

How do you reinstall it ?
Did you let yast make the choices ?
Or did you make it manually ?
By let yast make the choices I mean using the option yast>software>filter=pattern>kde

lordmorgul23 09-19-2008 11:57 AM

Well, I removed everything containing kde4* and kdebase4* through YAST - and then installed it again, using patterns.

ronlau9 09-19-2008 02:00 PM

When it turns it self off , it is my opinion a hard shutdown , so it might be possible that same files are damage.
It might be worth to run the repair option from the install media

dexen 09-19-2008 02:49 PM

I'm having the very same problems you described. I think your ones aren't really caused by broken installation.

I've upgraded from KDE 4.1.0 to 4.1.1 on my laptop, and, at the same time, installed it from scratch on a brand new system. Both ended up are broken in the very same way.

Tested them both with an exsiting user account (old config files) and with a new account, created from scratch. Neither worked right.

Re-installed packages on both machines, no improvement. There wasn't any error during the installation.

My OS is Slackware-current (post-12.1), with all the libs & stuff upgraded to newest versions. Kernel is 2.6.27-rc5 on one, 2.6.24 on the other.

To be more specific, both Plasma and krunner are unable to load plugins; they reports errors claiming the plugins are compiled for plasma version 4294967296 (that's 2^32).

I have no solution for the problems as of now. Neither the people on #slackware nor the ones on #kde on the Freenode encountered such problems.

BTW., you can still use KDE like that, just start a Konsole, and run all the programs from it. There are two alternative ways:
1) navigate to /usr/bin/konsole using Konqueror or Dolphin, if you have one open, OR
2) start the usual way, log in into a textual terminal (outside of, issue the following commands:
export DISPLAY=:0 # or whatever is the address of in your configuration
and now you can start all the apps by their names, like konqueror, dolphin, sysetmsettings, kword, kmail, kopete, and so on.

lordmorgul23 09-19-2008 03:22 PM

So, you think it's possible that it will solve itself when 4.1.2 is out? Oh, and thanks for the tip, actually it's kinda fun to be able to start an application with a GUI using SSH ;-)

dexen 09-19-2008 04:26 PM


Originally Posted by lordmorgul23
So, you think it's possible that it will solve itself when 4.1.2 is out?

I hope somebody will find out WTF is wrong with our packages and post about a fix somewhere, long before 4.1.2 is out ;) I bet it's a small stupid thing specific to our systems; otherwise, there would be fl00d of error reports all over the internet... Unless we two are the only KDE 4.1.1 users out there XD

One more note: the problem is *not* caused by SMP machines; my laptop's uniprocessor only.


Originally Posted by lordmorgul23
Oh, and thanks for the tip, actually it's kinda fun to be able to start an application with a GUI using SSH ;-)

Erm, you don't really need SSH to log into Linux's textual terminal... Of course, you can use OpenSSH (or PuTTY for that matter) to interact with an X program that's runnnig on a remote machine; X being very network-centric and client-server and whatnot.

dexen 09-19-2008 04:34 PM

The post seem to suggest updating to Qt44 solves the issue.


I've just updated to Slackware's newest Qt4 ( ) and KDE works allright now :)

lordmorgul23 09-19-2008 04:40 PM

Yeah, of course, I know I don't need SSH, it's just funnier that way, now I can actually open an application on my roommate's PC and freak him out :-D Thanks for the link, I'm running the updater right now, but it's got over 300MB to download, so I'll post the result later, hopefully from a working KDE4.1.1 ;-)

lordmorgul23 09-19-2008 08:16 PM

Oh yeah, it's working :-D Thank you so, so much, dexen.
There was one good thing about this situation, though - I've finally configured my Fluxbox ;-)

sniff 09-21-2008 05:23 AM

I had same problem, solved by QT4 update to 4.4.2.

There is a repo if anyone needs it...


All times are GMT -5. The time now is 02:36 PM.