apport-gtk crashed with IOError in _read_eof(): CRC check failed 0x6795d576 != 0x148ce802L

[Bob Bib]

Sudden crash while viewing a crash report info.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 2.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportLog:

ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
CrashReports:
 640:1000:138:51362:2012-04-11 18:55:50.885582000 +0300:2012-04-11 18:55:56.829486108 +0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash
 640:116:138:602133:2012-04-06 19:01:21.634838000 +0300:2012-04-06 19:01:25.814870432 +0300:/var/crash/_usr_lib_x86_64-linux-gnu_colord_colord.116.crash
 640:1000:138:2856352:2012-04-07 00:16:22.645249000 +0300:2012-04-11 18:55:42.633774061 +0300:/var/crash/_usr_lib_ubuntu-sso-client_ubuntu-sso-login.1000.crash
Date: Wed Apr 11 18:55:51 2012
ExecutablePath: /usr/share/apport/apport-gtk
ExecutableTimestamp: 1334064520
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcCwd: /home/mrbb01
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with IOError in _read_eof(): CRC check failed 0x6795d576 != 0x148ce802L
UpgradeStatus: Upgraded to precise on 2012-03-31 (11 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy ftp fuse kvm lpadmin netdev plugdev powerdev sambashare tape vboxusers video wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #945593, 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.