#NETWORKING DIGIKAM UPDATE#
#NETWORKING DIGIKAM PATCH#

QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.Дigikam(2637)/KEXIV2: Cannot load metadata from file (Error # 11 : /home/*****/vol2/My Pictures/Norsbo/3 HГѓSTTГѓVLING.jpg: The file contains data of an unknown image typeДigikam(2637)/KEXIV2: Cannot load metadata using Exiv2 (Error # 11 : /home/*****/vol2/My Pictures/Norsbo/3 HГѓSTTГѓVLING.jpg: The file contains data of an unknown image type Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Version numbering gets somewhat muddled in the packaging and build process.Д¬ompare what you have installed to this list, which for me is currently working well. This seems the best way to navigate the 'version' discussions, where the issues almost always reside. My Digikam is version 4.3.0-19.2 from the KDE Core Extras Repo, has been stable for a couple days now.ДЄlso, open Digikam and look in Help - Component Information. If you prefer stability, keep an eye on the mailing list for initial issues to subside before upgrading your version. IMHO, the openSUSE packagers for Digikam do an excellent job keeping up with the rapidly evolving Digikam application for those of us who want to stay bleeding edge with this application.

#NETWORKING DIGIKAM UPDATE#

There you will see how difficult it is for the DK developers to manage the update complexity across the various Linus distros, as well as Win and OSX. Almost always, the fixes require a local compile (by you) or a wait for the correction to propagate thru the packaging process. I suggest you subscribe to the Digikam mailing list via where these issues get discussed and identified, if not fixed. I'll also observe that Digikam upgrades frequently modify the database schemas as new features are added, and many folks have issues going 'backwards' once a schema has been modified by the upgrade (e.g. Starting Digiikam from the CLI is always a good way to get extra information and messages. I do not, so you may need to dig into that aspect. Since you mention that your managed assets (images, videos) are on a network share, then I presume you run Digikam with mysql. That 'seemed' to affect some folks who manage videos as well as images, did not affect me.

#NETWORKING DIGIKAM PATCH#

When 4.3.0 was first released, there were numerous issues due to a libKexiv2 patch that need to be installed. I suspect that your Digikam 4.3.0 is installed from Core Extras. I have the KDE Core and Core Extras repos enabled.

Networking digikam