Possible database corruption?

[Robert Markula]

Hey guys,
I'm a happy digikam user for years now, without ever experiencing a
single hiccup. Today it's Digikam 0.10.0 on Ubuntu 9.04 with approx.
30.000 images. However, when I started digikam this morning, all images
seemed to be... gone!?

The album was empty, even the keyword view contained no images. The
keywords were there alright, but... no images, even they were sitting in
their usual folders just fine.

I reimported a backup of the digikam4.db, still no pictures. I even
reimported the digikamrc, but that didn't help either.

I get no error messages whatsoever on starting or using digikam, the
images are just silently gone.

I was initially afraid that the database could be corrupt, but since the
database from the backup - that is known to work - doesn't work either,
I'm a bit lost. The album and database paths still point to the correct
directory, otherwise digikam would complain about missing images, right?

Well, what can I do now?

Cheers,
Robert
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

On Sunday 04 October 2009 13:25:36 Robert Markula wrote:
> Hey guys,
> I'm a happy digikam user for years now, without ever experiencing a
> single hiccup. Today it's Digikam 0.10.0 on Ubuntu 9.04 with approx.
> 30.000 images. However, when I started digikam this morning, all images
> seemed to be... gone!?
>
> The album was empty, even the keyword view contained no images. The
> keywords were there alright, but... no images, even they were sitting in
> their usual folders just fine.

Did you update to new KDE or use some specific PPA packages?
This problem occurs when digikam is not compatible with KIO libraries from
KDE. This often happens with newer KDE and using digikam compiled with older
version of KDE.

Regards,
Luka
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Robert Markula]

Hi Luka,

Luka Renko wrote:
> Did you update to new KDE or use some specific PPA packages?
> This problem occurs when digikam is not compatible with KIO libraries from
> KDE. This often happens with newer KDE and using digikam compiled with older
> version of KDE.

No, I'm using vanilla digikam with its original KDE dependencies from
the official Ubuntu repositories. Beside the ususal package updates
performed by update manager I didn't install any new/updated software
lately that could break digikam. No PPA or KDE-updates outside update
manager.

Cheers,
Robert
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

On Sunday 04 October 2009 19:01:30 Robert Markula wrote:

> Hi Luka,
>
> Luka Renko wrote:
> > Did you update to new KDE or use some specific PPA packages?
> > This problem occurs when digikam is not compatible with KIO libraries
> > from KDE. This often happens with newer KDE and using digikam compiled
> > with older version of KDE.
>
> No, I'm using vanilla digikam with its original KDE dependencies from
> the official Ubuntu repositories. Beside the ususal package updates
> performed by update manager I didn't install any new/updated software
> lately that could break digikam. No PPA or KDE-updates outside update
> manager.

Strange, the symptoms are the same as with package mismatch.

Can you start digikam from command line (for example Konsole) and report what
does it print out?

Can you provide output of the following command:
apt-cache policy digikam libmarble4 kdebase-runtime

Regards,
Luka
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

And make sure the slaves are running. Type

pgrep -l digi

while digiKam is running.
It should print something like

kio_digikamalbum
kio_digikamtags

etc.

Andi

On Sunday 04 October 2009 20:22:55 Luka Renko wrote:

> On Sunday 04 October 2009 19:01:30 Robert Markula wrote:
> > Hi Luka,
> >
> > Luka Renko wrote:
> > > Did you update to new KDE or use some specific PPA packages?
> > > This problem occurs when digikam is not compatible with KIO libraries
> > > from KDE. This often happens with newer KDE and using digikam compiled
> > > with older version of KDE.
> >
> > No, I'm using vanilla digikam with its original KDE dependencies from
> > the official Ubuntu repositories. Beside the ususal package updates
> > performed by update manager I didn't install any new/updated software
> > lately that could break digikam. No PPA or KDE-updates outside update
> > manager.
>
> Strange, the symptoms are the same as with package mismatch.
>
> Can you start digikam from command line (for example Konsole) and report
>  what does it print out?
>
> Can you provide output of the following command:
> apt-cache policy digikam libmarble4 kdebase-runtime
>
> Regards,
> Luka
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Robert Markula]

Luka, you wouldn't believe it. I struggled for hours without luck, until
I got the idea that a restart might help. I had already thought about
that, but that felt too simple and I wasn't convinced at all, but
desperation was finally stronger. And... it worked. I feel so stupid.
Smack me, you've got all rights to do so.

Maybe some slave died, as Andi suggested. I don't know. It works. Phew.

Thanks Luka and Andi for your time and for your help!

Luka Renko wrote:
> Strange, the symptoms are the same as with package mismatch.
>
> Can you start digikam from command line (for example Konsole) and report what
> does it print out?
>
> Can you provide output of the following command:
> apt-cache policy digikam libmarble4 kdebase-runtime

Sure, this is the output even if not needed anymore:

<snip>
ro@thinkpad:~$ apt-cache policy digikam libmarble4 kdebase-runtime
digikam:
  Installiert: 2:0.10.0-1ubuntu3
  Kandidat: 2:0.10.0-1ubuntu3
  Versions-Tabelle:
 *** 2:0.10.0-1ubuntu3 0
        500 http://localhost jaunty/main Packages
        100 /var/lib/dpkg/status
