digikam does not detect ptp camera in anka [solved]

[Lisa]

Hi all,
I assume this is a problem with   KDE 4.8.2  such as when I updated to 4.8.2 some packages were removed, like kdegraphics 4.6.5.  There is no kdegraphics 4.8.2 as some changes  have been implemented during release of 4.7.  
Anyway, when I try:
digikam --detect-camera
it crashes digikam which uses libgphoto2 to find cameras.  Mine is a Picture Transfer Protocol type camera (ptp).  I was wondering if anyone else using ANKA has issues with digikam 2.6.0-beta2?  I've tried downgrading libghoto2 from 2.4.11 to 2.4.10  but that did not help.  So now I am about to try and compile digikam 2.9 source and also am looking at other image management software such as Photivo (nope, needs GCC 4.6), xnviewmp, fotoxx, and Bluemarine.  I'm also going to play with/compile the latest libgphoto2 to see if that will help.  It's difficult to say where this problem lies, whether it is from digikam, the libgphoto2, udev?  Camera detection problem has already been notified to Anka bug reporting.  Just wondering if anyone had any suggestions.
Lisa Marie

[Lisa]

Should have switched over to the pardususer depots as lo and behold, there is photivo, gphoto and maybe some other goodies that will solve my problem.  Thanks, pardususer folks!

[Lisa]

Those programs in above message didn't help me as I still needed digikam to capturethe pictures and I saw no where that Photivo would do this. 
I guess I wanted this badly and at the same time learned a bit more about compiling, with the result of a squeaky mouse from the sweat, and a stiff neck    I've never used cmake or qmake before.

I solved this by compiling digikam 2.9 tar, and in order to do that, I had to install many -dev files , as well as marble 4.8.2 tar, and that needed some things such as libkdeedu 4.8.2 and also from qt-mobility-opensource-src 1.0.2 tar, and that needed a few more things (devels) like  qt-labs-messaging-framework.  I also compiled qjson 0.7.1 (I think marble needed that?) and I removed kipi-plugins and let digikam install it from extras.  And, while I was at it, I compiled kgpg, kcalc, kwallet, ark, and superkaramba all 4.8.2.  I see I also compiled liblqr and again, I forget which software needed that.  I'm sure my builds are like meatloaf but at least my camera is now detected.  Now if I could only be as determined to learn how to make a pisi for all of these and let you test them.    Funny, whiile doing searches for all of my build failes, I found alexey's name in a search engine who was working on qt-mobility.  I'm learning that there are lots of qt stuff that kde relies on. 

[atolboo]

Build files for the digikam-1.9.0 are at
http://svn.pardus.org.tr/pardus/tags/2011-EOL/multimedia/graphics/digikam/
Maybe they are of any help making digikam-2.9.0

[Lisa]

Funny you should share that atolboo, because I was wondering about that two days ago, and I recall someone asked about, to help a newbie learn what commands you give to install a certain software.  In the end, I finally used
cmake /home/me/hand/digikam-2.9.0  -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ..

I should have asked this first, as I could have saved a bit of time, but I learned some new things while I was searching for answers.
Thank you!
Regards, Lisa Marie

[Lisa]

I learned that this is a two-fold problem.  Firstly, that device notifier does not find my camera when I turn it on, and secondly, that digikam 2.6* would crash when  I would use the GUI to detect my camera or:
digikam --detect-camera
I read somewhere that the first problem has been fixed in KDE 4.8.3 and doing further testing, I logged into my other distro that uses 4.8.3 version, and while 'top' was on, I turned camera on and plasma-desktop pops up at top of 'top'.  Doing the same in Pardus 4,8.2 doesn't, so I figure this is a plasma-desktop bug, part of kde-workspace.  
Now I have to go through all of my notes and see all that I needed for dependencies.  Pisi history and bash history will come in handy for that.  

Edited to add, bug 296778 is KDE bug report, and changing from 'removable devices' to 'all devices' solved it for me as well.  All is well for both problems.