Version: 0.10.0 (using KDE 4.2.90) OS: Linux Installed from: Ubuntu Packages Copying files leads to an error message: "Der Prozess für das Protokoll digikamalbums wurde unerwartet beendet" ("The process for the protocoll digicamalbungs was closed unexpected" or something like that). Although this message appears copying works after canceling the message away. This happens on both copying via shortcuts/context menu and drag'n drop. Moving files works.
Take a look in you ~/.xsession-errors if you find any messages from digiKam kio-slave. Gilles Caulier
Something like that? timeChanged void SunLocator::update() kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so QWidget: Cannot create a QWidget when no GUI is being used kioslave: ####### CRASH ###### protocol = kio_digikamalbums pid = 9877 signal = 6 QSocketNotifier: Invalid socket 11 and type 'Read', disabling... timeChanged void SunLocator::update() timeChanged void SunLocator::update() kdeinit4: preparing to launch /usr/lib/kde4/kio_digikamalbums.so kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so QWidget: Cannot create a QWidget when no GUI is being used kioslave: ####### CRASH ###### protocol = kio_digikamalbums pid = 9891 signal = 6 QSocketNotifier: Invalid socket 11 and type 'Read', disabling... kdeinit4: preparing to launch /usr/lib/kde4/kio_digikamalbums.so
yes... So why it crash. Sound like an external depency broken. Which Exiv2 you use ? Go to Help/Components Info for details. Gilles Caulier
libexiv2 0.18 Maybe it has to do something with my update to KDE 4.2.90? After the update no thumbnails were shown so I installed a build from a PPA: https://edge.launchpad.net/~alessandro-ghersi/+archive/ppa
1/ i recommend to use Exiv2 0.18.1. 2/ yes, it sound like a binary compatibility broken after to have upgraded KDE. It's not a digiKam problem... Recompiled by hand digiKam & co must solve the problem Gilles Caulier
Compiled by hand OR new binaries compiled against new KDE and exiv libs provided by distribution.
Because of bug 196329 I've compiled the 1.0b1 tarball and the problem still exists.
Dominic, This file still valid using digiKam 2.x serie ? Gilles Caulier
Gilles, thanks for asking. It's working now :-)
This problem is relevant of digiKam KIO Slaves and all of these have been dropped in favor of a multi-threaded interface to query the database.