[printers]: gnome-control-center crashed with SIGSEGV in magazine_chain_pop_head()

Bug #1232485 reported by Ubuntu Denver
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Adding new printer causes crash. Cannot add a new printer. Continually crashes every time I attempt to add new printer.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu39
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 28 09:38:07 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-22 (6 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
MarkForUpload: True
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: 0x7f525162e9c7 <g_slice_alloc+167>: mov (%rbx),%rax
 PC (0x7f525162e9c7) ok
 source "(%rbx)" (0x656c6269736976) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_markup_parse_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: [printers]: gnome-control-center crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video
usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

Revision history for this message
Ubuntu Denver (ubuntudenver) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x18e1660) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:545
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=0) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:848
 g_slice_alloc (mem_size=mem_size@entry=16) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:1007
 g_slist_prepend (list=0x1d4f3a0, data=0x23b1320) at /build/buildd/glib2.0-2.38.0/./glib/gslist.c:267
 gtk_action_class_init (klass=0x21aff30) at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkaction.c:236

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: - [printers]: gnome-control-center crashed with SIGSEGV in g_slice_alloc()
+ [printers]: gnome-control-center crashed with SIGSEGV in
+ magazine_chain_pop_head()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions

Changed in gnome-control-center (Ubuntu):
status: New → Invalid
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.