gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke()

[Jonathan Lange]

Does what I type in here even matter?

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.5-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 1 11:34:04 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f32da439700: mov 0x8(%rax),%rcx
 PC (0x7f32da439700) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 g_closure_invoke (closure=0x1546910, return_value=0x0, n_param_values=2, param_values=0x14f4f90, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c:773
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x1520d00, emission_return=0x0, instance_and_params=0x14f4f90) at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3271
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fffd9103d18) at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3002
Title: gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to oneiric on 2011-07-26 (36 days ago)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #836014, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.