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

[Samuel Dorsaz]

i was playing with usb wireless mouse connector (logitech unified connector) by put in/out the usb port.
and notice than keyboard keymap disapear and re-apear when you do this.
just after my firefox windows loose the gtk appareance and crash arrive.

and macbookpro trackpad don't work from now
strange ^^

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: wl nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Tue Oct 4 15:35:03 2011
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
SegvAnalysis:
 Segfault happened at: 0x1d7dee: mov 0x8(%esi),%ebp
 PC (0x001d7dee) ok
 source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/libgdk-3.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (11 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin netdev plugdev sambashare users vboxusers www-data

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