Description of problem: Upto and including digikam-4.2.0-2.mga5 it was possible and quite easy to import pictures from ipad connecting the ipad to a usb port. This stopped working with digikam-4.4.0-1.mga5 and is quite irritating, especially as the ipad is quite common these days and it means final M5 would be without such function. The way it used to work was menu: Import -> Cameras --> Apple iPad (PTP mode) and it worked fine. With last 2 versions simply nothing happens: no pictures appear no matter what is tried. Please reassign to libaries digikam depends on if they are the cause of this. Reproducible: Steps to Reproduce:
Whiteboard: (none) => 5beta3
CC: (none) => eeeemailAssignee: bugsquad => anaselli
Summary: Latest 2 versions cannot access pictures on iPad => Latest 2 versions of digikam cannot access pictures on iPad
well it's quite common... but not enough i don't have any :p BTW if you're using ptp mode there is nothing as far as i know specially developed in digikam, but it should be related to gphoto2.
In #c1 anaselli@linux.it wrote: > BTW if you're using ptp mode That is not me using it but digikam's choice, and the only way the system works! > there is nothing as far as i know specially > developed in digikam, but it should be related to gphoto2. It escapes me what you mean by this, can you clarify? Thanks.
On comment#1 i meant that as far as i know digikam uses gphoto2 (libgphoto2) for that, so you could check if gphoto2 works properly then we have two possibilities - works and we can move this problem upstream - does not work it's a gphoto2 problem
A good! Thanks. Will revert soonest.
Ok digikam developers seem to confirm there is a bug in how digikam links libusb. I'm waiting for a fix and see if it is really your problem. Please stay tuned to provide feed-backs :)
Just gotten around to trying gphoto2 when comment 5 came in: gphoto2 works okay, but command line is hardly as easy as digikam when that works.
that confirms it's a digikam issue :)
Status: NEW => ASSIGNED
could you please check with the last cauldron release?
Yes it works now (although it it now tediously slow, which it wasn't when it worked earlier...). Thanks for the fix.
Should have closed with previous comment
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED