Bug 904403

Summary: [abrt] nepomuk-core-4.9.5-1.fc17: g_malloc0: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: kamnu
Component: nepomuk-coreAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: JDavis4102, jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c210bb39649d7f6691a283e79f5456bb9dec5bb9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 01:48:58 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: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: build_ids
none
File: proc_pid_status
none
File: open_fds none

Description kamnu 2013-01-26 14:00:18 UTC
Version-Release number of selected component:
nepomuk-core-4.9.5-1.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
crash_function: g_malloc0
kernel:         3.6.11-5.fc17.x86_64

truncated backtrace:
:Thread no. 1 (4 frames)
: #3 g_malloc0 at gmem.c:189
: #4 thread_memory_from_self at gslice.c:512
: #6 g_slice_free1 at gslice.c:1087
: #7 __nptl_deallocate_tsd at pthread_create.c:157

Comment 1 kamnu 2013-01-26 14:00:22 UTC
Created attachment 688000 [details]
File: environ

Comment 2 kamnu 2013-01-26 14:00:25 UTC
Created attachment 688001 [details]
File: backtrace

Comment 3 kamnu 2013-01-26 14:00:27 UTC
Created attachment 688002 [details]
File: limits

Comment 4 kamnu 2013-01-26 14:00:29 UTC
Created attachment 688003 [details]
File: cgroup

Comment 5 kamnu 2013-01-26 14:00:35 UTC
Created attachment 688004 [details]
File: smolt_data

Comment 6 kamnu 2013-01-26 14:00:37 UTC
Created attachment 688005 [details]
File: executable

Comment 7 kamnu 2013-01-26 14:00:41 UTC
Created attachment 688006 [details]
File: maps

Comment 8 kamnu 2013-01-26 14:00:43 UTC
Created attachment 688007 [details]
File: build_ids

Comment 9 kamnu 2013-01-26 14:00:45 UTC
Created attachment 688008 [details]
File: proc_pid_status

Comment 10 kamnu 2013-01-26 14:00:47 UTC
Created attachment 688009 [details]
File: open_fds

Comment 11 Fedora End Of Life 2013-07-03 23:16:22 UTC
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.

Comment 12 Fedora End Of Life 2013-08-01 01:49:03 UTC
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.