** Changed in: glipper (Ubuntu)
Status: Confirmed => Triaged
** Changed in: glipper (Ubuntu)
Importance: Undecided => High
** Description changed:
Glipper crashes if the history file (~/.local/share/glipper/history) is
damaged (invalid format of the length metainfo, which should be a
number).
- The fix appears to be to just forget about the invalid history file.
+ The workaround appears to be to just forget about the invalid history file:
+ $ rm ~/.local/share/glipper/history
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: glipper 2.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic-pae 2.6.38.8
Uname: Linux 2.6.38-11-generic-pae i686
Architecture: i386
Date: Thu Aug 25 11:26:13 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/glipper
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/glipper
ProcEnviron:
- LANG=en_US.UTF-8
- LANGUAGE=en_US:en
- SHELL=/usr/bin/zsh
- PATH=(custom, user)
+ LANG=en_US.UTF-8
+ LANGUAGE=en_US:en
+ SHELL=/usr/bin/zsh
+ PATH=(custom, user)
PythonArgs: ['/usr/bin/glipper']
SourcePackage: glipper
Title: glipper crashed with ValueError in load(): invalid literal for int()
with base 10:
"\xcb#W\x84\xb0\x0e\xa8\x93s$\x8a\xe0\xd7\xa9[\x08\x95\xa8\xf93,(\xa7\x91\xf3\x9a,\x05\xec\x9a6\xb4\xd9LP\xc4\xde\xb4\x8d,\xafZ\x9cJ\x1cz\x0ea\xb7\xc6\x97[u\xbcrL\xe2+\xeb\xef\x9cn\xd41\xca\xcan<y\xffv\x96\xcb\xd1\xdd\x82\x02\xfa\xea\x8dF#\xc2V6\xf6\xcc\xcc:\x15\x92\x15K\xb9'\xe0v\x86^\x1f\x8a\xabaR\xe4\xe2\xd9-\xe1\x84x\xfd\xf5\xa0\x12*T\xd7\xd2BPH\x92z\xef\xe3o\xd3]Re\r"
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
** Description changed:
Glipper crashes if the history file (~/.local/share/glipper/history) is
damaged (invalid format of the length metainfo, which should be a
number).
- The workaround appears to be to just forget about the invalid history file:
- $ rm ~/.local/share/glipper/history
+ The workaround appears to be to just forget about the invalid history file
(or move it away):
+ $ rm ~/.local/share/glipper/history
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: glipper 2.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic-pae 2.6.38.8
Uname: Linux 2.6.38-11-generic-pae i686
Architecture: i386
Date: Thu Aug 25 11:26:13 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/glipper
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/glipper
ProcEnviron:
LANG=en_US.UTF-8
LANGUAGE=en_US:en
SHELL=/usr/bin/zsh
PATH=(custom, user)
PythonArgs: ['/usr/bin/glipper']
SourcePackage: glipper
Title: glipper crashed with ValueError in load(): invalid literal for int()
with base 10:
"\xcb#W\x84\xb0\x0e\xa8\x93s$\x8a\xe0\xd7\xa9[\x08\x95\xa8\xf93,(\xa7\x91\xf3\x9a,\x05\xec\x9a6\xb4\xd9LP\xc4\xde\xb4\x8d,\xafZ\x9cJ\x1cz\x0ea\xb7\xc6\x97[u\xbcrL\xe2+\xeb\xef\x9cn\xd41\xca\xcan<y\xffv\x96\xcb\xd1\xdd\x82\x02\xfa\xea\x8dF#\xc2V6\xf6\xcc\xcc:\x15\x92\x15K\xb9'\xe0v\x86^\x1f\x8a\xabaR\xe4\xe2\xd9-\xe1\x84x\xfd\xf5\xa0\x12*T\xd7\xd2BPH\x92z\xef\xe3o\xd3]Re\r"
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833629
Title:
glipper crashed with ValueError in load(): invalid literal for int()
with base 10: "\xcb#W\x84\xb0\x0e [...] \r"
To manage notifications about this bug go to:
https://bugs.launchpad.net/glipper/+bug/833629/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
