hamster-applet crashed with TypeError in load_config()

[Severin H]

Binary package hint: hamster-applet

After having added it to the GNOME panel, hamster-applet keeps crashing when I try to open the preferences dialog using its context menu. This is a reproducable bug.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/hamster-applet/hamster-applet
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx
Package: hamster-applet 2.24.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: python /usr/lib/hamster-applet/hamster-applet --oaf-activate-iid=OAFIID:Hamster_Applet_Factory --oaf-ior-fd=26
ProcEnviron:
 LANG=de_CH.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/hamster-applet/hamster-applet', '--oaf-activate-iid=OAFIID:Hamster_Applet_Factory', '--oaf-ior-fd=26']
SourcePackage: hamster-applet
Title: hamster-applet crashed with TypeError in load_config()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[swoody (swoody)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at https://wiki.ubuntu.com/DebuggingGNOMEApplets or run "/usr/lib/hamster-applet/hamster-applet -w" and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. Could you also let us know if you have "python-evolution" installed?
If anyone else has this bug, or can recreate it, please let us know.

[Dimitrios Symeonidis (azimout)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!