| Summary: | Plasma Crash from Panel Tool Box | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Ron <motlreg97> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | aseigo, cfeck, fshaked, mingomax, RunebladeOmega, uanagana |
| Priority: | NOR | ||
| Version: | 4.6.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Ron
2011-04-23 08:58:03 UTC
were you running amarok at the time? (In reply to comment #1) > were you running amarok at the time? I was not running Amarok and since I have disabled the desktop effects(DE) I have not been able to reproduce the problem. I suspect this issue and another crash I had reported were both due to DE being active. As I am now unable to reproduce the error, even after activating DE, I do not have any objections to closing this report and waiting to see if it happens again. Thank you. Sounds like the RSS widget needs to limit the number of feeds it fetches at a time, otherwise it will crash because of open file limit. *** Bug 274210 has been marked as a duplicate of this bug. *** *** Bug 275042 has been marked as a duplicate of this bug. *** *** Bug 262454 has been marked as a duplicate of this bug. *** Created attachment 63779 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
I had Chromium, Dolphin, and Okular (two windows) open on Kubuntu 11.04 (KDE 4.6.2) when the desktop disappeared (black screen, no widgets or panel). The desktop returned to normal a few minutes later, along with a notice that Plasma had crashed...
-- Backtrace (Reduced):
#12 0x00007fdd14b571c1 in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate (this=0x13956a30, context=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:310
#13 0x00007fdd14b572a0 in QEventDispatcherGlib::QEventDispatcherGlib (this=0x35e3fc0, parent=0x0) at kernel/qeventdispatcher_glib.cpp:357
#14 0x00007fdd14a44587 in QThreadPrivate::createEventDispatcher (data=0x35c2a90) at thread/qthread_unix.cpp:261
#15 0x00007fdd14a45156 in QThreadPrivate::start (arg=0x35c28a0) at thread/qthread_unix.cpp:313
#16 0x00007fdd0cc2ad8c in start_thread (arg=0x7fdce79d4700) at pthread_create.c:304
Created attachment 63939 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
Running Kubuntu 11.04, Plasama reported a sudden, spontaneous crash while no resource-intensive applications were running (Kopete, Chromium, and Okular).
-- Backtrace (Reduced):
#12 0x00007f92b72e01c1 in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate (this=0x17a95fc0, context=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:310
#13 0x00007f92b72e02a0 in QEventDispatcherGlib::QEventDispatcherGlib (this=0x14bd6710, parent=0x0) at kernel/qeventdispatcher_glib.cpp:357
#14 0x00007f92b71cd587 in QThreadPrivate::createEventDispatcher (data=0x226bcb0) at thread/qthread_unix.cpp:261
#15 0x00007f92b71ce156 in QThreadPrivate::start (arg=0x3481df0) at thread/qthread_unix.cpp:313
#16 0x00007f92af3b3d8c in start_thread (arg=0x7f92891b1700) at pthread_create.c:304
Thank you for this crash report and helping to improve our software. Unfortunately we were not able to work on this specific report yet. Nowadays the version this crash was reported against is no longer maintained and this makes it very difficult to work on this report as the source code might have changed and the information in the backtrace is no longer valid. Also it is quite likely that this problem got fixed in a later version. Crash reports are very often reported multiple times. If you are able to reproduce this crash with the latest version of KDE Plasma (4.10.3) please reopen this report and adjust the version information in the dropdown above and please also include a new backtrace as generated by the crash reporting tool. Please also make sure that the steps on how to reproduce the crash are precise and correct. Thank you! |