Bug 1608872

Summary: [abrt] GConf2: magazine_cache_trim(): gconfd-2 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Edgar Hoch <edgar.hoch>
Component: GConf2Assignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, john.j5live, mclasen, rhughes, rstrode, sandmann, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/78304b0d7526176ee9a915566cfdc0af991fa7e9
Whiteboard: abrt_hash:de97abd0b53058d80cb888c78467b3725973d960;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 21:58:01 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: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Edgar Hoch 2018-07-26 12:10:48 UTC 
Description of problem:


Version-Release number of selected component:
GConf2-3.2.6-20.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/gconfd-2
crash_function: magazine_cache_trim
executable:     /usr/libexec/gconfd-2
journald_cursor: s=ab41069824404d1e9bafd3e025f6f209;i=24b38;b=9819dd2dc01b4b76ae12b89ad019b25a;m=6475fef31;t=571d9238b20c0;x=ea7a254a69a84ad4
kernel:         4.17.9-200.fc28.x86_64
rootdir:        /
runlevel:       N 3
type:           CCpp
uid:            2024

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_cache_trim at gslice.c:648
 #1 magazine_cache_push_magazine at gslice.c:710
 #2 thread_memory_magazine2_unload at gslice.c:1199
 #3 g_slice_free_chain_with_offset at gslice.c:1199
 #4 markup_dir_free at markup-tree.c:305
 #9 markup_tree_unref at markup-tree.c:197
 #10 ms_destroy at markup-backend.c:930
 #11 destroy_source at markup-backend.c:785
 #12 gconf_source_free at gconf-sources.c:86
 #13 gconf_sources_free at gconf-sources.c:457

Potential duplicate: bug 1543031
Comment 1 Edgar Hoch 2018-07-26 12:10:54 UTC 
Created attachment 1470737 [details]
File: backtrace
Comment 2 Edgar Hoch 2018-07-26 12:10:56 UTC 
Created attachment 1470738 [details]
File: cgroup
Comment 3 Edgar Hoch 2018-07-26 12:10:57 UTC 
Created attachment 1470739 [details]
File: core_backtrace
Comment 4 Edgar Hoch 2018-07-26 12:10:58 UTC 
Created attachment 1470740 [details]
File: cpuinfo
Comment 5 Edgar Hoch 2018-07-26 12:11:00 UTC 
Created attachment 1470741 [details]
File: dso_list
Comment 6 Edgar Hoch 2018-07-26 12:11:01 UTC 
Created attachment 1470742 [details]
File: environ
Comment 7 Edgar Hoch 2018-07-26 12:11:02 UTC 
Created attachment 1470743 [details]
File: exploitable
Comment 8 Edgar Hoch 2018-07-26 12:11:04 UTC 
Created attachment 1470744 [details]
File: limits
Comment 9 Edgar Hoch 2018-07-26 12:11:05 UTC 
Created attachment 1470745 [details]
File: maps
Comment 10 Edgar Hoch 2018-07-26 12:11:07 UTC 
Created attachment 1470746 [details]
File: mountinfo
Comment 11 Edgar Hoch 2018-07-26 12:11:09 UTC 
Created attachment 1470747 [details]
File: open_fds
Comment 12 Edgar Hoch 2018-07-26 12:11:10 UTC 
Created attachment 1470748 [details]
File: proc_pid_status
Comment 13 Ben Cotton 2019-05-02 21:15:18 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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
EOL if it remains open with a Fedora 'version' of '28'.

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 28 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 Ben Cotton 2019-05-28 21:58:01 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.