Comment 5 for bug 83922

--- "Benjamin.M" <email address hidden> wrote:

> I'm using latest Feisty Fawn, all updates installed.
> And I have a i386 System, non the less I am
> experiencing nearly the same problem!
> If started from console, I also get the Timeout
> message. But I have a log which says:
>
> Log messages of
> /home/ben/.gdesklets/logs/gdesklets%3A0.0.log
> /usr/lib/gdesklets/main/__init__.py:118:
> GtkDeprecationWarning: gtk.threads_init is
> deprecated, use gtk.gdk.threads_init inst
> ead
> gtk.threads_init()
>
>
==========================================================[02/22/07-20:24:42]===
> === Unhandled error! Something bad and unexpected
> happened. ===
>
> [EXC]db type could not be determined
> in /usr/lib/gdesklets/gdesklets-daemon: line 127
> <module>
> in /usr/lib/gdesklets/gdesklets-daemon: line 114
> _gdesklets_main
> in /usr/lib/gdesklets/utils/ErrorFormatter.py: line
> 118 _new_imp
> in /usr/lib/gdesklets/main/Starter.py: line 2
> <module>
> in /usr/lib/gdesklets/utils/ErrorFormatter.py: line
> 118 _new_imp
> in /usr/lib/gdesklets/config/DaemonConfigger.py:
> line 1 <module>
> in /usr/lib/gdesklets/utils/ErrorFormatter.py: line
> 118 _new_imp
> in /usr/lib/gdesklets/config/StateSaver.py: line 128
> <module>
> in /usr/lib/gdesklets/config/StateSaver.py: line 30
> __init__
> in /usr/lib/gdesklets/config/Backend.py: line 68
> Backend
> in shelve.py: line 225 open
> in shelve.py: line 209 __init__
> in anydbm.py: line 80 open
> [EXC]/usr/lib/python2.5/anydbm.py
>
> [---] 75 mod = _defaultmod
> [---] 76 else:
> [---] 77 raise error, "need 'c' or 'n'
> flag to open new db"
> [---] 78 elif result == "":
> [---] 79 # db type cannot be determined
> [ERR]> 80 raise error, "db type could not
> be determined"
> [---] 81 else:
> [---] 82 mod = __import__(result)
> [---] 83 return mod.open(file, flag, mode)
>
> Version is 0.35.3-4ubuntu2
>
> I tried dpkg --purge to uninstall it and reinstall
> it, so its not a
> config problem I guess.
>
> --
> gdesklets does not start feisty herd3 amd64
> https://launchpad.net/bugs/83922
>
I dont think its exactly the same bug , the i386
version was working with 32bit systems at the time I
filed that bug also I got no meaningful log output.
python id being updated frequently and that may be
causing it , I had a similar problem with freeguide
for a couple of days that was cause by an update to
java.

____________________________________________________________________________________
Have a burning question?
Go to www.Answers.yahoo.com and get answers from real people who know.