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

[Yura Tolstik]

Binary package hint: gnome-settings-daemon

ubuntu 10.10 with all updates

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-settings-daemon 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Tue Sep 28 17:26:25 2010
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4bf99e <_IO_default_xsputn+14>: call 0x46bb1f
 PC (0x004bf99e) ok
 source "0x46bb1f" (0x0046bb1f) ok
 destination "(%esp)" (0xbee8dfec) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_return_if_fail_warning () from /lib/libglib-2.0.so.0
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libubuntuone.so
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libubuntuone.so
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libubuntuone.so
Title: gnome-settings-daemon crashed with SIGSEGV in g_return_if_fail_warning()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2971): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:2970): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (Do:2970): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

[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 #633167, 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.