Binary package hint: gksu
I left my computer, and about an hour later, returned to it. This crash had occurred, and the crash report was ready to send. I do not know the reason for the crash.
I do have an external USB hard drive that contains some corrupted data and may be failing. When I have been heavily accessing it, occasionally my computer slows to a crawl for up to about 30 minutes. CPU usage is not increased during this time. I was experiencing some slowdown when I returned to my computer, and I had been accessing the data on that hard drive with an application (run as a limited user) before I had left my computer. The application is audacious2. It had terminated abnormally while I was away, but I don't know whether that was before or after this crash occurred. The abnormal termination of audacious2 was not a segfault, so I don't think it's the same as the more common crash that audacious2 has produced on my system in this situation (Bug 691378).
I don't know if any of that is related to this crash. It quite possibly is not. I don't have any details on the crash of audacious2 that occurred shortly before or after this crash.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gksu 2.0.2-2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
Architecture: amd64
Date: Thu Dec 23 22:58:14 2010
ExecutablePath: /usr/bin/gksu
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
ProcCmdline: /usr/bin/gksu --message <span\ weight="bold"\ size="larger">Please\ enter\ your\ password\ to\ access\ problem\ reports\ of\ system\ programs</span> /usr/share/apport/apport-gtk
ProcEnviron:
LANGUAGE=en_US.utf8
LANG=en_US.utf8
LC_MESSAGES=en_US.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fc75656eaf0 <gdk_draw_pixbuf+112>: mov (%rbx),%rdx
PC (0x7fc75656eaf0) ok
source "(%rbx)" (0x696e7261772d676f) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
gdk_draw_pixbuf () from /usr/lib/libgdk-x11-2.0.so.0
?? () from /usr/lib/libgksu2.so.0
g_main_dispatch (context=0x1be4dd0) at /build/buildd/glib2.0-2.26.1/glib/gmain.c:2149
g_main_context_dispatch (context=0x1be4dd0) at /build/buildd/glib2.0-2.26.1/glib/gmain.c:2702
g_main_context_iterate (context=0x1be4dd0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at /build/buildd/glib2.0-2.26.1/glib/gmain.c:2780
Title: gksu crashed with SIGSEGV in gdk_draw_pixbuf()
UserGroups: adm admin cdrom lpadmin plugdev sambashare
I now believe that this crash had not actually occurred before I returned to my computer. It seems that a different crash had occurred (which apport was unable to generate a report for, since it was an assertion failure where the message could not be retrieved--the crash was in network-manager). I clicked Apport's panel (notification area) icon to try to report it, which caused gksu to run, and then gksu crashed. So the above information about my ailing hard drive is (even) less likely to be relevant.