| Summary: | plasma crash after strange amarok related behaviour | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Vít Tuček <vit.tucek> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | aseigo, mike |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Vít Tuček
2011-05-06 08:08:59 UTC
Created attachment 61417 [details] New crash information added by DrKonqi plasma-desktop (0.4) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.0 - What I was doing when the application crashed: Playing music with amarok 2.4.0 - Unusual behavior I noticed: Exactly the same as bug 272598 -- strange plasma icon notifications, slow menu/widget response (though keyboard navigation through virtual desktops worked fine and responsively). After a few iterations of the notification (I've seen up to 15 at times) plasma finally will crash. It may be related to last.fm integration but I'm not sure -- it seems to begin when amarok is switching songs but then will continue several times. Also running ktorrent as noted in bug 270069. Why is #270069 marked resolved? I don't see a resolution listed. -- Backtrace (Reduced): #14 0xb666fd22 in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate (this=0x106d5998, context=0x0) at kernel/qeventdispatcher_glib.cpp:310 #15 0xb666ff2b in QEventDispatcherGlib::QEventDispatcherGlib (this=0xcfeb268, parent=0x0) at kernel/qeventdispatcher_glib.cpp:353 #16 0xb653e894 in QThreadPrivate::createEventDispatcher (data=0xaec5cf0) at thread/qthread_unix.cpp:213 #17 0xb653edd0 in QThreadPrivate::start (arg=0xaec5508) at thread/qthread_unix.cpp:259 [...] |