Bug 370175 - Cannot Import Images (Failed to detect camera with GPhoto2 from Solid information)
Summary: Cannot Import Images (Failed to detect camera with GPhoto2 from Solid informa...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: 5.2.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-06 04:35 UTC by John Salatas
Modified: 2017-08-15 21:59 UTC (History)
3 users (show)

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


Attachments
digikam (11.91 KB, text/plain)
2016-10-06 04:35 UTC, John Salatas
Details
gphoto2 (9.25 KB, text/plain)
2016-10-06 04:36 UTC, John Salatas
Details
digikam 5.3.0 (git checkout at 20161013). (7.98 KB, text/plain)
2016-10-13 21:03 UTC, John Salatas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Salatas 2016-10-06 04:35:17 UTC
Same thing happens with Canon EOS Rebel SL1 digital camera and Samsung Galaxy Note 3 phone.

I connect the camera to the PC through usb. 

Using the gphoto2 command line interface as described at http://www.gphoto.org/doc/manual/using-gphoto2.html I can see the camera, the files it contains and I can download these files in my PC (see attached file named "gphoto2"). 

Running digikam and selecting Import -> Cameras -> (my camera name) nothing happens (not even an error message). In the console I'm getting the output shown in the attachment named "digikam". 


Reproducible: Always
Comment 1 John Salatas 2016-10-06 04:35:42 UTC
Created attachment 101439 [details]
digikam
Comment 2 John Salatas 2016-10-06 04:36:05 UTC
Created attachment 101440 [details]
gphoto2
Comment 3 Jeremy Lainé 2016-10-09 18:56:38 UTC
I have the same behaviour with an EOS 5D Mark II. What's odd is that I am sure it worked in previous releases (though not the last 4.x releases).
Comment 4 Maik Qualmann 2016-10-13 19:38:20 UTC
I have reviewed the corresponding code. But no mistake found. It works here with the most diverse devices without problems. I will add some additional debug output for digiKam-5.3.0. Please upload then the console messages of digiKam-5.3.0 here.

Maik
Comment 5 Maik Qualmann 2016-10-13 20:21:40 UTC
Git commit 2a9b32a66327f7ede92f4ca969c954b3adcd7a55 by Maik Qualmann.
Committed on 13/10/2016 at 20:20.
Pushed by mqualmann into branch 'master'.

add test debug messages for Solid and gPhoto2

M  +2    -0    app/main/digikamapp.cpp
M  +8    -0    utilities/importui/backend/gpcamera.cpp

http://commits.kde.org/digikam/2a9b32a66327f7ede92f4ca969c954b3adcd7a55
Comment 6 John Salatas 2016-10-13 20:38:21 UTC
I just tried it in KDE Neon developer stable and it works (for my Samsung Galaxy Note 3 phone). 
Is this helpful? If not I could try to build digikam with the latest code in git in KDE Neon user edition
Comment 7 John Salatas 2016-10-13 21:03:07 UTC
Yeap! I can confirm that compiling digikam 5.3.0 from git (as of 20161013) in kde neon user, seems to fix the problem (see attached log).
Comment 8 John Salatas 2016-10-13 21:03:47 UTC
Created attachment 101559 [details]
digikam 5.3.0 (git checkout at 20161013).
Comment 9 Maik Qualmann 2016-10-14 06:02:53 UTC
Gilles,
I think we can close this bug. It will be related to the changes to detect the gPhoto2 packages.

Maik
Comment 10 caulier.gilles 2016-10-14 06:44:44 UTC
Ah. Something is wrong in the new simplified cmake script to detect Gphoto2 library ?

Gilles
Comment 11 John Salatas 2016-10-14 06:48:51 UTC
(In reply to caulier.gilles from comment #10)
> Ah. Something is wrong in the new simplified cmake script to detect Gphoto2
> library ?
> 
> Gilles

No! :)

Everything is ok now with the latest code in git. Version 5.2.0 was broken :)