Bug 1592215

Summary: [abrt] gnome-control-center: slab_allocator_free_chunk(): gnome-control-center killed by SIGSEGV
Product: [Fedora] Fedora Reporter: igor <gigor44>
Component: gnome-control-centerAssignee: Pete Walter <walter.pete>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: evamarilyn.vj, jan.public, jeff.linahan, lothiraldan, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9bdca07966c3746be7abf78cc32dc7e6bc16e5e7
Whiteboard: abrt_hash:265cd0a7f48b478e00d68666e2dec39b89a58f9b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:05:08 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 igor 2018-06-18 08:12:34 UTC 
Version-Release number of selected component:
gnome-control-center-3.28.2-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        gnome-control-center
crash_function: slab_allocator_free_chunk
executable:     /usr/bin/gnome-control-center
journald_cursor: s=be18f9cc67af46bba28a9f2dfbc75e92;i=11917;b=b0c083286a9e4342ad9a1bbfc68e898c;m=19fb84225;t=56ee60f3a74fc;x=71d2e58f91332d1f
kernel:         4.16.15-300.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 slab_allocator_free_chunk at gslice.c:1366
 #1 magazine_cache_trim at gslice.c:679
 #2 magazine_cache_push_magazine at gslice.c:710
 #3 thread_memory_magazine2_unload at gslice.c:1118
 #4 g_slice_free1 at gslice.c:1118
 #5 g_slist_foreach at gslist.c:862
 #6 pango_layout_line_unref at ../pango/pango-layout.c:4061
 #7 pango_layout_clear_lines at ../pango/pango-layout.c:2855
 #8 layout_changed at ../pango/pango-layout.c:1271
 #9 pango_layout_set_attributes at ../pango/pango-layout.c:614
Comment 1 igor 2018-06-18 08:12:39 UTC 
Created attachment 1452546 [details]
File: backtrace
Comment 2 igor 2018-06-18 08:12:41 UTC 
Created attachment 1452547 [details]
File: cgroup
Comment 3 igor 2018-06-18 08:12:43 UTC 
Created attachment 1452548 [details]
File: core_backtrace
Comment 4 igor 2018-06-18 08:12:44 UTC 
Created attachment 1452549 [details]
File: cpuinfo
Comment 5 igor 2018-06-18 08:12:47 UTC 
Created attachment 1452550 [details]
File: dso_list
Comment 6 igor 2018-06-18 08:12:48 UTC 
Created attachment 1452551 [details]
File: environ
Comment 7 igor 2018-06-18 08:12:50 UTC 
Created attachment 1452552 [details]
File: exploitable
Comment 8 igor 2018-06-18 08:12:51 UTC 
Created attachment 1452553 [details]
File: limits
Comment 9 igor 2018-06-18 08:12:55 UTC 
Created attachment 1452554 [details]
File: maps
Comment 10 igor 2018-06-18 08:12:57 UTC 
Created attachment 1452555 [details]
File: mountinfo
Comment 11 igor 2018-06-18 08:12:59 UTC 
Created attachment 1452556 [details]
File: open_fds
Comment 12 igor 2018-06-18 08:13:01 UTC 
Created attachment 1452557 [details]
File: proc_pid_status
Comment 13 Jeff Linahan 2018-10-21 03:50:17 UTC 
*** Bug 1641315 has been marked as a duplicate of this bug. ***
Comment 14 Boris Feld 2018-10-31 13:02:27 UTC 
Similar problem has been detected:

I just tried detecting my sleeping printer over the network

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        gnome-control-center printers
crash_function: slab_allocator_free_chunk
executable:     /usr/bin/gnome-control-center
journald_cursor: s=ca248d9a4fcc4b5089677cd70c8fc8e3;i=3371d0;b=1d24cea2dc8446f99a7917cce7749b17;m=4b7fa194e4;t=57985c263dfc0;x=569ba3f552baebe2
kernel:         4.18.14-200.fc28.x86_64
package:        gnome-control-center-3.28.2-1.fc28
reason:         gnome-control-center killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 Ben Cotton 2019-05-02 20:32:12 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 16 Ben Cotton 2019-05-28 23:05:08 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.