rworkman at slackbuilds.org
Wed May 9 13:59:42 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Michael Wagner wrote:
> it seems as if there is a bug in libgphoto2. I use version 2.3.1 with
> udev-0.97 from slackware 11.
> The generated udev rules are never applied because udev does not report BUS
> properties to 90-libgphoto2.rules. It skips the file at the following line:
> BUS!="usb*", GOTO="libgphoto2_rules_end" (never true)
> Changing this line to:
> SUBSYSTEM!="usb*", GOTO="libgphoto2_rules_end"
> solves the issue for me. It also works with the udev rules generated
> via "print-camera-list udev-rules-0.98" (althoug udev version is 0.97)
This doesn't make sense. The BUS key was renamed to SUBSYSTEM(S) in
udev-098, and while the older BUS key was left in for backwards
compatibility, I see no indication that support for the newer
SUBSYSTEM(S) key had already been added before that. However, the
udev documentation often leaves a lot to be desired, so...
Can you use udevinfo(8) to give a full attribute walk on one of the
affected devices and post that here? I'm curious as to what all keys
are being exported to sysfs by the devices...
As of right now (at least based on the information we have), this does
appear to be a bug in libgphoto (as opposed to our script) - we are
simply generating the udev rules according to their instructions.
This should probably be reported to them, but if you want to hold off
for a bit until we can look at the udevinfo output, then that's fine.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Slackbuilds-users