Bug 361523 - Nikon Coolpix P610: "Failed to detect camera with GPhoto2 from Solid information"
Summary: Nikon Coolpix P610: "Failed to detect camera with GPhoto2 from Solid informat...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: 4.14.0
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-08 15:13 UTC by Mathieu MD
Modified: 2020-07-26 12:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu MD 2016-04-08 15:13:25 UTC
I cannot import photos from a Nikon Coolpix P610 into Digikam 4.14.0 on Debian testing (stretch).
The log shown in console is:
digikam(7482)/digikam (core): Failed to detect camera with GPhoto2 from Solid information

It seems to be the same problem as discussed in https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/865032 and #311393.

Actually, gPhoto2 2.5.9 does work with the camera (although it's not listed in `--list-cameras`), and I can use it's Fuse interface `gphotofs` to mount the camera folders. But I rather prefer to directly mount the SD card and import from it into Digikcam directly.

Reproducible: Always

Steps to Reproduce:
0. Launch Digikam from a console
1. Connect camera with USB cable
2. Click "Importation > Appareils photo > NIKON NIKON DSC COOLPIX P610"
3. Check the line displayed in the console

Actual Results:  
digikam(7482)/digikam (core): Failed to detect camera with GPhoto2 from Solid information

Expected Results:  
Nothing show in the console, and the actual importation window opened displaying photos from the camera.

At least, Digikam should warn the user about the problem (via a popup or notification message). Most users won't try to launch Digikam from Konsole to check for logs.
Comment 1 caulier.gilles 2016-04-08 19:00:28 UTC

*** This bug has been marked as a duplicate of bug 307839 ***
Comment 2 caulier.gilles 2020-07-26 12:52:06 UTC
Fixed with #307839