Bug 163816 - Plasma crashes and doesnt recover when I try to lock from app launcher
Summary: Plasma crashes and doesnt recover when I try to lock from app launcher
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-11 20:40 UTC by Eduardo Sampaio
Modified: 2008-06-30 21:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eduardo Sampaio 2008-06-11 20:40:52 UTC
Version:            (using KDE 4.0.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

A few times (about 10-20% of the attempts) when I am trying to lock my notebook via application launcher, the plasma crashes and does not recover like with other crashes I experienced.
I have to kill X via ctrl+alt+backspace.
Then, when I try to re-login the loading animation freezes on the desktop icon and displays an error message I cant remember now, but says something about the access to .ICEauthority file.
I've found out the .ICEauthority owner is changed to root and I can only log in back to KDE4 when sudo chown the .ICEauthority back to my user. 

Hope to help you guys, rock on KDE4 is ruling!!
Comment 1 Aaron J. Seigo 2008-06-25 19:07:32 UTC
you can also Alt+f2 to get the run dialog (instead of hard killing X); in any case, i can't reproduce this in the least, we'd need a backtrace to help address it and i'd be really interested if this problem is resolved in 4.1 code in any case.
Comment 2 Eduardo Sampaio 2008-06-25 19:57:50 UTC
I can't do that because it usually happens when kded4 has crashed too, so either I'm lucky and have a konsole open at the desktop so I can re-start plasma or I have to hard kill X.
Think this might be related? How can I backtrace it for you?
The kded4 problem happens a lot, I found a way around but its a pain in the ass to have to restart it every 20 min or so using:
> kded4
> qdbus org.kde.kded /kded loadModule kdedglobalaccel

This is what happens: 
eduardo@Iluvatar:~$ kded4
kded(7311) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded:  "NetworkManager"
eduardo@Iluvatar:~$ qdbus org.kde.kded /kded loadModule kdedglobalaccel
true

After a while this is printed on the konsole signalling kded crashed:
KDE Daemon (kded) already running.
kded(7532): Communication problem with  "kded" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

Don't know if its related or not or if I should open another bug or if this is duplicate or already fixed, maybe you can shed some light on this issue?
And help me out on how to generate the backtrace to send you.

Thanks in advance.

Eduardo Sampaio
Comment 3 Eduardo Sampaio 2008-06-25 20:12:49 UTC
It crashed again, and I got some information that was spit on the konsole. Does this help?

<unknown program name>(10170)/ checkComposite: Plasma lacks an argb visual 0x0 0
<unknown program name>(10170)/ checkComposite: Plasma is COMPOSITE-less on 0x8054b68
QFSFileEngine::open: No file name specified
QLayout: Attempting to add QLayout "" to Plasma::Dialog "", which already has a layout
QLayout: Attempting to add QLayout "" to PanelController "", which already has a layout
QPainter::begin: Cannot paint on a null pixmap
QPainter::end: Painter not active, aborted
Plasma crashed, attempting to automatically recover
KCrash: Application 'plasma' crashing...
sock_file=/home/eduardo/.kde4/socket-Iluvatar/kdeinit4__0
plasma(10170): Communication problem with  "plasma" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

eduardo@Iluvatar:~$ <unknown program name>(10175)/ checkComposite: Plasma lacks an argb visual 0x0 0
<unknown program name>(10175)/ checkComposite: Plasma is COMPOSITE-less on 0x8054b68
QFSFileEngine::open: No file name specified
QLayout: Attempting to add QLayout "" to Plasma::Dialog "", which already has a layout
QLayout: Attempting to add QLayout "" to PanelController "", which already has a layout
eduardo@Iluvatar:~$ QPainter::begin: Cannot paint on a null pixmap
QPainter::end: Painter not active, aborted
plasma(10175): Communication problem with  "plasma" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

Eduardo Sampaio
Comment 4 Aaron J. Seigo 2008-06-25 23:06:00 UTC
thanks for following up on this report; you can find out how to create good backtraces here:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 5 Eduardo Sampaio 2008-06-30 21:45:28 UTC
Thanks for the help Aaron, Ive installed all dbg packages and gdb and I think it was solved in one of the updates since it never happened again...

I'll close the bug and if it happens again hopefully I'll have the backtrace to send.

Best regards and sorry if I wasted your time.

Eduardo Sampaio