Description of problem: the process virtuoso-t started eating way too much resources, so I killed it ... the crash appeared right after that Version-Release number of selected component: nepomuk-core-4.9.5-1.fc18 Additional info: backtrace_rating: 3 cmdline: /usr/bin/nepomukservicestub nepomukstorage crash_function: Soprano::FilterModel::executeQuery executable: /usr/bin/nepomukservicestub kernel: 3.7.8-202.fc18.x86_64 uid: 1000 var_log_messages: Feb 24 15:14:23 kvolny abrt[12333]: Saved core dump of pid 14388 (/usr/bin/nepomukservicestub) to /var/spool/abrt/ccpp-2013-02-24-15:13:59-14388 (153931776 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 Soprano::FilterModel::executeQuery at /usr/src/debug/soprano-2.8.0/soprano/filtermodel.cpp:164 #1 Soprano::Server::ServerConnection::Private::query at /usr/src/debug/soprano-2.8.0/server/serverconnection.cpp:539 #2 Soprano::Server::ServerConnection::Private::_s_readNextCommand at /usr/src/debug/soprano-2.8.0/server/serverconnection.cpp:228 #3 QMetaObject::activate at kernel/qobject.cpp:3537 #5 QAbstractSocketPrivate::canReadNotification at socket/qabstractsocket.cpp:654 #6 event at socket/qnativesocketengine.cpp:1151 #7 QReadNotifier::event at socket/qnativesocketengine.cpp:1148 #8 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4562 #9 QApplication::notify at kernel/qapplication.cpp:4423 #10 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:961 Potential duplicate: bug 865290
Created attachment 702031 [details] File: backtrace
Created attachment 702032 [details] File: build_ids
Created attachment 702033 [details] File: cgroup
Created attachment 702034 [details] File: core_backtrace
Created attachment 702035 [details] File: dso_list
Created attachment 702036 [details] File: environ
Created attachment 702037 [details] File: limits
Created attachment 702038 [details] File: maps
Created attachment 702039 [details] File: open_fds
Created attachment 702040 [details] File: proc_pid_status
Created attachment 702041 [details] File: smolt_data
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.