Version-Release number of selected component: nepomuk-core-4.9.1-1.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 3 cmdline: /usr/bin/nepomukservicestub nepomukstorage kernel: 3.5.4-2.fc17.i686 truncated backtrace: :Thread no. 1 (8 frames) : #0 ?? : #1 QMetaObject::invokeMethod at kernel/qmetaobject.cpp:1166 : #2 invokeMethod at /usr/include/QtCore/qobjectdefs.h:434 : #3 Nepomuk2::ResourceWatcherManager::changeProperty at /usr/src/debug/nepomuk-core-4.9.1/services/storage/resourcewatchermanager.cpp:219 : #4 Nepomuk2::ResourceMerger::merge at /usr/src/debug/nepomuk-core-4.9.1/services/storage/resourcemerger.cpp:941 : #5 Nepomuk2::DataManagementModel::storeResources at /usr/src/debug/nepomuk-core-4.9.1/services/storage/datamanagementmodel.cpp:1798 : #6 Nepomuk2::StoreResourcesCommand::runCommand at /usr/src/debug/nepomuk-core-4.9.1/services/storage/datamanagementcommand.h:166 : #7 ??
Created attachment 620286 [details] File: core_backtrace
Created attachment 620287 [details] File: environ
Created attachment 620288 [details] File: limits
Created attachment 620289 [details] File: backtrace
Created attachment 620290 [details] File: cgroup
Created attachment 620291 [details] File: maps
Created attachment 620292 [details] File: dso_list
Created attachment 620293 [details] File: open_fds
Created attachment 620294 [details] File: var_log_messages
While the backtrace is different, I'm pretty sure this is the same use-after-free as in bug #858271. (In both bugs, there's a QObject related to file watching which is receiving a signal after having been deleted.) *** This bug has been marked as a duplicate of bug 858271 ***
Bug still present in nepomuk-core-4.9.2-2.fc17 build