Hi, I'm using debian unstable and I've had a similar issue for quite some time (about 3 months IIRC) but on my side I never managed to get digikam past the splash screen saying "Loading database...".
Today I tried to start it many times since I read your bug report and I found a CPU usage using 100% of *both* cores while I was starting digikam. Thus, I discovered there was another process using CPU : FAM ! I killed the hanged up digikam and stopped FAM via /etc/init.d/fam stop and digikam works like a charm since then. I don't know if it's the source of your bug, but try to disable it and it may work... Would be a fam bug then ? Regards -- Loïc Gomez
signature.asc
Description: This is a digitally signed message part.
