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

[Braxton Westbrook]

Binary package hint: policykit-1-gnome

Don't Know What Happend Just Apport Said The polkit-gnome-authentication-agent-1 Crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic-pae 2.6.38-rc2
Uname: Linux 2.6.38-1-generic-pae i686
Architecture: i386
Date: Fri Feb 4 21:19:28 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb78194bb: mov 0x44(%eax),%ecx
 PC (0xb78194bb) ok
 source "0x44(%eax)" (0xaaaaaaee) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: policykit-1-gnome
StacktraceTop:
 ?? () from /usr/lib/libappindicator.so.1
 g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1715): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nm-applet:1725): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 theme_changed_cb (theme=0x9b2a858, user_data=0x9b9e190)
 g_cclosure_marshal_VOID__VOID (closure=0xb5d01760,
 ?? ()

[Espinet François (espinetfrancois)]

It happened to me after trying to clean the computer with the computer-janitor (and failing)
The system is telling me that there is an other manager running (like update manager or Synaptic) whereas there isn't. Although this bug with computer-janitor was reported (and fixed already) it has reappeared again so maybe these two bugs are linked.