Bug 907919

Created attachment 693386 [details]
File: backtrace

Created attachment 693387 [details]
File: cgroup

Created attachment 693388 [details]
File: core_backtrace

Created attachment 693389 [details]
File: dso_list

Created attachment 693390 [details]
File: environ

Created attachment 693391 [details]
File: limits

Created attachment 693392 [details]
File: maps

Created attachment 693393 [details]
File: open_fds

Created attachment 693394 [details]
File: proc_pid_status

Created attachment 693396 [details]
File: var_log_messages

Starting up Fedora.  Error appeared after login.

backtrace_rating: 4
Package: nepomuk-core-4.9.5-1.fc18
OS Release: Fedora release 18 (Spherical Cow)

Reboot after updates installed (24/2/2013)

backtrace_rating: 4
Package: nepomuk-core-4.9.5-1.fc18
OS Release: Fedora release 18 (Spherical Cow)

I believe this should end up as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=915070

backtrace_rating: 4
Package: nepomuk-core-4.9.5-1.fc18
OS Release: Fedora release 18 (Spherical Cow)

at the startup

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.4-202.fc18.x86_64
package:        nepomuk-core-4.10.1-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
uid:            1000
ureports_counter: 3

Started after update to KDE 4.10.2 and appears right after login.

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.5-201.fc18.x86_64
package:        nepomuk-core-4.10.1-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
uid:            1000
ureports_counter: 1
xsession_errors:

Date/Time shows it happend during shutdown.

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.5-201.fc18.x86_64
package:        nepomuk-core-4.10.1-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
uid:            500
ureports_counter: 1

Since I also reported this bug, I now found a missing file over the nepomuk settings menu. This is the message:

the name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files

I found it cause my nepomuk has a file index of 0 files.

Don't know if you already know that problem/bug. pls contact me if it could be helpful for you and so for us all.

During system boot this error has happened multiple times; on more than one occassion, I had no keyboard or mouse activity until after a system reboot.  This has happened since kernel 3.8.5-201.x86_64 as well as with the newer kernel 3.8.6-203.x86_64.

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.6-203.fc18.x86_64
package:        nepomuk-core-4.10.1-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
uid:            1000
ureports_counter: 2

I had just started my computer when this occured.

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.6-203.fc18.x86_64
package:        nepomuk-core-4.10.1-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
uid:            1000
ureports_counter: 1

I have no real idea how this happened.  Abrt just popped up saying nepomukserver had died.

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.6-203.fc18.x86_64
package:        nepomuk-core-4.10.1-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
uid:            431
ureports_counter: 1
xsession_errors:

nepomuk crashed just after opening a new session (as usual...)

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.7-201.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
xsession_errors:

I hit CTRL-Q in kmail at the time that ABRT tells me this bug occurred.

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.8.8-202.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: 1
xsession_errors:

This occured when using the Activity Bar to switch activities.

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.9.10-200.fc18.x86_64
package:        nepomuk-core-4.10.4-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1000
xsession_errors:

I am not sure how it happened.  Not even sure what nepomukserver does.  

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.9.10-200.fc18.x86_64
package:        nepomuk-core-4.10.5-1.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
reported_to:    uReport: BTHASH=608360993c497bc1998a8edc1185e42437963a40
runlevel:       N 5
uid:            1000
xsession_errors:

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.