Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 377337 - kde-4.7.0: hangs on startup, after "K" icon has lit up
Summary: kde-4.7.0: hangs on startup, after "K" icon has lit up
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: AMD64 Linux
: Normal critical (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: kde-python
  Show dependency tree
 
Reported: 2011-08-01 22:18 UTC by optiluca@gmail.com
Modified: 2012-08-01 14:02 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
.xsession-errors from a typical unsuccessful boot (xsession-errors-KDE-bad,27.21 KB, text/plain)
2011-08-01 22:19 UTC, optiluca@gmail.com
Details

Note You need to log in before you can comment on or make changes to this bug.
Description optiluca@gmail.com 2011-08-01 22:18:51 UTC
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
Comment 1 optiluca@gmail.com 2011-08-01 22:19:17 UTC
Created attachment 281783 [details]
.xsession-errors from a typical unsuccessful boot
Comment 2 Andreas K. Hüttel archtester gentoo-dev 2011-08-02 20:56:11 UTC
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?
Comment 3 optiluca@gmail.com 2011-08-02 22:09:56 UTC
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)
Comment 4 optiluca@gmail.com 2011-08-02 22:19:48 UTC
I believe the last line of .xsession-errors refers to me switching to the terminal actually
Comment 5 Stefan Fuchs 2011-08-25 11:23:59 UTC
I can confirm that. Same thing happens on my system.
Comment 6 Vitaliy V. Osypenko 2011-08-31 15:37:39 UTC
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
Comment 7 Stefan Fuchs 2011-09-05 22:28:13 UTC
Thanks Vitaly. After following your instructions, this hanging at the last symbol hasn't occurred again. The offending plasmoid was CpuFreqDisplay in my case.
Comment 8 Andreas K. Hüttel archtester gentoo-dev 2011-09-06 21:09:41 UTC
Blargh. We need to get our python act together.
Comment 9 Andreas K. Hüttel archtester gentoo-dev 2011-11-05 21:13:36 UTC
@optiluca: do you still have problems with 4.7.3 ?
Comment 10 optiluca@gmail.com 2011-11-06 00:56:01 UTC
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
Comment 11 Andreas K. Hüttel archtester gentoo-dev 2011-11-12 17:24:27 UTC
OK there is no real point in keeping this open anymore- seems to be a configuration problem :|
Comment 12 porternw.tmp 2012-08-01 14:02:31 UTC
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