Hi,
tir, 20 06 2006 kl. 11:24 +0200, skrev Frederic Peters:
Hi,
Anders Lind wrote:
First of all sorry that I send you a mail directly - I'm not familiar
with the bugtracking reportbug tool and VI.
Not a problem for me; cc'ing to 366135@ for archival.
Thank you!
This bug # also had a very useful reference. So I installed the
libgphoto2-2-dev package with positive results. (read on please)
I could imagine that it might has something to do with this:
Note (TODO). print-usb-usermap is deprecated as of 2.1.99.1. Use
print-camera-list instead. Description of udev rules and HAL setup
missing here.
, from this page:
http://www.gphoto.org/doc/manual/permissions-usb.html#setting-up-linux-hotplug
This is unrelated.
In that case my question is whether it is something that should be fixed
in libgphoto2-2 or by the package maintainers of kcmshell kamera and
digikam?
I believe this should be fixed in digikam since other programs (I just
checked again with gthumb and f-spot) don't have any problems with the
upgrade.
Unfortunately I don't have enough time to investigate digikam properly
but I am there to answer any question you could have.
Afterwards I added my user to the camera group - and a reboot was
needed!!!
Then both digikam and the camera controls of KControl worked as well as
gtkam! (before the reboot they only worked as root.)
So the question is whether those .so files (in case they are causing the
problems) should be included in the standard libgphoto2-2 distribution?
(Since digikam and the camera control/setting windows of KControl
depends on them.)
I also have a Canon PowerShot A620 actually so this update to libgphoto2
was very appreciated.
My only problem now - which is a normal user/newbie problem is how I
see the files, stored in the camera, in Konqueror. Konqueror detects the
camera with a folder, but never shows the pictures inside of it. Any
ideas what to do, when I use udev and hal?
Regards,
Frederic
Best regards and thank you all!!!
Anders Lind
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
