Description of problem: Unsure exactly what I did to produce this crash, but at the time I was both trying to get Akonadi's Nepomuk feeder to start indexing again (from a "system is busy, indexing suspended" message in akonadiconsole) and had added some folders to Nepomuk's file indexing configuration. Version-Release number of selected component: nepomuk-core-4.9.2-5.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/bin/nepomukservicestub nepomukstorage crash_function: QCoreApplication::postEvent kernel: 3.6.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 QCoreApplication::postEvent at kernel/qcoreapplication.cpp:1339 : #1 QMetaMethod::invoke at kernel/qmetaobject.cpp:1703 : #2 QMetaObject::invokeMethod at kernel/qmetaobject.cpp:1179 : #3 invokeMethod at /usr/include/QtCore/qobjectdefs.h:434 : #4 Nepomuk2::ResourceWatcherManager::createResource at /usr/src/debug/nepomuk-core-4.9.2/services/storage/resourcewatchermanager.cpp:262 : #5 Nepomuk2::ResourceMerger::merge at /usr/src/debug/nepomuk-core-4.9.2/services/storage/resourcemerger.cpp:941 : #6 Nepomuk2::DataManagementModel::storeResources at /usr/src/debug/nepomuk-core-4.9.2/services/storage/datamanagementmodel.cpp:1805 : #7 Nepomuk2::StoreResourcesCommand::runCommand at /usr/src/debug/nepomuk-core-4.9.2/services/storage/datamanagementcommand.h:166 : #8 Nepomuk2::DataManagementCommand::run at /usr/src/debug/nepomuk-core-4.9.2/services/storage/datamanagementcommand.cpp:62 : #9 QThreadPoolThread::run at concurrent/qthreadpool.cpp:107
Created attachment 639329 [details] File: core_backtrace
Created attachment 639330 [details] File: environ
Created attachment 639331 [details] File: backtrace
Created attachment 639332 [details] File: limits
Created attachment 639333 [details] File: cgroup
Created attachment 639334 [details] File: smolt_data
Created attachment 639335 [details] File: xsession_errors
Created attachment 639336 [details] File: executable
Created attachment 639337 [details] File: maps
Created attachment 639338 [details] File: dso_list
Created attachment 639339 [details] File: build_ids
Created attachment 639340 [details] File: proc_pid_status
Created attachment 639341 [details] File: open_fds
Created attachment 639342 [details] File: var_log_messages
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.