polkit-gnome-authentication-agent-1 crashed with SIGABRT in __kernel_vsyscall()

[Nick Hatzakis]

I'm using Ubuntu 11.04

This message appears everytime i boot my computer from a 8G usb stick. I have all updates installed except these:
linux-firmware (i have the version 1.52)
linux-generic (i have the version 2.6.38.8.22)
linux-headers-generic (i have the version 2.6.38.8.22)
linux-image-generic (i have the version 2.6.38.8.22)
linux-libc-dev (i have the version 2.6.38-8.42)

I don't know what it is.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri Jul 8 18:51:23 2011
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: policykit-1-gnome
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: polkit-gnome-authentication-agent-1 crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (<unknown>:14915): dee-WARNING **: Transaction from com.canonical.Unity.ApplicationsPlace.RunnerGroupsModel is in the past. Ignoring transaction.

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