apport-gtk crashed with EOFError in _read_exact(): Compressed file ended before the end-of-stream marker was reached

[Dawid de Jager]

Upgrade in progress from Ubuntu 12.10 to 13.04 beta
Commands used:
Alt-F2
update-manager -d
Process completed download of packages then proceeded to installation where the error was eventually encountered.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: apport-gtk 2.9.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
Uname: Linux 3.5.0-27-generic x86_64
ApportLog:
 ERROR: apport (pid 11146) Fri Apr 5 16:27:15 2013: called for pid 2838, signal 11, core limit 0
 ERROR: apport (pid 11146) Fri Apr 5 16:27:15 2013: executable: /usr/bin/nautilus (command line "nautilus -n")
 ERROR: apport (pid 11146) Fri Apr 5 16:27:15 2013: debug: session gdbus call: (true,)

 ERROR: apport (pid 11146) Fri Apr 5 16:27:25 2013: wrote report /var/crash/_usr_bin_nautilus.1000.crash
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Fri Apr 5 21:24:20 2013
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2013-03-01 (35 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with EOFError in _read_exact(): Compressed file ended before the end-of-stream marker was reached
UpgradeStatus: Upgraded to raring on 2013-04-05 (0 days ago)
UserGroups:

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rolando Garza (rolandog)]

I encountered several error messages before apport crashed...

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