Package: gajim
Version: 0.11.3-1
Severity: grave
Justification: renders package unusable
Hi!
I just noticed that gajim fails to start. After moving .gajim out of the
way it fails with the following error:
Requires docutils 0.4 for set_classes to be available
creating logs database
Traceback (most recent call last):
File "gajim.py", line 2264, in ?
check_paths.check_and_possibly_create_paths()
File "/usr/share/gajim/src/common/check_paths.py", line 112, in
check_and_possibly_create_paths
create_log_db()
File "/usr/share/gajim/src/common/check_paths.py", line 34, in create_log_db
con = sqlite.connect(logger.LOG_DB_PATH)
ValueError: database parameter must be string or APSW Connection object
I don't now when gajim stopped to work (it was definitely fine some days ago),
so I
guess some library is broken. When I have some time I'll try to find the
culprit.
/Armin
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gajim depends on:
ii dnsutils 1:9.4.2-1 Clients provided with BIND
ii python 2.4.4-6 An interactive high-level object-o
ii python-glade2 2.12.0-2 GTK+ bindings: Glade support
ii python-gtk2 2.12.0-2 Python bindings for the GTK+ widge
ii python-pysqlite2 2.4.0-1 python interface to SQLite 3
ii python-support 0.7.5 automated rebuilding support for p
Versions of packages gajim recommends:
ii dbus 1.1.2-1 simple interprocess messaging syst
ii notification-daemon 0.3.7-1+b1 a daemon that displays passive pop
ii python-dbus 0.82.3-1 simple interprocess messaging syst
pn python-gnupginterface <none> (no description available)
-- debconf-show failed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
