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

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.

  gnome-control-center crashed with SIGSEGV in

Status in gnome-control-center package in Ubuntu:

Bug description:
  gnome-control-center crashed with SIGSEGV in _start()

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  CrashCounter: 1
  Date: Tue Sep 25 15:11:46 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
  ProcCmdline: gnome-control-center --overview
   Segfault happened at: 0xb77a2db8:    mov    0x4(%ecx),%ebp
   PC (0xb77a2db8) ok
   source "0x4(%ecx)" (0x00000004) not located in a known VMA region (needed 
readable region)!
   destination "%ebp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
   ?? ()
   ?? ()
   _start ()
  Title: gnome-control-center crashed with SIGSEGV in _start()
  UpgradeStatus: Upgraded to quantal on 2012-09-12 (13 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev root sambashare sudo www-data
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup                            23.92-0ubuntu1
   gnome-control-center-signon         0.0.17-0ubuntu1
   indicator-datetime                  12.10.1-0ubuntu1

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to