Description of problem: I tried to shut down the computer from the menu, but it wouldn't shut down or give me a message, so I ran "shutdown -P now" from a shell script. I had recently put a large number of photos and videos on the hard drive, so nepomuk probably had a lot of indexing to do. Version-Release number of selected component: nepomuk-core-4.9.5-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/nepomukservicestub nepomukstorage crash_function: QObject::~QObject() executable: /usr/bin/nepomukservicestub kernel: 3.7.2-204.fc18.x86_64 uid: 1000 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/syscall-template.S:81 #7 qt_safe_poll(pollfd*, int, int, bool) at /lib64/libQtCore.so.4 #8 QProcessPrivate::waitForFinished(int) 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 861653
Created attachment 686350 [details] File: backtrace
Created attachment 686351 [details] File: build_ids
Created attachment 686352 [details] File: cgroup
Created attachment 686353 [details] File: core_backtrace
Created attachment 686354 [details] File: environ
Created attachment 686355 [details] File: limits
Created attachment 686356 [details] File: maps
Created attachment 686357 [details] File: open_fds
I rebooted the computer several hours after installing updates, and the ABRT notification came up when I logged into KDE. This is the first time I've seen it on this machine, but I've reported the same or similar bug that happens now and then on my laptop. The httpd daemon did not start correctly upon reboot, but I suppose that's not related. backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
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.