After just a few seconds after starting kde4.2 RC1 plasma desktops freezes. It looks like plasma hibernates. It wakes up some times at updates the clock, 3 minutes last time. My cpu montior hasn't been updated since plasma started to hibernate.
Rest of kde seems to bee working, I can start application with krunner. Switch virtual desktops work just fine.

I need some tips on how I can find the cause of this problem.

After three restarts... 20 minutes waiting Plasma seems to have left its hibernate state

Which applets in particular are you using? It sounds like a web based one is having issues trying to connect to a site, and locking Plasma while it waits for a response ( Twitter, RSS, etc )

bcooksley wrote:Which applets in particular are you using? It sounds like a web based one is having issues trying to connect to a site, and locking Plasma while it waits for a response ( Twitter, RSS, etc )

Calculator
Dictionary
Eyes
Device Notifier
Digital Clock
Folder View
Now Playing
Pager
Show Widget Dashboard
CPU monitor
Disk monitor
Network monitor
Lancelot Launcher

I don't think any of them are web based, except from the Dictionary. But Dictionary shouldn't use the web before something is typed in it.

bcooksley wrote:Which applets in particular are you using? It sounds like a web based one is having issues trying to connect to a site, and locking Plasma while it waits for a response ( Twitter, RSS, etc )

A plasmoid can freeze the whole desktop? oops...

Do you notice any elevated activity ( large RAM / CPU usage or heavy disk i/o ) during the time Plasma is "hibernated"?

You could try removing the contents of Plasma's cache's ( located at $KDEHOME/cache-$HOSTNAME/plasma-* )
Do not just remove everything in the cache unless at a terminal, without KDE running.

bcooksley wrote:Do you notice any elevated activity ( large RAM / CPU usage or heavy disk i/o ) during the time Plasma is "hibernated"?

No, the computer felt quicker with plasma in this state... Xorg used less cpu than it normally uses (10-15%). I didn't see plasma in top.

Right after it hibernates could you look at the file "~/.xsession-errors", Grep it for "plasma" then post the resulting text here?

bcooksley wrote:Right after it hibernates could you look at the file "~/.xsession-errors", Grep it for "plasma" then post the resulting text here?

I don't want to restart rigth now. But I didn't find many entries in .xsession-errors with plasma and that file does not have many timestamps :-P (the only one I found was in the begining). This might be the culprit:

Code: Select all

plasma(12111) NowPlaying::playerAdded: Player "org.mpris.amarok" added
plasma(12111) NowPlaying::playerAdded: Installing "org.mpris.amarok" as watched player
plasma(12111) NowPlaying::dataUpdated: Got no data
plasma(12111) NowPlaying::findPlayer: Looking for players.  Possibilities: ("org.mpris.amarok")
plasma(12111) NowPlaying::findPlayer: Installing "org.mpris.amarok" as watched player
(12644)/: Communication problem with  "amarok" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

Thats the last lines from plasma.

That looks like the Now Playing plasmoid is at fault. It is trying to call Amarok and failing. Do you have Amarok 2 running when you experience these problems?

Yes, according to .xsession-errors:

Code: Select all

kdeinit4: preparing to launch /usr/bin/amarok
Amarok is already running!

This message is right before the plasma message.

I cannot reproduce this problem any more...

As you cannot reproduce it anymore, please add a [SOLVED] to the title. Thanks.