Bug 981377

Summary: [abrt] nepomuk-core-4.10.4-1.fc19: exit: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: G. Hynes <ghynes>
Component: nepomuk-coreAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bob53181, fac_franky, jreznik, jsedlak, kevin, ltinkl, puntogil, rdieter, rnovacek, spichka21, stealthcipher, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7fe33ce567ac3e9ba4c5fb745bc3c615117af586
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 15:51:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description G. Hynes 2013-07-04 15:00:37 UTC 
Version-Release number of selected component:
nepomuk-core-4.10.4-1.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.9.8-300.fc19.x86_64
runlevel:       N 5
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (1 frames)
 #14 exit at exit.c:99

Potential duplicate: bug 874956
Comment 1 G. Hynes 2013-07-04 15:00:42 UTC 
Created attachment 768845 [details]
File: backtrace
Comment 2 G. Hynes 2013-07-04 15:00:45 UTC 
Created attachment 768846 [details]
File: cgroup
Comment 3 G. Hynes 2013-07-04 15:00:49 UTC 
Created attachment 768847 [details]
File: core_backtrace
Comment 4 G. Hynes 2013-07-04 15:00:52 UTC 
Created attachment 768848 [details]
File: dso_list
Comment 5 G. Hynes 2013-07-04 15:00:55 UTC 
Created attachment 768849 [details]
File: environ
Comment 6 G. Hynes 2013-07-04 15:01:01 UTC 
Created attachment 768850 [details]
File: limits
Comment 7 G. Hynes 2013-07-04 15:01:05 UTC 
Created attachment 768851 [details]
File: maps
Comment 8 G. Hynes 2013-07-04 15:01:08 UTC 
Created attachment 768852 [details]
File: open_fds
Comment 9 G. Hynes 2013-07-04 15:01:11 UTC 
Created attachment 768853 [details]
File: proc_pid_status
Comment 10 G. Hynes 2013-07-04 15:01:18 UTC 
Created attachment 768854 [details]
File: var_log_messages
Comment 11 Evgeny 2013-07-12 18:37:27 UTC 
On desktop starting.

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.9.9-301.fc19.x86_64
package:        nepomuk-core-4.10.4-1.fc19
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1000
xsession_errors:
Comment 12 gil cattaneo 2013-07-25 07:10:10 UTC 
after latest updated and system reboot 

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: exit
executable:     /usr/bin/nepomukserver
kernel:         3.9.9-302.fc19.i686
package:        nepomuk-core-4.10.5-1.fc19
reason:         Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1000
xsession_errors:
Comment 13 Fedora End Of Life 2015-01-09 18:40:09 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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.
Comment 14 Fedora End Of Life 2015-02-17 15:51:03 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.