apport-gtk crashed with IOError in _read_eof(): CRC check failed 0xd4a6ed19 != 0x24689064
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apport (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
I received this, and several other errors upon login from a restart that I performed just after updating and running dist-upgrade. I actually initially had issues logging in, I'd enter my password and it would send me back to the login screen over and over, so I had to restart again. This time I was able to enter my password and log-in. Although, immediately after logging in, a bunch of old windows were displayed for a moment, then went away to reveal my expected desktop. It was at that point that I received several errors including this.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: apport-gtk 2.6.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Mon Oct 1 22:15:21 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: apport
Title: apport-gtk crashed with IOError in _read_eof(): CRC check failed 0xd4a6ed19 != 0x24689064
UpgradeStatus: Upgraded to quantal on 2012-10-01 (1 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers
| Tory (tory-andrew-law) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| Changed in apport (Ubuntu): | |
| importance: | Undecided → Medium |
| visibility: | private → public |
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 #1059938, 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.