Version-Release number of selected component: kde-workspace-4.10.3-1.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/plasma-desktop --nocrashhandler core_backtrace: crash_function: KCrash::defaultCrashHandler executable: /usr/bin/plasma-desktop kernel: 3.9.4-200.fc18.i686.PAE runlevel: N 5 uid: 1000 var_log_messages: Jun 9 22:49:32 Black abrt[5529]: Saved core dump of pid 4392 (/usr/bin/plasma-desktop) to /var/tmp/abrt/ccpp-2013-06-09-22:49:28-4392 (179109888 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 KCrash::defaultCrashHandler at /usr/src/debug/kdelibs-4.10.3/kdeui/util/kcrash.cpp:346 #4 QMetaObject::addGuard at kernel/qobject.cpp:400 #5 QPointer at ../../src/corelib/kernel/qpointer.h:62 #6 takeAt at ../../src/corelib/tools/qlist.h:486 #7 QDeclarativeRepeater::itemsRemoved at graphicsitems/qdeclarativerepeater.cpp:407 #8 qt_static_metacall at .moc/release-shared/moc_qdeclarativerepeater_p.cpp:105 #9 QDeclarativeRepeater::qt_static_metacall at .moc/release-shared/moc_qdeclarativerepeater_p.cpp:93 #10 QMetaObject::activate at kernel/qobject.cpp:3539 #11 QDeclarativeVisualModel::itemsRemoved at .moc/release-shared/moc_qdeclarativevisualitemmodel_p.cpp:160 #12 QDeclarativeVisualDataModel::_q_itemsRemoved at graphicsitems/qdeclarativevisualitemmodel.cpp:1314 Potential duplicate: bug 951987
Created attachment 758995 [details] File: backtrace
Created attachment 758996 [details] File: cgroup
Created attachment 758997 [details] File: dso_list
Created attachment 758999 [details] File: environ
Created attachment 759000 [details] File: limits
Created attachment 759001 [details] File: maps
Created attachment 759002 [details] File: open_fds
Created attachment 759003 [details] File: proc_pid_status
Created attachment 759004 [details] File: xsession_errors
I was using Firefox reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/plasma-desktop --nocrashhandler crash_function: KCrash::defaultCrashHandler executable: /usr/bin/plasma-desktop kernel: 3.10.10-100.fc18.i686.PAE package: kde-workspace-4.10.5-3.fc18 reason: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
The workspace crashes apparently randomdly. Maybe that is related to notifications. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/plasma-desktop --nocrashhandler crash_function: KCrash::defaultCrashHandler executable: /usr/bin/plasma-desktop kernel: 3.10.10-100.fc18.x86_64 package: kde-workspace-4.10.5-3.fc18 reason: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
About once an hour, my plasma desktop crashes, and is relaunched automatically (sometimes with a delay). I have no idea what is the cause. Sorry. The backtrace is difficult to read. The error comes from a QScript, and is related to a QDeclarativeListModel and a QDeclarativeVisualModel. But we cannot know more. :-\ reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/plasma-desktop --nocrashhandler crash_function: KCrash::defaultCrashHandler executable: /usr/bin/plasma-desktop kernel: 3.10.11-100.fc18.x86_64 package: kde-workspace-4.10.5-3.fc18 reason: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
This one is a Qt bug... see also: http://bugs.kde.org/311871 but upstream is having trouble creating a minimal test case. :-/
The crashs occurs several time per day. I have not understood how to reproduce it. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/plasma-desktop --nocrashhandler crash_function: KCrash::defaultCrashHandler executable: /usr/bin/plasma-desktop kernel: 3.10.13-101.fc18.x86_64 package: kde-workspace-4.10.5-3.fc18 reason: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
I am sorry I keep reporting that bug (that was the third time). I forgot I had already reported it. Is there a way to tell abrt I no longer want to be notified of crashes from plasma-desktop? It seems abrt reset the "reported" flag each time the package kde-workspace is upgraded.
*** Bug 1018256 has been marked as a duplicate of this bug. ***
*** Bug 1005433 has been marked as a duplicate of this bug. ***
*** Bug 1017082 has been marked as a duplicate of this bug. ***
I guess ABRT cannot locally detect the report as a duplicate, only the server component figures out it's a duplicate and redirects the report to this bug, that's why the client lets you report the bug multiple times.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.