*** This bug is a duplicate of bug 932953 ***
    https://bugs.launchpad.net/bugs/932953


** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/933317

Title:
  gsd-backlight-helper crashed with SIGSEGV in __libc_start_main()

Status in “gnome-settings-daemon” package in Ubuntu:
  New

Bug description:
  changing screen lock options

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-settings-daemon 3.3.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
  Uname: Linux 3.2.0-16-generic-pae i686
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Thu Feb 16 08:29:29 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-backlight-helper
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120215)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-backlight-helper 
--get-max-brightness
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x8048f8c:     mov    0x8(%eax),%eax
   PC (0x08048f8c) ok
   source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? ()
   __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
   ?? ()
  Title: gsd-backlight-helper crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/933317/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to