apport-gtk crashed with struct.error in read32(): unpack requires a bytes object of length 4

Bug #1098197 reported by Timo Jyrinki
208
This bug affects 47 people
Affects Status Importance Assigned to Milestone
Apport
Fix Released
Undecided
Unassigned
apport (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This is on booting to just updated (do-release-upgrade) raring.

  File "/usr/lib/python3/dist-packages/apport/report.py", line 652, in add_gdb_info
    gdb_cmd = self.gdb_command(rootdir)
  File "/usr/lib/python3/dist-packages/apport/report.py", line 1459, in gdb_command
    self['CoreDump'].write(f)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 75, in write
    block = gz.read(1048576)
  File "/usr/lib/python3.3/gzip.py", line 366, in read
    self._read(readsize)
  File "/usr/lib/python3.3/gzip.py", line 455, in _read
    self._read_eof()
  File "/usr/lib/python3.3/gzip.py", line 487, in _read_eof
    crc32 = read32(self.fileobj)
  File "/usr/lib/python3.3/gzip.py", line 69, in read32
    return struct.unpack("<I", input.read(4))[0]
struct.error: unpack requires a bytes object of length 4

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: apport-gtk 2.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Jan 10 16:18:23 2013
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2012-03-16 (299 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
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 struct.error in read32(): unpack requires a bytes object of length 4
UpgradeStatus: Upgraded to raring on 2013-01-10 (0 days ago)
UserGroups:

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
tags: removed: need-duplicate-check
Changed in apport (Ubuntu):
importance: Undecided → Medium
Bryce Harrington (bryce)
description: updated
Logan Rosen (logan)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
David Henningsson (diwic) wrote :

Also happened in Saucy on a daily dist-upgrade.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Confirmed in saucy
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

tags: added: saucy
Revision history for this message
Simplehuman (simplehuman) wrote :

Also confirm this bug after booting PC

Revision history for this message
Kenneth Wrede (kennethwrede) wrote :

Saucy, "apt-get update" after clean install.

Revision history for this message
Kenneth Wrede (kennethwrede) wrote :

... apt-get UPGRADE (of course)

Revision history for this message
Richard Elkins (texadactyl) wrote :

Saucy, "apt-get update" after removing lastfm.

Revision history for this message
Shaharil Ahmad (shaharil-ahmad) wrote :

positive on saucy.

Revision history for this message
Shaharil Ahmad (shaharil-ahmad) wrote :

again on saucy this time after update mir.

Revision history for this message
Shaharil Ahmad (shaharil-ahmad) wrote :

saucy beta affected

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

saucy daily 2013-09-22 affected

Revision history for this message
Michał Karnicki (karni) wrote :

saucy beta 2 affected. Fresh install, after updating the system. Just after booting 4 crash dialogs visible.

tags: added: trusty
dino99 (9d9)
tags: added: i386
Revision history for this message
Benjamin Schmid (benbuntu) wrote :

Any hints on how to workaround this crash on every login?

Revision history for this message
Jean Porcherot (jpo38) wrote :

If this may help: The problem appeared on my machine (Xubuntu 13.10 32bits) after adding/removing video drivers (sudo apt-get install nvidia-current nvidia-common nvidia-173 and later sudo apt-get remove nvidia-current nvidia-common nvidia-173)

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in apport (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in apport (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Richard Elkins (texadactyl) wrote :

Cannot reproduce in Ubuntu 22.04.2 LTS.

Changed in apport:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.