Version: 0.10.0 (rev.: 933374) (using 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)), Debian packages) Compiler: cc OS: Linux (x86_64) release 2.6.30-1-amd64 after upgrading from kde 4.2.4 to 4.2.96 (debian 5 unstable) amd64 i am unable to see any thumbnails in the album view (actually, no where in the application). i did not upgrade digikam. i backed up the DB and let digikam create a new DB but it did not solve the issue. while it was starting (with no db) i got the following console messages: laptop:~# digikam Warning: Directory Image, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1. QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to Phonon::FactoryPrivate::phononBackendChanged(): org.freedesktop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to Phonon::DeviceListing::audioDevicesChanged(): org.freedesktop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to KSycoca::notifyDatabaseChanged(QStringList): org.freedesktop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) Starting to load Plugins. . . .
This is fully relevant of binary compatibility problem with package. It's not digiKam. It's dependencies problem not resolved properly by packagers... Gilles Caulier
i remember i had that same issue in the past. maybe i even reported it? no sure. do you suggest i wait or report in debian's BTS ? btw, which package you suppose is responsible for this ? thanks :-)
Yes, report in Debian. look about libmarblewidget dependency. Gilles Caulier
me joker :-( i use sources from git and not packages from deb. (in this case) so i just recompiled and it works just fine :-)