Ubuntu
digikam package

libgphoto doesn't work with digikam

Bug #675351 reported by David McGlone
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

kodak easyshare z760 is detected by shotwell, f-spot and digikam, but import only works with shotwell and f-spot. digikam needs the file 40-libgphoto2-2.rules changed from this:
SUBSYSTEM!="usb", GOTO="libgphoto2_rules_end"
to this:
SUBSYSTEM!="usb_device*", GOTO="libgphoto2_rules_end"

But when the change is made, it renders shotwell and f-spot unusable.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libgphoto2-2 2.4.8-0ubuntu2 [modified: lib/udev/rules.d/40-libgphoto2-2.rules]
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sun Nov 14 19:02:47 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: libgphoto2

Revision history for this message
David McGlone (david-dmcentral) wrote :
Revision history for this message
Paul Tagliamonte (paultag) wrote :

Thanks for reporting this issue and helping make Ubuntu better!

This looks like an issue with digikam to me, I'm going to re-assign it.

affects: libgphoto2 (Ubuntu) → digikam (Ubuntu)
Revision history for this message
Paul Tagliamonte (paultag) wrote :

This looks to be a mis-implementation, but I'm not sure. I'm going to leave it NEW and wait for someone from the digikam package to triage this. Thanks!

Changed in digikam (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in digikam (Ubuntu):
status: New → Confirmed
Revision history for this message
Rohan Garg (rohangarg) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in digikam (Ubuntu):
importance: Medium → Undecided
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for digikam (Ubuntu) because there has been no activity for 60 days.]

Changed in digikam (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.