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 adapter_changed()

Status in gnome-control-center package in Ubuntu:

Bug description:
  I changed the bluetooth settings and devices. Than I have the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu13
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug 31 08:50:07 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 
  ProcCmdline: gnome-control-center bluetooth
   Segfault happened at: 0xb6d4f57a <g_type_instance_get_private+202>:  mov    
   PC (0xb6d4f57a) ok
   source "(%esi)" (0x00001060) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
   g_type_instance_get_private () from 
   ?? () from /usr/lib/
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/
   ffi_call () from /usr/lib/i386-linux-gnu/
   g_cclosure_marshal_generic () from 
  Title: gnome-control-center crashed with SIGSEGV in 
  UpgradeStatus: Upgraded to quantal on 2012-08-14 (16 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup                            23.90-0ubuntu1
   gnome-control-center-signon         0.0.13-0ubuntu1
   indicator-datetime                  12.10.0-0ubuntu1

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to