Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 229230 - gphoto2 can stop manage permissions now
Summary: gphoto2 can stop manage permissions now
Alias: None
Product: Fedora
Classification: Fedora
Component: gphoto2
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact:
Depends On:
Blocks: FC7Blocker
TreeView+ depends on / blocked
Reported: 2007-02-19 17:25 UTC by David Zeuthen
Modified: 2013-07-02 23:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-02-21 11:19:26 UTC
Type: ---

Attachments (Terms of Use)

Description David Zeuthen 2007-02-19 17:25:28 UTC
We've moved ACL handling into HAL proper with hal-0.5.9-0.git20070218. So this
file and the associated binaries should be removed



Comment 1 Jindrich Novy 2007-02-19 19:17:46 UTC
Happily removed.

Comment 2 David Zeuthen 2007-02-19 19:29:11 UTC
Thanks - but you removed a bit too much; this file


is still needed since it's used to classify USB interfaces as being cameras.
Without this HAL won't know the USB device is a camera. Thanks.

Comment 3 David Zeuthen 2007-02-19 19:30:22 UTC
I meant


of course.

Comment 4 Jindrich Novy 2007-02-21 11:19:26 UTC
10-camera-libgphoto2.fdi is now added back.

Comment 5 Andreas Heik 2007-11-26 12:34:58 UTC
Today, there are 2 problems with gphoto2 and acl-management in Fedora 8.

First, the hal-rule for "main usb devices" into
/usr/share/hal/fdi/policy/10osvendor/20-acl-management.fdi begin at line 61 will
not match.
My Device (Canon PowerShot S45) returns info.subsystem = 'usb_device'  (string).
Is the rule <match key="info.subsystem" contains="usb"> better at this line??

The second problem is the fdi-information file into gphoto2-package.
Checking for usb-bus works only with string="usb_device" or contains="usb". 
If the device has no key "usb.interface_class", all camara-rules will be
skipped. I think there is no need for skipping usb storage devices or we need a
better determination rule.
At least, the keys "usb.vendor_id", "usb.product_id" are changed to
"usb_device.vendor_id", "usb_device.product_id"

best regards, andreas

Note You need to log in before you can comment on or make changes to this bug.