** 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/843636

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

Bug description:
  Ubuntu 11.10 Testing under kvm

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.1.91-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Tue Sep  6 19:22:28 2011
  Disassembly: => 0x8f08359:    Cannot access memory at address 0x8f08359
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x8f08359:     Cannot access memory at address 
0x8f08359
   PC (0x08f08359) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  Stacktrace:
   #0  0x08f08359 in ?? ()
   No symbol table info available.
   #1  0x09e2b070 in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame inner to this frame (corrupt stack?)
  StacktraceTop:
   ?? ()
   ?? ()
  Title: gnome-settings-daemon crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to