Bug 175401

Summary:	Digikam doesn't always detect mass storage camera and fails to correctly autocreate datebsed folders
Product:	[Applications] digikam	Reporter:	Angelo Naselli <anaselli>
Component:	Import-UMS	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	marcel.wiesweg, thomas
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	0.10.0
Sentry Crash Report:

Description Angelo Naselli 2008-11-17 15:56:38 UTC

Version:           0.10.0 beta5 (using KDE 4.1.3)
OS:                Linux
Installed from:    Mandriva RPMs

Bug reported by Thomas Rasmussen
https://qa.mandriva.com/show_bug.cgi?id=45830

Description of problem:
1. Connecting Nikon D40 to USB port. lsusb shows:
[root@localhost thomas]# lsusb
Bus 002 Device 011: ID 04b0:0413 Nikon Corp. D40 (mass storage mode)

2. In Digikam I choose Import > Cameras (Add) > USB PTP Class Camera or Add
camera and then autodetect. Either way Digikam reports that it could not
connect to camera. I have also tried to manually add Nikon DSC D40 (PTP mode)
with same result. At the same time I am able to browse the files on the camera
using Dolphin.

3. The strange thing is that 2 minutes later Digikam is able to autodetect the
camera as a Mass Storage Camera. But when I try to import photos fram the
camera I get an error popup saying "Failed to create directory".

4. When I unplug the camera and insert the flash card in the laptops cardreader
and then try to import from the flashcard, I get the same error popup saying
"Failed to create directory".

5. In an console I get this output:
digikam(22088) Digikam::CollectionScanner::scanAlbum: Folder does not exist or
is not readable:  "/home/thomas/Billeder/2008/2008-03-24/2008-09-18". But I
pointed Digikam to import and autocreate directories in
/home/thomas/Billeder/2008/ and not /home/thomas/Billeder/2008/2008-03-24/

6. Next time I try I get an error saying that the directory already exists.

7. When I try to import fram the flashcard and unselect the auto creation of
folders based on Date (ISO) the import works ok.

Comment 1 Marcel Wiesweg 2008-11-17 18:11:06 UTC

1+2) lsusb shows that your Nikon is connected in Mass Storage Mode. I would expect the PTP mode to fail then.

3) At which point in time is the camera listed under the menu entry "Cameras (Auto-detected)" and when under "USB mass storage devices"?

3-7) Can these points be summarized as "auto-creating directories is broken"?

Comment 2 Thomas Rasmussen 2008-11-18 09:19:25 UTC

I don't use the camera when listed under "USB mass storage devices" - this is when I try to read from the flashcard in the laptops cardreader. But when I connect the camera with USB it is also listed under "USB mass storage devices" as "D40". When I try to connect to the camera this way, Digikam locks up and I get the following output in a console: 
"Object::connect: No such signal Solid::StorageAccess::setupDone(Solid::ErrorType,QVariant)
Object::connect:  (receiver name: 'Digikam')"


The problem I reported has 2 parts:

1) Digikam fails to autocreate ISO datebased folders. Creates them in wrong places and says that it fails to create them.

2) Digikam has problems detecting my camera (Nikon D40) although lsusb all the time shows it as connected. Choosing Import>Cameras>Add Camera>Auto-Detect results in an error popup that says: "Failed to auto-detect camera. Please check if your camera is turned on and retry or try setting it". Retrying doesn't help.

When i manually add "Mass Storage Camera" and then try to import photos the connection fails with an error popup saying "Failed to connect to the camera. Please make sure it is connected properly and turned on. Would you like to try again?"

Comment 3 Marcel Wiesweg 2008-11-29 17:42:19 UTC

The failure to mount a USB mass storage camera has been fixed lately. There are other still open bugs concerning PTP cameras, but here the camera is running in mass storage mode.

The second part of the bug is the failure to create date-based subfolders, which has already been reported in bug 175322

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