Bug 317247 - No picture is found after update to ver 3.0.0
Summary: No picture is found after update to ver 3.0.0
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 3.0.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-23 20:26 UTC by Victoria
Modified: 2017-07-25 17:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Victoria 2013-03-23 20:26:02 UTC 
I've just updated (through yumex) to digikam 3.0.0.

Even if there are pictures in the folders and a huge database is still recognized, no pictures are shown or found. The albums view has the number (0) after each and every album, even if there are pictures in it.

I've tried to add a folder (to force digikam to read the directories again) and I get this error message: Could not start process Unable to create io-slave: klauncher said: Error loading 'kio_file'..

I'm running Fedora Gnome 3.4.2 on a 64bits laptop. It worked fine (great) with older versions of digikam.
Comment 1 caulier.gilles 2013-03-23 21:35:48 UTC 
It sound like a dependency broken with KIOSlave. It's probably a packaging problem.

Gilles Caulier
Comment 2 caulier.gilles 2013-12-04 16:54:41 UTC 
Victoria,

Do you see my previous comment ?

Problem still here with digiKam 3.5.0 ?

Gilles Caulier
Comment 3 caulier.gilles 2015-06-30 08:06:27 UTC 
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 4 caulier.gilles 2015-08-20 06:52:11 UTC 
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier
Comment 5 swatilodha27 2016-07-02 17:37:07 UTC 
digiKam no more uses KIO slaves. Please try the latest 5.0.0 version.

If you think the report is still valid, feel free to re-open.