error during updates ... policekit indication
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: policykit-1-gnome 0.96-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.34-5.14-generic 2.6.34
Uname: Linux 2.6.34-5-generic i686
Architecture: i386
CheckboxSubmission: e1704bb1fb5034f76b1f1f44a864ccff
CheckboxSystem: 67865677bd9717193325b33f995a8686
Date: Wed Jun 30 20:59:30 2010
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
LANG=nl_NL.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x45b98b: movsbl (%edx),%eax
PC (0x0045b98b) ok
source "(%edx)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: policykit-1-gnome
StacktraceTop:
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors:
(polkit-gnome-authentication-agent-1:1149): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(quicksynergy:1623): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(quicksynergy:1623): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(quicksynergy:1623): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
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 #555033, 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.