Summary: | Plasma crashes and doesnt recover when I try to lock from app launcher | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | Eduardo Sampaio <esampaio> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Eduardo Sampaio
2008-06-11 20:40:52 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. 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
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 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 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 |