Bug 428634

Summary:	Camera EOS 5D Mark III does not connect with Digikam either manually or automatically under Windows10
Product:	[Applications] digikam	Reporter:	grazykite
Component:	Import-WIA	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	7.1.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description grazykite 2020-11-03 11:00:56 UTC

SUMMARY
If I connect my Canon EOS 5D Mark III via USB3.0 with my PC (Digikam is running) there is no possibility that camera is selected by Digikam automatically. There is no list available where I can select camera type if I will do it manually in preferences. If I implement camera as an USB device manually in preferences it does not work also.  
All simple things has been checked like: is camera switched on, are there pictures available on sd card and so on.

It would be very nice to get your feedback for solving this issue. Thanks in advance. Best regards.

System description
Operating System
	Windows 10 Pro 64-bit
CPU
	Intel Core i9 9900K @ 3.60GHz	
	Coffee Lake 14nm Technology
RAM
	32,0GB Dual-Channel Unknown @ 1339MHz (19-19-19-43)
Motherboard
	ASUSTeK COMPUTER INC. ROG MAXIMUS XI HERO (LGA1151)	
Graphics
	PHL BDM3275 (3840x2160@60Hz)
	4095MB NVIDIA GeForce RTX 2070 (MSI)	
Digikam does not connect camera for downloading pictures. 
Windows recognize camera and and open import process of pictures automatically.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Maik Qualmann 2020-11-03 16:24:57 UTC


*** This bug has been marked as a duplicate of bug 388137 ***

Comment 2 caulier.gilles 2022-01-20 09:28:17 UTC

Hi all,

GPhoto2 camera drivers support under Windows will be added to next 7.6.0 release. See the story on bug https://bugs.kde.org/show_bug.cgi?id=398166

Gilles Caulier