Version: 4.7 (using KDE 4.7.0) Title says it all really. A new KDE installation, clean .kde folder. After a few days of use, it now hangs after the "K" has lit up. Not always, but when it happens only a full restart seems to fix the issue. Logging in/out will keep recreating the same problem I attach a copy of .xsession-errors Reproducible: Sometimes
Created attachment 281783 [details] .xsession-errors from a typical unsuccessful boot
Just for fun... please try (when it "hangs") switching with ALT+CTRL+F1 to the text console and then back to KDE with ALT+CTRL+F7... does that change anything?
No change at all I am afraid. I got a copy of .xsession-errors precisely by doing that. (logging in a console and copying the file)
I believe the last line of .xsession-errors refers to me switching to the terminal actually
I can confirm that. Same thing happens on my system.
Here is my post from https://bugs.kde.org/show_bug.cgi?id=278943 It is possible I have the similar problem. With kde 4.6.5 and now with kde 4.7.0. KDM starts but never shows desktop, just mouse pointer. Top shows that plasma-desktops has 100% cpu usage. I "resolved" it by removing ~/.kde4/share/apps/plasma/plasmoids directory where I had had two similar plasmoids scripted in python. And if I restore this directory after login and try to readd these plasmoids, plasma-desktop hangs and eats cpu in the same way, but sometimes it adds plasmoids and works fine. BUT when I run same plasmoid with plasmoidviewer it always works! It looks like that PyQt4, pykde4 or something similar is involved. Other plasmoids work fine. For me don't work two with this imports: from PyQt4.QtCore import * from PyQt4.QtGui import * from PyKDE4.plasma import Plasma from PyKDE4 import plasmascript from PyQt4 import QtCore import commands import time
Thanks Vitaly. After following your instructions, this hanging at the last symbol hasn't occurred again. The offending plasmoid was CpuFreqDisplay in my case.
Blargh. We need to get our python act together.
@optiluca: do you still have problems with 4.7.3 ?
Hi. I don't know really, as the offending plasmoid was gmail-notifier, which I since stopped using. I can re-install it and see if I can reproduce the previous behaviour
OK there is no real point in keeping this open anymore- seems to be a configuration problem :|
It's not a configuration problem (as far as I can tell), it's a Gentoo + python plasmoid problem. Anytime a python plasmoid is active, this problem recurs and has been happening to me for ~9 months. See https://bugs.kde.org/show_bug.cgi?id=278943, everyone there having this issue also seems to use Gentoo. Also see the recently opened forum thread here: http://forums.gentoo.org/viewtopic-t-888852-highlight-.html