Bug 222716 - Digikam does not start. Showing: Reading databasae...
Summary: Digikam does not start. Showing: Reading databasae...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-14 15:21 UTC by Marcus Hardt
Modified: 2018-08-10 09:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Hardt 2010-01-14 15:21:04 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When I start digikam, it hangs, showing "Reading database..." in the graphical window.

I had this before (about a year ago). Those days it was due to the interaction with sqlite. Of course I kept my debian/testing up to date. Versions involved:

Digikam:      1.0.0-1 0
libsqlite3-0: 3.6.21-2

I don't see any specific error messages on the konsole on which I start digikam.

Anything I can do?
Comment 1 Marcel Wiesweg 2010-01-14 16:56:04 UTC
Try to produce a backtrace: Run digikam under gdb. When it is hung, press Ctrl+C on the console to interrupt, then "thr appl all bt" and gives us the backtraces.

Does it use CPU when hanging?
Comment 2 Marcus Hardt 2010-01-15 12:42:17 UTC
No CPU consumption when hanging

The backtrace is at the URL (to keep the bug readable (this ok?))
http://marcus.hardt-it.de/stuff/digikam-backtrace.txt
Comment 3 caulier.gilles 2010-01-15 12:46:17 UTC
Thread 1 (Thread 0x7ffff7fa4750 (LWP 13465)):
#0  0x00007ffff0b9259b in write () from /lib/libc.so.6
---Type <return> to continue, or q <return> to quit---
#1  0x00007fffec8b2177 in Client::writeToServer(char*, int) () from /usr/lib/libfam.so.0
#2  0x00007fffec8b4e5f in ?? () from /usr/lib/libfam.so.0
#3  0x00007ffff3c3bdbd in ?? () from /usr/lib/libkio.so.5
#4  0x00007ffff3c3ce53 in ?? () from /usr/lib/libkio.so.5
#5  0x00007ffff3c3ca5e in ?? () from /usr/lib/libkio.so.5
#6  0x00007ffff3c3ca5e in ?? () from /usr/lib/libkio.so.5
#7  0x00007ffff3c3d14b in KDirWatch::addDir(QString const&, QFlags<KDirWatch::WatchMode>) () from /usr/lib/libkio.so.5
#8  0x0000000000627d56 in ?? ()
#9  0x00000000006371d7 in ?? ()
#10 0x000000000067db3e in ?? ()
#11 0x0000000000778e35 in ?? ()
#12 0x00007ffff0af1abd in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>,
    init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffffffe308) at libc-start.c:222
#13 0x0000000000471fd9 in _start ()
Current language:  auto
The current source language is "auto; currently asm".
Current language:  auto
The current source language is "auto; currently c".
(gdb)

==> Kdelibs :: KDirWatch :: libfam problem...

Reassigned.

Gilles Caulier
Comment 4 caulier.gilles 2018-08-10 09:39:09 UTC
Since we port digiKam to pure Qt5 based only directory listener, this problem is not reproducible.

Gilles Caulier