system crashed when attempting to set default browser to chromium

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

Bug Description

Unable to change default browser

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu29
ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Jul 2 20:27:37 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-05-16 (47 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130514)
MarkForUpload: True
ProcCmdline: gnome-control-center info
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fc681de7767 <g_slice_alloc+167>: mov (%rbx),%rax
 PC (0x7fc681de7767) ok
 source "(%rbx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL 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 /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gnome-control-center crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 27.3.1-0ubuntu1
 gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1
 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1

Revision history for this message
Peter Pfeiffer (pfeiffep) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x7fc684ef3660) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:545
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=0) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:848
 g_slice_alloc (mem_size=mem_size@entry=16) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:1007
 g_slist_prepend (list=0x7fc6851c6ac0, data=0x7fc685418270) at /build/buildd/glib2.0-2.37.3/./glib/gslist.c:267
 prepend_and_ref_widget (widget=<optimized out>, data=0x7fff20471158) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtktooltip.c:700

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jeremy Bícha (jbicha)
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.