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

Bug #1010343 reported by vitobrus
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

In impostazioni di sistema non mi permette di variare nulla. Poi chiudendo va in crash

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic x86_64
ApportVersion: 2.1.1-0ubuntu2
Architecture: amd64
Date: Fri Jun 8 08:49:01 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f583cf1e158 <gnome_control_center_show+24>: mov 0x20(%rdx),%rdi
 PC (0x7f583cf1e158) ok
 source "0x20(%rdx)" (0xaaaaaaaaaaaaaaca) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
Stacktrace:
 #0 0x00007f583cf1e158 in gnome_control_center_show ()
 No symbol table info available.
 #1 0x00007f583cf1bba6 in _start ()
 No symbol table info available.
StacktraceTop:
 gnome_control_center_show ()
 _start ()
Title: gnome-control-center crashed with SIGSEGV in gnome_control_center_show()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[1312]: WARNING: Session 'ubuntu' runnable check failed: Uscito con codice 5
 (jockey-gtk:1842): Gtk-CRITICAL **: gtk_icon_set_render_icon_pixbuf: assertion `icon_set != NULL' failed
 (jockey-gtk:1842): Gtk-CRITICAL **: gtk_icon_set_render_icon_pixbuf: assertion `icon_set != NULL' failed
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.2-0ubuntu1
 indicator-datetime 0.3.94-0ubuntu3

Revision history for this message
vitobrus (vitobrus) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gnome_control_center_show (center=0x7f583d7f5800, app=0x7f583d810250) at gnome-control-center.c:1261
 application_command_line_cb (application=0x7f583d810250, command_line=<optimized out>, shell=0x7f583d7f5800) at control-center.c:121
 ffi_call_unix64 () at ../src/x86/unix64.S:75
 ffi_call (cif=cif@entry=0x7fff82451af0, fn=fn@entry=0x7f583cf1b9f0 <application_command_line_cb>, rvalue=<optimized out>, avalue=<optimized out>, avalue@entry=0x7fff824519f0) at ../src/x86/ffi64.c:486
 g_cclosure_marshal_generic (closure=0x7f583dad4620, return_gvalue=0x7fff82451c90, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x7f583cf1b9f0) at /build/buildd/glib2.0-2.33.1/./gobject/gclosure.c:1454

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
tags: added: saucy
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
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: Confirmed → 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.