gnome-settings-daemon crashed with signal 5 in xkl_process_error()

[Mark Rabideau]

new upgrade has cause entire desktop to vanish -- most unity settings are destroyed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.91-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 9 09:21:10 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 xkl_process_error () from /usr/lib/libxklavier.so.16
 _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
UpgradeStatus: Upgraded to oneiric on 2011-09-09 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-panel:2141): Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion `extra_space >= 0' failed
 (gnome-panel:2141): Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion `extra_space >= 0' failed
 (gnome-panel:2141): Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion `extra_space >= 0' failed
 (gnome-panel:2141): Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion `extra_space >= 0' failed
 (update-manager:3077): Gtk-WARNING **: Attempting to add a widget with type aptdaemon+gtk3widgets+AptProgressDialog to a GtkWindow, but as a GtkBin subclass a GtkWindow can only contain one widget at a time; it already contains a widget of type GtkVBox

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