Package: libusb-1.0-0 Version: 2:1.0.17-1+b1 Severity: normal Any application linked with libusb outputs tons of debugging output to the terminal. Using CLI applications like gphoto2 is hell.
I was thinking gphoto2 was at fault here, but then I realized all applications linked with libusb were doing the same. The gphoto2 manual page states something about the USB_DEBUG environment variable for controlling libusb debug, which is unset. Setting it to any value though doesn't have any effect either. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.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-93 ii libudev1 204-5 ii multiarch-support 2.17-93 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
