Your message dated Tue, 03 Dec 2013 15:52:16 +0100
with message-id <874n6qvvfj....@olivierberger.com>
and subject line Re: Bug#718439: digikam: digikam (core): Schema update to V 7 
failed!
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 ---
Hi.

Maximiliano Curia <m...@gnuservers.com.ar> writes:

> Control: tags -1 + moreinfo
>
> In article <20131201084326.24638.65255.reportbug@jonsnow> you wrote:
>> I've experienced the same issue. As for OR, there's nothing suspicious
>> apparently: it used to work fine a few days ago, and now the error is here.
>
>> I'm not sure upstream report is conclusive, as seems it relates to upgrades
>> over a few increments, which is not the case here AFAIU.
>
> The upstream bug comment 22 explains a way to fix your db, does it work for
> you? https://bugs.kde.org/show_bug.cgi?id=323062#c22
>
> Did the error started happening after upgrading to digikam 3.4.0 (currently in
> testing)?
>
> Do you have a backup of your previous database that could be used to test the
> schema upgrade?
>

Thanks for caring.

I'm sorry I haven't had time to report earlier.

Actually, it happens that the db file was read-only, and that explains
the problem that were exhibited (for the records, I manage my photos
with git-annex and thus the db file was read-only too).

I'll try and investigate a bit more though, on ways of improvement in
case of read-only DB file handling, but it seems the reopening of this
particular bug was a bit too fast, then.

Thanks a lot and sorry about the bothering.

Best regards,
-- 
Olivier BERGER 
(OpenPGP: 4096R/7C5BB6A5 : http://weusepgp.info)
http://www.olivierberger.com/weblog/

--- 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

Reply via email to