Your message dated Sat, 09 Nov 2013 11:01:08 +1100
with message-id <3968891.92LEqO9PWs@acer>
and subject line Fwd: Bug#718439: Upstream bug report
has caused the Debian Bug report #718439,
regarding digikam (core): Schema update to V 7 failed!
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
718439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:3.1.0-4
Severity: normal
Dear Maintainer,
when starting digikam, I get
rd@blackbox:~/Downloads$ digikam
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading
configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 16: Having
multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having
multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103:
Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138:
Having multiple values in <test> isn't supported and may not work as expected
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
digikam(5648)/digikam (core): Schema update to V 7 failed!
and the albums and tags are gone.
Digikam recommends to report the issue at bugs.kde.org, but I thought
it might be good to report to the distribution first.
Thanks,
Rainer
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable'), (250,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages digikam depends on:
ii digikam-data 4:3.1.0-4
ii digikam-private-libs 4:3.1.0-4
ii kde-runtime 4:4.10.5-1
ii libc6 2.17-7
ii libgcc1 1:4.7.2-5
ii libgphoto2-2 2.4.14-2
ii libgphoto2-port0 2.4.14-2
ii libkdcraw22 4:4.10.5-1
ii libkdecore5 4:4.10.5-1
ii libkdeui5 4:4.10.5-1
ii libkexiv2-11 4:4.10.5-1
ii libkhtml5 4:4.10.5-1
ii libkio5 4:4.10.5-1
ii libkipi10 4:4.10.5-1
ii libknotifyconfig4 4:4.10.5-1
ii libkparts4 4:4.10.5-1
ii libphonon4 4:4.6.0.0-3
ii libqt4-dbus 4:4.8.5+dfsg-2
ii libqt4-sql 4:4.8.5+dfsg-2
ii libqt4-sql-sqlite 4:4.8.5+dfsg-2
ii libqt4-xml 4:4.8.5+dfsg-2
ii libqtcore4 4:4.8.5+dfsg-2
ii libqtgui4 4:4.8.5+dfsg-2
ii libsolid4 4:4.10.5-1
ii libstdc++6 4.7.2-5
ii libthreadweaver4 4:4.10.5-1
ii perl 5.14.2-21
ii phonon 4:4.6.0.0-3
Versions of packages digikam recommends:
ii chromium [www-browser] 28.0.1500.71-1~deb7u1
ii ffmpegthumbs 4:4.10.5-1
ii iceweasel [www-browser] 22.0-1
ii kipi-plugins 4:3.1.0-4
ii konqueror [www-browser] 4:4.10.5-1
ii lynx-cur [www-browser] 2.8.8dev.12-2
ii mplayerthumbs 4:4.10.5-1
ii rekonq [www-browser] 2.3.2-1
ii w3m [www-browser] 0.5.3-8
Versions of packages digikam suggests:
pn digikam-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
---------- Forwarded Message ----------
Subject: Bug#718439: Upstream bug report
Date: Tue, 20 Aug 2013, 21:29:36
From: Rainer Dorsch <m...@bokomoko.de>
To: 718...@bugs.debian.org
I opened an upstream bugreport:
https://bugs.kde.org/show_bug.cgi?id=323062
At least a workaround is described there (go back digikam4.db file from
backup). The problem is not fully understood though. I have no problem though
if you want to close the debian bugreport.
Thanks
Rainer
--
Rainer Dorsch
http://bokomoko.de/
-----------------------------------------
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
