polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_datalist_id_set_data_full()

[alfe08]

With the starting of the session, the keyboard is in qwerty then qu' it should be in azerty

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 2 22:06:56 2011
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110202)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcCwd: /home/alfe
ProcEnviron:
 LANGUAGE=fr_FR:fr_FR.UTF-8:fr:en_GB:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6fc9ff59c8 <g_datalist_id_set_data_full+744>: cmp 0x8(%rax),%r12d
 PC (0x7f6fc9ff59c8) ok
 source "0x8(%rax)" (0x7375424437) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: policykit-1-gnome
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/libglib-2.0.so.0
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nm-applet:1406): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion `GTK_IS_WIDGET (widget)' failed
 (nautilus:1400): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

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