gnome-control-center crashed with SIGSEGV in slab_allocator_free_chunk()

Bug #1727027 reported by Mike Vilot
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Fresh install of 17.10
Had just printed a Test Page to HP network printer, then used Settings to disable TouchPad.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 14:37:17 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-10-24 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f32f54a9007: mov %rax,0x18(%rsi)
 PC (0x7f32f54a9007) ok
 source "%rax" ok
 destination "0x18(%rsi)" (0x4854415056455c) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_key_file_get_string_list () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
Title: gnome-control-center crashed with SIGSEGV in g_slice_free_chain_with_offset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mike Vilot (mikevilot) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 slab_allocator_free_chunk (chunk_size=chunk_size@entry=16, mem=mem@entry=0x56019065fc60) at ../../../../glib/gslice.c:1366
 magazine_cache_trim (allocator=0x7f32f5754c20 <allocator>, stamp=<optimized out>, ix=32766) at ../../../../glib/gslice.c:679
 magazine_cache_push_magazine (ix=ix@entry=0, magazine_chunks=<optimized out>, count=<optimized out>) at ../../../../glib/gslice.c:710
 thread_memory_magazine2_unload (tmem=<optimized out>, ix=0) at ../../../../glib/gslice.c:809
 g_slice_free_chain_with_offset (mem_size=16, mem_chain=<optimized out>, next_offset=8) at ../../../../glib/gslice.c:1199

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: - gnome-control-center crashed with SIGSEGV in
- g_slice_free_chain_with_offset()
+ gnome-control-center crashed with SIGSEGV in slab_allocator_free_chunk()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-control-center (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.