Bug#444808: usbutils: lsusb does not report any devices
Package: usbutils Version: 0.72-9 Severity: normal lsusb does not report any devices when a non-root user run it. No errors are reported either. I ran lsusb with strace and it tries to open files under /dev/bus/usb/nnn/nnn which are not world readable. The lsusb man page says it has to open files under /proc/bus/usb/nnn/nnn which is world readable. I guess reading files under /dev/bus/usb is a new way to retreive USB information, but then the DIAGNSTICS section in the man page needs to be fixed so that lsusb must open files under /dev/bus/usb. It would also be nice for lsusb to report that it fails to open files. Takeshi -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.9 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages usbutils depends on: ii libc6 2.6.1-5 GNU C Library: Shared libraries ii libusb-0.1-42:0.1.12-7 userspace USB programming library ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime usbutils recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444808: usbutils: lsusb does not report any devices
clone 444808 -1 reassign -1 udev retitle -1 udev: USB devices should be readable by normal users severity -1 important severity 444808 minor retitle 444808 usbutils: manpage is outdated wrt /dev/bus/usb thanks Takeshi Hakamata a écrit : Package: usbutils Version: 0.72-9 Severity: normal lsusb does not report any devices when a non-root user run it. No errors are reported either. I ran lsusb with strace and it tries to open files It looks like that once again udev has changed the permission on the USB device nodes to something like 0660. This is plainly wrong. Note that read permissions on the device does not allow any transfer, as ioctls need write access. I am therefore cloning this bug to udev. under /dev/bus/usb/nnn/nnn which are not world readable. The lsusb man page says it has to open files under /proc/bus/usb/nnn/nnn which is world readable. I guess reading files under /dev/bus/usb is a new way to retreive USB information, but then the DIAGNSTICS section in the man page needs to be fixed so that lsusb must open files under /dev/bus/usb. ubutils is now using libusb. I will update the manpage in the next upload. It would also be nice for lsusb to report that it fails to open files. Unfortunately that is not possible has usbutils does not open the files itself. Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444808: usbutils: lsusb does not report any devices
reopen 444808 thanks Marco d'Itri a écrit : On Oct 01, Aurelien Jarno [EMAIL PROTECTED] wrote: It looks like that once again udev has changed the permission on the USB device nodes to something like 0660. This is plainly wrong. Note that It looks like the user is using a too much recent kernel compiled without backward compatibility sysfs elements and a not recent enough version of udev. I actually have the same problem on my machine (didn't noticed before), I am running kernel 2.6.22-1-amd64 and udev 0.114-2, which is the latest available version. [volta:~]$ ls /dev/bus/usb/001/ -l total 0 crw-rw 1 root root189, 0 2007-09-30 16:47 001 crw-rw 1 root root189, 2 2007-09-30 16:47 003 crw-rw 1 root root189, 6 2007-09-30 14:51 007 crw-rw 1 root root189, 7 2007-09-30 14:51 008 crw-rw 1 root root189, 8 2007-09-30 14:51 009 -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