libmarble4:
  Installiert: 4:4.2.2-0ubuntu1
  Kandidat: 4:4.2.2-0ubuntu1
  Versions-Tabelle:
 *** 4:4.2.2-0ubuntu1 0
        500 http://localhost jaunty/main Packages
        100 /var/lib/dpkg/status
kdebase-runtime:
  Installiert: 4:4.2.2-0ubuntu1
  Kandidat: 4:4.2.2-0ubuntu1
  Versions-Tabelle:
 *** 4:4.2.2-0ubuntu1 0
        500 http://localhost jaunty/main Packages
        100 /var/lib/dpkg/status
</snip>

Thanks again,
Robert
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

This would have been my next tip (when no slaves are found):
KDE sometimes doesn't like starting slaves, so you need to run

kbuildsyscoca4 --noincremental

and then log out, even better, restart KDM.

Andi

On Sunday 04 October 2009 20:46:17 Robert Markula wrote:

> Luka, you wouldn't believe it. I struggled for hours without luck, until
> I got the idea that a restart might help. I had already thought about
> that, but that felt too simple and I wasn't convinced at all, but
> desperation was finally stronger. And... it worked. I feel so stupid.
> Smack me, you've got all rights to do so.
>
> Maybe some slave died, as Andi suggested. I don't know. It works. Phew.
>
> Thanks Luka and Andi for your time and for your help!
>
> Luka Renko wrote:
> > Strange, the symptoms are the same as with package mismatch.
> >
> > Can you start digikam from command line (for example Konsole) and report
> > what does it print out?
> >
> > Can you provide output of the following command:
> > apt-cache policy digikam libmarble4 kdebase-runtime
>
> Sure, this is the output even if not needed anymore:
>
> <snip>
> ro@thinkpad:~$ apt-cache policy digikam libmarble4 kdebase-runtime
> digikam:
>   Installiert: 2:0.10.0-1ubuntu3
>   Kandidat: 2:0.10.0-1ubuntu3
>   Versions-Tabelle:
>  *** 2:0.10.0-1ubuntu3 0
>         500 http://localhost jaunty/main Packages
>         100 /var/lib/dpkg/status
> libmarble4:
>   Installiert: 4:4.2.2-0ubuntu1
>   Kandidat: 4:4.2.2-0ubuntu1
>   Versions-Tabelle:
>  *** 4:4.2.2-0ubuntu1 0
>         500 http://localhost jaunty/main Packages
>         100 /var/lib/dpkg/status
> kdebase-runtime:
>   Installiert: 4:4.2.2-0ubuntu1
>   Kandidat: 4:4.2.2-0ubuntu1
>   Versions-Tabelle:
>  *** 4:4.2.2-0ubuntu1 0
>         500 http://localhost jaunty/main Packages
>         100 /var/lib/dpkg/status
> </snip>
>
> Thanks again,
> Robert
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Robert Markula]

Hi Andy,

Andi Clemens wrote:
> This would have been my next tip (when no slaves are found):
> KDE sometimes doesn't like starting slaves, so you need to run
>
> kbuildsyscoca4 --noincremental
>
> and then log out, even better, restart KDM.

Good to know, thanks for the tip!

Cheers,
Robert
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jens Nie-3]

OK. Time for me to join in. I have basically the same problem.

I have recently experimented with a brand new Leica M9 a friend of mine -
lucky him - owns since a couple of days now, and was quite confused that i was
not able to view the images (dng) within digikam. Must be something wrong with
the raw part of digikam or the libkdcraw or related i guess. However that
motivated me to compile the latest beta4 sources of digikam, as i did not find
any binaries for opensuse 11.1 available. Before compiling i removed any
digikam and kipi-plugin package in order to have the system as clean as
possible.Compilation worked like a charm. However digikam showed no thumbnails
for the images after the next start of the application. Moreover digikam does
not seem to find any plugins now, which i compiled and installed as well (I
really like the opengl viewer for going through the images as it is really
fast. Nearly as fast as the good ole kuickshow application we had in KDE3,
which was damn fast actually. Such a pitty it's no longer available for KDE4.)

But back to this.

So i googled a bit on this and found, that digikam once had this problem in
the past already. I followed the both tipps removing the marble packages and
rebuilding the thumbnails, which took some hours with my 30.000+ images. All
in all with no success. No thumbnails.

Now i checked with pgrep if the slaves are available: They are not. So i
followed the kbuildsycoca4 thing, but digikam still does not show any
thumbnails.

Any more tipps? I have so many new photos to explore, and i really can't wait
to see them ;-)

For the protocol: I use the KDE 4.3.1 packages provided by the opensuse build
service for opensuse 11.1

On Sunday 04 October 2009 20:32:51 Andi Clemens wrote:

> And make sure the slaves are running. Type
>
> pgrep -l digi
>
> while digiKam is running.
> It should print something like
>
> kio_digikamalbum
> kio_digikamtags
>
> etc.
>
> Andi
>

[...]
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users