turns on libusb debugging by default
Bug #1206104 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libgphoto2 (Debian) |
Fix Released
|
Unknown
|
|||
libgphoto2 (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt |
Bug Description
The change from libusb to libusbx in libgphoto2 (https:/
$ gphoto2 --auto-detect
libusbx: debug [libusb_
libusbx: debug [discovered_
libusbx: debug [libusb_
The same can be seen when starting shotwell, so it's not a problem in the gphoto2 binary. It does not happen with "lsusb", so it seems it's also not a problem with libusbx itself.
Related branches
affects: | libusbx (Ubuntu) → libgphoto2 (Ubuntu) |
Changed in libgphoto2 (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
Changed in libgphoto2 (Debian): | |
status: | Unknown → New |
Changed in libgphoto2 (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
libgphoto2 libgphoto2_ port/libusb1/ libusb1. c
look for the libusb_set_debug line, comment it out.
Oh, and update to 2.5.2 already, 2.4.14 is 1.5 years old.