glipper crashed with ValueError in load(): invalid literal for int() with base 10: '\xe2^[...]\x9b'
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| glipper (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Apparently the history contains uncommon data, which glipper fails to process properly.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: glipper 2.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Thu Nov 17 14:30:05 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/glipper
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/glipper
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/zsh
PATH=(custom, user)
PythonArgs: ['/usr/
SourcePackage: glipper
Title: glipper crashed with ValueError in load(): invalid literal for int() with base 10: '\xe2^\
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
| Daniel Hahler (blueyed) wrote | #1 |
| summary: |
glipper crashed with ValueError in load(): invalid literal for int() - with base 10: - '\xe2^\'\xf4\xb8\xb3\xb4\xf6\x99\x83\'\xce\xdd\xfa\xc4\xe9S\x7f=\xf0C\xa0\xf2\x9fs\xdce\x1d\xfd\xaa\x8b\xb7\x8b\xbd\xfaK}\xf7\x1a\x9f\xb0$:q\xb5\xe0\xd5\x8d*o\xc5`1\x99\xa0\xe2T>\x17UCE\x107\x12\x82]\xf7\xba\xb5\xeb$~\r$S\x0c\x02)w|\x98@N\xc5\xfdSO\xe1\xf1\xd7\xd9\\\x1d\x8f\xbf\xd1\x0c\xa6\xafw.\x02@\xce\x8e\xea\xb5(3\xf7\xbee\x91\xcf\xc8c\xbbpf\xe7\x1c\xf5\x97E\x07*\'w\x14q\xedv\xa2?"\xc8\x04\x90\x14yc=\x1a\x90\xa5\xed\xaf\xc4\x88\xdc#U\xef\xd3o\xaf\x9a\xc2L\x8d\\\xbd\xa7u\xa6\xfd\xbf\xde\xd6\x13\x94(3\xf7\xbe\xc4\x89\xdcj@\xa4\x8fGR\x83\x8dD5ZjGf+(e\xd4\xee\x98\x9b' + with base 10: '\xe2^[...]\x9b' |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
| 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 #833629, 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.