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

[Linus Hoppe]

Binary package hint: policykit-1-gnome

Crash shown by apport

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
NonfreeKernelModules: fglrx wl
Architecture: i386
Date: Wed Jun 1 17:35:07 2011
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcCwd: /home/linus
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7166eb7 <g_datalist_id_set_data_full+727>: cmp 0x4(%esi),%edi
 PC (0xb7166eb7) ok
 source "0x4(%esi)" (0x00000024) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: policykit-1-gnome
StacktraceTop:
 g_data_set_internal (datalist=0x8990108, key_id=52, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.28.6/./glib/gdataset.c:325
 g_datalist_id_set_data_full (datalist=0x8990108, key_id=52, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.28.6/./glib/gdataset.c:598
 g_object_unref (_object=0x8990100) at /build/buildd/glib2.0-2.28.6/./gobject/gobject.c:2721
 ?? ()
 __libc_start_main (main=0x804f320, argc=1, ubp_av=0xbfa43274, init=0x804f7e0, fini=0x804f840, rtld_fini=0xb77efa50, stack_end=0xbfa4326c) at libc-start.c:226
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_data_set_internal()
UpgradeStatus: Upgraded to natty on 2011-05-24 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
XsessionErrors: (process:3082): Gtk-WARNING **: Locale not supported by C library.

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