Hello, Tony! On Thu, 2008-03-06 at 11:38 -0800, tony mancill wrote: > Package: gpodder > Version: 0.11.0-1 > Severity: important > > I'm unable to start gpodder on a system running a current version of > Debian unstable. The error produced is: > > Traceback (most recent call last): > File "/usr/bin/gpodder", line 155, in ? > sys.exit( main()) > File "/usr/bin/gpodder", line 113, in main > from gpodder import console > File "/var/lib/python-support/python2.4/gpodder/console.py", line 25, in ? > from libpodcasts import load_channels > File "/var/lib/python-support/python2.4/gpodder/libpodcasts.py", line 80, > in ? > class ChannelSettings(object): > File "/var/lib/python-support/python2.4/gpodder/libpodcasts.py", line 81, > in ChannelSettings > storage = shelve.open( libgpodder.gPodderLib().channel_settings_file) > File "/usr/lib/python2.4/shelve.py", line 234, in open > return DbfilenameShelf(filename, flag, protocol, writeback, binary) > File "/usr/lib/python2.4/shelve.py", line 215, in __init__ > Shelf.__init__(self, anydbm.open(filename, flag), protocol, writeback, > binary) > File "/usr/lib/python2.4/anydbm.py", line 83, in open > return mod.open(file, flag, mode) > File "/usr/lib/python2.4/dbhash.py", line 16, in open > return bsddb.hashopen(file, flag, mode) > File "/usr/lib/python2.4/bsddb/__init__.py", line 298, in hashopen > d.open(file, db.DB_HASH, flags, mode) > bsddb.db.DBInvalidArgError: (22, 'Invalid argument -- > /home/tony/.config/gpodder/channelsettings.db: unsupported hash version: 9')
It seems like some updated Python package broke something. Try the following workaround: rm -f ~/.config/gpodder/*.db The .db files will be re-created on next gPodder startup. This bug has been fixed in SVN already (using a pickle-based storage method instead of the unstable shelve module that breaks every now and then for reasons unknown to me). So, as a temporary fix for the current version, remove the db files as described above. This will definitely be fixed in the next release when we change the storage method. Thanks, Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
