hamster-applet crashed with OperationalError in execute()

Bug #360208 reported by David Prieto
8
Affects Status Importance Assigned to Milestone
hamster-applet (Ubuntu)
Invalid
High
Unassigned

Bug Description

Binary package hint: hamster-applet

I'm using jaunty. Hamster can't be added to the panel.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/hamster-applet/hamster-applet
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: hamster-applet 2.26.0-0ubuntu1
ProcCmdline: python /usr/lib/hamster-applet/hamster-applet --oaf-activate-iid=OAFIID:Hamster_Applet_Factory --oaf-ior-fd=19
ProcEnviron:
 LANG=es_ES.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/hamster-applet/hamster-applet', '--oaf-activate-iid=OAFIID:Hamster_Applet_Factory', '--oaf-ior-fd=19']
SourcePackage: hamster-applet
Title: hamster-applet crashed with OperationalError in execute()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
David Prieto (frandavid100-gmail) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Changed in hamster-applet (Ubuntu):
importance: Undecided → High
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

david, i cannot reproduce this on jaunty. can you try purging the hamster-applet package and re-install it?

Changed in hamster-applet (Ubuntu):
status: New → Incomplete
Revision history for this message
David Prieto (frandavid100-gmail) wrote :

Hi Dimitrios,

Purging the package does not solve the issue, but if I try to launch hamster in a guest account it works. Should I try deleting the config files? Where exactly are they stored?

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

You can find them under ~/.gnome2/hamster-applet
Let me know how it went
Good luck :-)

Revision history for this message
David Prieto (frandavid100-gmail) wrote :

Solved :)

I'm attaching the config folder, which was causing the crash.

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

the issue was a corrupted hamster.db in the user's settings (~/.gnome2/hamster-applet)
marking as invalid (although it would be useful, in the future, to fail gracefully instead of crashing)

Changed in hamster-applet (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Felix Kuehling (fxkuehl) wrote :

I got the same problem after upgrading from Karmic to Lucid.

I think crashing like this due to "corrupted" configuration files is not acceptable. If the solution is to delete the hamster.db, doesn't that mean I loose all the history stored in the file? That too, is not acceptable to anyone who was actively using hamster in Karmic.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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