|
Digikam & Entangle permission or usb problems
Hi & thanks in advance. I'm running Slackware v14.1 with kernel v3.12 and trying to get may Canon EOS 6D tethered to my laptop via Entangle v0.6.0 & trying to use Digikam v4.6 to connect directly as well. Both programs recognize my camera & model #. On Digikam when I try to import photos thru my camera which was auto-detected I get the following;
Failed to connect to the camera. Please make sure it is connected properly and turned on. Digikam is dependent on the gphoto2 library so I verified the following; bash-4.2# gphoto2 -l There is 1 folder in folder '/'. - store_00020001 There are 2 folders in folder '/store_00020001'. - DCIM - MISC There is 1 folder in folder '/store_00020001/DCIM'. - 100CANON There are 0 folders in folder '/store_00020001/DCIM/100CANON'. There are 0 folders in folder '/store_00020001/MISC'. bash-4.2# bash-4.2# gphoto2 --auto-detect Model Port ---------------------------------------------------------- Canon EOS 6D usb:001,005 bash-4.2# bash-4.2# mount /mnt/USB1 mount: special device /dev/sdb1 does not exist bash-4.2# Using Entangle it shows my camera make & model but I get the following when select my camera & try to connect for tethered shooting: Unable to connect to camera: Unable to initialize camera Check that the camera is not - opened by another photo application - mounted as a filesystem on the desktop - in sleep mode to save battery power Ive spent a few days googling this issue and everything I'm finding is dated and does not seem to apply to my software & kernel version. Examples: http://www.hyperborea.org/journal/20...m-permissions/ http://www.gphoto.org/doc/manual/permissions-usb.html |
I have been a long time digikam user, and have two cameras.
When I first started using digikam, I found I had to set the camera to PTP mode. This is done on the camera itself. I do not own a Canon, so I don't know where in the configuration you might have to look. I would suggest you look in the documentation that came with the camera for that setting. I have an Olympus E 620 and a Nikon Coolpix 5000. Both cameras work with digikam digikam-4.7.0-x86_64-1_SBo on the stock kernel 3.10.17 SMP. I'm running 14.1 64 bit system. Some things you can check for. After you plug in your camera, is it mounted? Just run 'mount' to display mounted partitions. My cameras become /dev/sdd1 ( I have 3 disks in my system ) and mount on /run/media/cliff/disk. I had never heard of Entangle until I read your post. I was intrigued, so I installed it with SBopkg. It installed without problems. Now for the fun part. I can connect to both cameras. I could not do much with the Olympus, and since it is not listed as a supported camera, I switched to the Nikon, which is listed as supported. After I connect to the Nikon, I get a pop up message "Camera load control failed. Unable to fetch control config". I went to the site for Entangle. There is no manual for the application, only some FAQ's that don't explain much about the program. I have not found anything so far on control config, how to create it, options etc. So, in summary, I have had good results with digikam, once you set the camera to PTP mode. Entangle is another story. I'll keep digging and post if I find something useful. Another interesting thing, when I bring up Entangle, the look of the program doesn't even come close to the screen shots that are shown on their web site. ( http://entangle-photo.org/ ) The buttons on the left side are missing; all that shows is a black box in their place. I suspect something is missing. For the record, I installed all the dependencies listed on sbo for entangle. I downloaded the source. I looked at the list of dependencies in the README. I have all the dependencies with higher levels; except one called gudev. I can not find any package on slack called gudev. So that is a mystery to me right now. |
I have 2 cameras also, an EOS 20D & EOS 6D. I looked thru my 6D manual and online forums & discovered that the newer canons do not have the option to turn ptp off or on. My EOS 20D does so I turned it on & tried down loading from it thru Digikam and still no luck (same error as 6D). Here is another issue that is odd, when selecting "Edit" in Digikam with an image from my 6D it opens up with a heavy magenta cast & with low contrast. Editing is hard because I'm starting with a degraded image. However when loading an image from my EOS 20D it looks normal in the "Edit" menu. I actually download my image files with a card reader but thought I would try the camera just to see if Digikam had the same issues as Entangle and it does. This makes me wonder if I need to write a udev rule for my cameras. What are your thoughts on that?
I ran mount as you suggested and got the following; bash-4.2$ mount /dev/sda1 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) /dev/sda2 on /home type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) /dev/mmcblk0p1 on /mnt/Card type vfat (rw,noexec,nosuid,nodev) bash-4.2$ My understanding is that Digikam is dependent on libgphoto2 so I ran the following line command & my 6D camera files downloaded to my home directory; bash-4.2# gphoto2 –get-all-files <CR> … (Saves files in /home/john) Downloading '_MG_0323.JPG' from folder '/store_00020001/DCIM/100CANON'... Saving file as _MG_0323.JPG Downloading '_MG_0324.JPG' from folder '/store_00020001/DCIM/100CANON'... Saving file as _MG_0324.JPG Downloading '_MG_0325.JPG' from folder '/store_00020001/DCIM/100CANON'... Saving file as _MG_0325.JPG Downloading '_MG_0326.JPG' from folder '/store_00020001/DCIM/100CANON'... Saving file as _MG_0326.JPG Downloading '_MG_0327.JPG' from folder '/store_00020001/DCIM/100CANON'... Saving file as _MG_0327.JPG Downloading '_MG_0328.JPG' from folder '/store_00020001/DCIM/100CANON'... Saving file as _MG_0328.JPG This has me lost because it seems like Digikam should work if gphoto2 is working. My experience with finding information on Entangle is like yours, hardly any info out there. Thanks for responding Camorri. |
The digikam-users list has had some complaints about recognising Canons (6D, 7D) of late - since 4.5 I think.
I haven't kept the mail (Nikon user), but a search against the list should find some-thing. Not sure if a solution has been posted. Make sure the camera isn't mounted by something else - in my case Shotwell used to get in first. Umount fixed it - but I haven't had that happen for a while. |
Quote:
I have never seen a problem with editing pics from my system. Just wondering what type of image you were editing. .jpg raw ? Don't know if you noticed or not, digikam 4.7 is now in sbo. You could update and see if it helps. |
I just tried the umount & got the following as user;
bash-4.2$ umount /mnt/USB1 umount: /mnt/USB1 is not mounted (according to mtab) bash-4.2$ and as root; bash-4.2# umount /mnt/USB1 umount: /mnt/USB1: not mounted bash-4.2 I then started Digikam & got the same error. I have never written a udev rule so I am going to have to research it. If you write one please let me know how it worked for you. I shoot in raw all the time. FYI: (I should have added this earlier) When I purchased my EOS 6D I was doing most of my image editing on my desktop (Mac w/Snowleopard which cannot be upgraded any further) and using ACR with CS5 which could not open the raw files. After much searching I was left with 2 choices which were upgrade to a new MAC or use Adobe dng converter. I used the dng converter for a couple of months & do not like the extra step in my work flow. I'm now back to my trusty laptop (IBM Thinkpad Z60m w/32 bit archetecture Slackware 14.1) which I'm happy with. Canon is changing the new camera cs2 files just enough to force customers to upgrade some software applications so I was not totally surprised that I had an issue opening the raw file in Digikam. I have since found out that when using the dng converter in Digikam & using Raw Therapee my cr2 files all look the same with a heavy magenta cast & low contrast. But all is not lost because I downloaded UFraw yesterday & it works great. Why I don't know. I tried Dark Table but it won't run on my laptop. I need 64 bit architecture. I will look into the latest release of Digikam. Thanks |
Resolved
A good friend of mine called me this morning after seeing this post and has worked out a solution after putting some time into this. Start "Entangle & Digikam" out of Xterm as "Super User". I can now shoot tethered. There are still a few functions in Entangle that don't work but writing a udev rule for your camera may give you full access. My EOS 6D now comes up automatically in Digikam and I can download my pictures. The pics still have a "Magenta cast/Low contrast" when opening as raw files in the editor which is an issue with the new Canon cr2 files which they control and is beyond my skill set to remedy.
|
Thank-you for the update. I did some reading on writing udev rules.
I will give Entangle another try as root, and report back. If it works as su, that would lead me to believe there is a permission problem. |
An update.
Spent some time with both of my cameras. I have finally got the Nikon Coolpix 5000 to work, to some degree with Entangle. I had to change the USB setting in the camera to PTP mode. It was set to Mass Storage mode. After some trial and error with Entangle, I got it to take a picture and display it. That was it, just one picture. I got it saved on the cameras internal memory card. I could not get the shot saved on my systems hard drive. I will investigate that a little more. I did not need to run Entangle with root privileges. I tried 'kdesu entangle', and it launches Entangle, but I don't need to. I do not need the camera mounted to the file system to get a picture taken by tethering. I spent some time in my with my Olympus as well. It has more modes for the USB connection. You can set it for Mass Storage, MTP, Control and two printer modes. I tried Control, thinking that was the magic ticket I needed. Nope. Entangle doesn't recognize the camera in this mode. It does "see" the camera in Mass Storage mode, but will not connect to it or do anything useful with it. Well, the Olympus is not on the supported cameras list, so a little disappointment, but not surprised it doesn't work with Entangle. The doc for the camera does talk about a program Olympus sells for tethering. So, it can be done with windows ( choke gag ). I will do some more testing with the Nikon, and post my results. |
Just had some time to play with the Entangle program some more. When I first got it to work it would only take one picture like you described. I played around with the "Camera Settings" sidebar settings and got it to display a new image each time I shot after changing a couple of things. I checked the box "Capture" and gave a new destination folder for the images. I can now trigger the camera from my laptop. Try playing around with the settings and see if it helps.
|
I now have everything working from the Entangle sidebar "Camera Settings" menu. I can change film speed, picture style, camera color space & everything else that is in the menu from my laptop. You just have to play around with the settings to see what works for your camera. I'm very happy with the program now. It even downloads my camera's images to the new folder that I designated.
John |
Digikam - camera not found error
Using ubuntu 16.04 fully updated, plugging my Sony Xperia S (LT26i) into the usb port and starting digikam produces the camera not found error. By the way,selecting "configure digikam" finds the camera but nothing more. To resolve this, I opened the file manager, showing the camera as a mounted device, which I unmounted. I then entered lsusb in a terminal to find the device name as "Bus 001 Device 006: ID 0fce:0169 Sony Ericsson Mobile Communications AB Xperia S". Aware of issues with permissions, I read the device details of /dev/bus/usb/001/006 as "crw-rw----+ 1 root root 189, 5 Sep 5 10:01 006". I changed root to my user name and restarted digikam, when all worked.
I gather this can be solved properly by changing the udev rules in some way. |
| All times are GMT -5. The time now is 11:03 AM. |