Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 153535
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo KDE team <kde@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: mikael lammentausta <mikael.lammentausta@savonia-amk.fi>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 153535 depends on: Show dependency tree
Bug 153535 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-10-31 03:51 0000 
Until this is fixed, digiKam should require v.2.1.6 of libgphoto2. See
http://bugs.kde.org/show_bug.cgi?id=125696. The bug is reported by a Debian
user, but I get the same error on Gentoo with the latest libgphoto2.

BTW, digiKam-0.9.0_beta3 has been released a week ago, and it's not in portage.

------- Comment #1 From Ioannis Aslanidis 2006-10-31 04:41:51 0000 ------- 
Sorry, but I've to a life :)

About the dependency issue, please notice that digikam is incompatible with
versions of libgphoto2 lower than 2.1.16, iirc.

------- Comment #2 From Ioannis Aslanidis 2006-10-31 10:15:06 0000 ------- 
Fixed in CVS in version 0.9.0_beta3. Thanks for reporting the issue.

------- Comment #3 From Robert Davis 2006-11-02 21:28:43 0000 ------- 
Am I missing something? The problem seems to be the lack of .la files.  My
Gentoo 2006.1 build of 2.2.0 has them.  The Debian bug doesn't say if 2.1.6 had
.la or not.  For Debian 2.2.0 and digikam you need the -dev package to add the
.la files.  And this hasn't been narrowed down to a libgphoto or KDE problem. 
It has been working here.

------- Comment #4 From Ioannis Aslanidis 2006-11-03 00:01:49 0000 ------- 
I'll have a new look at it.

------- Comment #5 From Harm Geerts 2006-11-04 16:19:43 0000 ------- 
It works fine with libgphoto2-2.2.1-r1 and digikam-0.9.0_beta3 using kde-3.5.5
here.

I also can't reproduce the behavior described in the upstream bug.
The dynamic loading is working as it should.

$ strace digikam --detect-camera 2>&1 | grep libgphoto2
open("/usr/lib64/libgphoto2/2.2.1/soundvision.la", O_RDONLY) = 18
open("/usr/lib64/libgphoto2/2.2.1/soundvision.so", O_RDONLY) = 18

The misbehavior might be the result of the missing .la files which contain the
dlname.

The digikam README recommends >=libgphoto-2.2
(And it's causing the infamous up/downgrade loop in portage)
So please fix this issue :)

------- Comment #6 From Ioannis Aslanidis 2006-11-04 17:03:28 0000 ------- 
Reverted in CVS.

------- Comment #7 From mikael lammentausta 2006-11-06 22:18:01 0000 ------- 
Ok, I'll re-emerge libgphoto2-2.2 to see if this issue still persists. The
contact to camera as a normal user stopped after the upgrade, so I thought this
would be a bug in digiKam.

Any idea where to start? I'm in the plugdev group, and the connection has
worked before.

------- Comment #8 From Thomas Bettler 2007-01-18 23:31:40 0000 ------- 
Already thrown an eye at bug #153471 ?
You just might want to sync and upgrade to solve this issue...

Alternative steps to gather more information on the isse:
1. check if it works as root
 -> if yes continue
2. check you got write permissions on your camera
$ ls -l /dev/bus/usb/*/*
 -> have a look at the respective device...
You don't? -> set them manually and check if it works now...
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug