Version-Release number of selected component: nepomuk-core-4.9.4-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QProcess::state executable: /usr/bin/nepomukserver kernel: 3.6.11-3.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QProcess::state at io/qprocess.cpp:1583 #1 ProcessControl::isRunning at /usr/src/debug/nepomuk-core-4.9.4/server/processcontrol.cpp:134 #2 Nepomuk2::ServiceManager::runningServices at /usr/src/debug/nepomuk-core-4.9.4/server/servicemanager.cpp:405 #3 Nepomuk2::Server::quit at /usr/src/debug/nepomuk-core-4.9.4/server/nepomukserver.cpp:158 #5 _dbus_marshal_set_uint32 at dbus-marshal-basic.c:313 #6 _dbus_header_set_serial at dbus-marshal-header.c:412 #7 dbus_message_set_serial at dbus-message.c:259 #8 _dbus_connection_send_preallocated_unlocked_no_update at dbus-connection.c:2022 #9 _dbus_connection_send_preallocated_and_unlock at dbus-connection.c:2060 #10 _dbus_connection_send_and_unlock at dbus-connection.c:2097 Potential duplicate: bug 860713
Created attachment 669400 [details] File: backtrace
Created attachment 669401 [details] File: cgroup
Created attachment 669402 [details] File: core_backtrace
Created attachment 669403 [details] File: dso_list
Created attachment 669404 [details] File: environ
Created attachment 669405 [details] File: limits
Created attachment 669406 [details] File: maps
Created attachment 669407 [details] File: open_fds
Created attachment 669408 [details] File: proc_pid_status
Created attachment 669409 [details] File: var_log_messages
This occurs on login before I do anything. backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Does this at boot time. backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
The bug appeared just after logon backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
this usually happens right at the beginning of my KDE session backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Beats the heck out of me. I'd just booted, and sent a pending email that for some reason kmails/nepomuk wouldn't send earlier. A notification popped up that nepomuk had crashed, and asked if I wanted to report it. So I'm reporting it. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QProcess::state executable: /usr/bin/nepomukserver kernel: 3.8.11-200.fc18.x86_64 package: nepomuk-core-4.10.2-2.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 431 ureports_counter: 2
to start kde backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QProcess::state executable: /usr/bin/nepomukserver kernel: 3.9.2-200.fc18.x86_64 package: nepomuk-core-4.10.2-2.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1
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.