Description of problem: The problem occurred right after the reboot. Version-Release number of selected component: nepomuk-core-4.9.5-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/bin/nepomukservicestub nepomukstorage crash_function: QObject::~QObject() kernel: 3.7.6-102.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #1 QObject::~QObject() at /lib64/libQtCore.so.4 : #3 signalHandler at /usr/src/debug/nepomuk-core-4.9.5/servicestub/main.cpp:51 : #4 (anonymous namespace)::signalHandler at /usr/src/debug/nepomuk-core-4.9.5/servicestub/main.cpp:45 : #6 __poll at ../sysdeps/unix/sysv/linux/poll.c:87 : #7 qt_safe_poll(pollfd*, int, int, bool) at /lib64/libQtCore.so.4 : #8 ?? at /lib64/libQtCore.so.4 : #9 QProcess::waitForFinished(int) at /lib64/libQtCore.so.4 : #10 Soprano::VirtuosoController::shutdown at /usr/src/debug/soprano-2.8.0/backends/virtuoso/virtuosocontroller.cpp:219 : #11 Soprano::VirtuosoController::~VirtuosoController at /usr/src/debug/soprano-2.8.0/backends/virtuoso/virtuosocontroller.cpp:89 : #13 QObjectPrivate::deleteChildren() at /lib64/libQtCore.so.4 Potential duplicate bug: 905934
Created attachment 701958 [details] File: core_backtrace
Created attachment 701959 [details] File: environ
Created attachment 701960 [details] File: limits
Created attachment 701961 [details] File: backtrace
Created attachment 701962 [details] File: cgroup
Created attachment 701963 [details] File: smolt_data
Created attachment 701964 [details] File: xsession_errors
Created attachment 701965 [details] File: executable
Created attachment 701966 [details] File: maps
Created attachment 701967 [details] File: dso_list
Created attachment 701968 [details] File: build_ids
Created attachment 701969 [details] File: proc_pid_status
Created attachment 701970 [details] File: var_log_messages
Created attachment 701971 [details] File: open_fds
Steps to reproduce: 1. Login 2. nepomukservicestub dies Session manager is set to start with fresh session.
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.