Bug 180751
Summary: | Import photos from usb camera fails - messages in description | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Darwin H. Webb <thethirddoorontheleft> |
Component: | gphoto2 | Assignee: | Radek Vokál <rvokal> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | jbarnes, ronny-rhbugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.1.99-5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-27 07:21:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Darwin H. Webb
2006-02-10 03:16:12 UTC
Which version of gphoto2 are you running. Also can you check your udev and libusb version? I believe this if fixed in the most recent rawhide version. From above - FC5 HTTP install and fully updated as of Feb 9th am pst gThumb 2.7.2 After updates of Feb 10th 8:30 am pst gphoto2-2.1.99-5.1 udev-084-1 libusb-0.1.11-2.1 kernel-2.6.15-1.1928_FC5 Problem still exists. Darwin This is still not working as of FC5T3 install from cd's. Feb 20-21. gphoto2-2.1.99-5.2 udev-084-1.1 libusb-0.1.11-2.2 kernel-2.6.15-1.1955_FC5 hal-0.5.7-0.cvs20060213.1 Noral Desktop install - SELinux enabled - DHCP - Pent III 800eb x86 32 bit , tyan s1854 m/b via Apollo 133 chip set. Last 2 messages from messages: Feb 21 11:08:05 Host8 kernel: usb 1-1.2: new full speed USB device using uhci_hcd and address 4 Feb 21 11:08:05 Host8 kernel: usb 1-1.2: configuration #1 chosen from 1 choice [root@Host8 log]# Message on pop up window: An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Operation not permitted). Make sure no other program or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device. Darwin I think this is a permissions problem as I see something similar from my KDE desktop. Which file controls what permissions are assigned to the device in /proc/bus/usb when the device is plugged in? I've changed the permission handling in gphoto2-2.1.99-5 so I believe this is fixed now. [root@testmess ~]# rpm -qa gphoto2 gphoto2-2.1.99-5.2 Well, it is still the same package as before and it is still doing it as of the Feb 27th updates so how is it going to get fixed without a new pakage or some usb system adjustments? Darwin The latest package sets the permissions on /dev/bus/usb/XXX. That's what I think is the fix for this bug. this is a problem with selinux, so /usr/libexec/gphoto-set-procperm doesn't work audit.log type=AVC msg=audit(1141149795.660:155): avc: denied { search } for pid=4892 comm="cat" name="console" dev=dm-7 ino=717436 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:pam_var_console_t:s0 tclass=dir type=AVC msg=audit(1141149795.660:155): avc: denied { read } for pid=4892 comm="cat" name="console.lock" dev=dm-7 ino=718562 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:pam_var_console_t:s0 tclass=file type=SYSCALL msg=audit(1141149795.660:155): arch=40000003 syscall=5 success=yes exit=3 a0=bfe6f8fa a1=8000 a2=0 a3=8000 items=1 pid=4892 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 comm="cat" exe="/bin/cat" type=CWD msg=audit(1141149795.660:155): cwd="/usr/libexec" type=PATH msg=audit(1141149795.660:155): item=0 name="/var/run/console/console.lock" flags=101 inode=718562 dev=fd:07 mode=0100600 ouid=0 ogid=500 rdev=00:00 type=AVC msg=audit(1141149795.660:156): avc: denied { getattr } for pid=4892 comm="cat" name="console.lock" dev=dm-7 ino=718562 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:pam_var_console_t:s0 tclass=file type=SYSCALL msg=audit(1141149795.660:156): arch=40000003 syscall=197 success=yes exit=0 a0=3 a1=bfe6e83c a2=756ff4 a3=804d7e0 items=0 pid=4892 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 comm="cat" exe="/bin/cat" type=AVC_PATH msg=audit(1141149795.660:156): path="/var/run/console/console.lock" type=AVC msg=audit(1141149795.688:157): avc: denied { chown } for pid=4895 comm="chown" capability=0 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:system_r:hald_t:s0 tclass=capability type=AVC msg=audit(1141149795.688:157): avc: denied { setattr } for pid=4895 comm="chown" name="004" dev=tmpfs ino=16904 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:usb_device_t:s0 tclass=chr_file type=SYSCALL msg=audit(1141149795.688:157): arch=40000003 syscall=212 success=yes exit=0 a0=8444d90 a1=1f4 a2=ffffffff a3=0 items=1 pid=4895 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 comm="chown" exe="/bin/chown" type=CWD msg=audit(1141149795.688:157): cwd="/usr/libexec" type=PATH msg=audit(1141149795.688:157): item=0 name="/dev/bus/usb/002/004" flags=1 inode=16904 dev=00:10 mode=020644 ouid=0 ogid=0 rdev=bd:83 type=AVC msg=audit(1141149795.688:158): avc: denied { setattr } for pid=4896 comm="chown" name="004" dev=usbfs ino=16871 scontext=system_u:system_r:hald_t:s0 tcontext=system_u:object_r:usbfs_t:s0 tclass=file type=SYSCALL msg=audit(1141149795.688:158): arch=40000003 syscall=212 success=yes exit=0 a0=8d17d90 a1=1f4 a2=ffffffff a3=0 items=1 pid=4896 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 comm="chown" exe="/bin/chown" type=CWD msg=audit(1141149795.688:158): cwd="/usr/libexec" type=PATH msg=audit(1141149795.688:158): item=0 name="/proc/bus/usb/002/004" flags=1 inode=16871 dev=00:11 mode=0100644 ouid=0 ogid=0 rdev=00:00 this log was generated with selinux permissive This bug still isn't fixed. This message seems to indicate that the problem may be with HAL though: http://www.redhat.com/archives/fedora-devel-list/2006-February/msg01469.html I'm running gphoto2-2.1.99-5.2 hal-0.5.7-1 udev-084-6 dbus-0.60-7.2 on my machine if that helps. I'll look around to see if anyone's filed the HAL bug. |