the bug is years old without activity nor new report and the code
changed quite a lot since, closing, feel free to register new bugs if
you have issues in newer versions though

** 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.

  [power]: gnome-control-center crashed with SIGSEGV in

Status in gnome-control-center package in Ubuntu:

Bug description:
  This happened after opening the power settings. I opened it, didn't
  click anything, and then it closed without warning.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.90-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  Date: Sun Mar  4 09:41:04 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: gnome-control-center power
   PATH=(custom, no user)
   Segfault happened at: 0x7f09bcd7b817 <g_cancellable_is_cancelled+7>: mov    
   PC (0x7f09bcd7b817) ok
   source "0x18(%rdi)" (0x00000019) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
   g_cancellable_is_cancelled () from /usr/lib/x86_64-linux-gnu/
   g_dbus_connection_send_message_with_reply () from 
   ?? () from /usr/lib/x86_64-linux-gnu/
   ?? () from /usr/lib/x86_64-linux-gnu/
   g_dbus_proxy_call () from /usr/lib/x86_64-linux-gnu/
  Title: [power]: gnome-control-center crashed with SIGSEGV in 
  UpgradeStatus: Upgraded to precise on 2012-01-28 (36 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
   deja-dup           21.90-0ubuntu1
   gnome-bluetooth    3.2.2-0ubuntu3
   indicator-datetime 0.3.90-0ubuntu1

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to