Opened 9 years ago
Last modified 9 years ago
#278 assigned defect
winswitch applet freezes KDE plasma-desktop
Reported by: | cd311 | Owned by: | cd311 |
---|---|---|---|
Priority: | major | Milestone: | 0.11 |
Component: | Global | Keywords: | winswitch_applet, KDE, plasma_desctop, freeze |
Cc: |
Description
Hi
as mentioned in https://bugs.kde.org/show_bug.cgi?id=341495
winswitch_applet 0.12.21-1 freezes the plasma-desktop application of KDE 4.14.2 after maybe an hour of running with the error message:
void DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "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."
It was indicated that this is due to a "faulty plasma widget".
with regards
christian
Change History (3)
comment:1 follow-up: 2 Changed 9 years ago by
Milestone: | → 0.11 |
---|---|
Owner: | set to cd311 |
Status: | new → assigned |
comment:2 Changed 9 years ago by
How can I get a backtrace? I use a normal plasma-desktop from the kubuntu ppa backports. As far as I know there are no packages with debug symbols. Would those backtraces even be of any use?
The problem occurs after roughly an hour. Give or take 15 minutes. It never happened directly after the start of winswitch.
christian
comment:3 Changed 9 years ago by
If you start the winswitch_applet
from a terminal, you should be able to control-C it when the problem occurs, or even better would be to first send a SIGUSR1 (kill -SIGUSR1 $THEPIDOFTHEAPPLET
) which should dump what all the threads are doing - maybe one is stuck.
gdb backtraces without debug symbols are hard to read, but sometimes not completely hopeless.. worth a shot!
Can you get us a gdb backtrace of what winswitch_applet is doing when KDE plasma desktop is spinning at 100%?
Does this happen straight away or after 1 hour or more?
I may have fixed a similar bug in xpra: we needed to create the widget only after the main loop is running. But this manifested itself as a broken systray on start.