Package: libusb-1.0-0 Version: 2:1.0.17-1+b1 Followup-For: Bug #727221 I don't know if other applications are affected, but I can reproduce it and it indeed makes usage of gphoto2 quite annoying.
Neither setting USB_DEBUG nor LIBUSB_DEBUG makes any difference for me. LIBUSB_DEBUG=0 gphoto2 -L spits huge amount of lines starting with "libusbx: debug " to stderr. The original submitter has attached some sample of produced output in the bug #727217 filled against gphoto2 (which uses libgphoto2-port0 which in turn depends on libusb-1.0-0). -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (700, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libusb-1.0-0 depends on: ii libc6 2.17-97 ii libudev1 204-5 ii multiarch-support 2.17-97 libusb-1.0-0 recommends no packages. libusb-1.0-0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
