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/nepomukserver crash_function: exit kernel: 3.6.5-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (1 frames) : #25 exit at exit.c:100
Created attachment 641319 [details] File: core_backtrace
Created attachment 641320 [details] File: environ
Created attachment 641321 [details] File: event_log
Created attachment 641322 [details] File: backtrace
Created attachment 641323 [details] File: limits
Created attachment 641324 [details] File: cgroup
Created attachment 641325 [details] File: smolt_data
Created attachment 641326 [details] File: executable
Created attachment 641327 [details] File: maps
Created attachment 641328 [details] File: dso_list
Created attachment 641329 [details] File: proc_pid_status
Created attachment 641330 [details] File: open_fds
Crash reported right after login. backtrace_rating: 4 Package: nepomuk-core-4.9.4-2.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Started computer backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
It occurred immediately after reboot. I had done a yum update immediately before and made sure my workstation was current before rebooting. backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I didn't have a red hat bug reporting account backtrace_rating: 4 Package: nepomuk-core-4.9.5-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
On a regular logon to KDE. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: exit executable: /usr/bin/nepomukserver kernel: 3.8.3-103.fc17.x86_64 package: nepomuk-core-4.10.1-1.fc17 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 51911 ureports_counter: 1
Nothing special. Just login, nothing else, then error message appears. Thats all. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: exit executable: /usr/bin/nepomukserver kernel: 3.8.12-100.fc17.x86_64 package: nepomuk-core-4.10.2-2.fc17 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1
When logging in, desktop did not display, but mouse cursor was visible and active. Pressing Ctrl-Alt-Delete gave the option to logout, turn off or restart the computer. I logged out and then logged in and desktop was working properly. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: exit executable: /usr/bin/nepomukserver kernel: 3.6.9-2.fc17.x86_64 package: nepomuk-core-4.10.2-2.fc17 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1 xsession_errors:
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.
kmail was unable to retrieve mail; the fetch threads for all email accounts were all hung. Attempted to restart akonadi from the k-control center, but akonadi would not restart. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: exit executable: /usr/bin/nepomukserver kernel: 3.9.10-100.fc17.x86_64 package: nepomuk-core-4.10.4-1.fc17 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1057 ureports_counter: 1 xsession_errors:
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.