Bug 914575

Summary: USB devices are not detected on OpenSuse 13.2 as it happens with previous OpenSuse versions
Product: [openSUSE] openSUSE Distribution Reporter: Forgotten User BcX7nIFOzy <forgotten_BcX7nIFOzy>
Component: OtherAssignee: Oliver Neukum <oneukum>
Status: RESOLVED NORESPONSE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: bwiedemann, chcao, forgotten_BcX7nIFOzy, jsmeix, suse-beta, tiwai
Version: 13.2Flags: oneukum: needinfo? (chcao)
Target Milestone: ---   
Hardware: All   
OS: openSUSE 13.2   
Whiteboard:
Found By: Third Party Developer/Partner Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Contains lsusb output and strace
audit.log file

Description Forgotten User BcX7nIFOzy 2015-01-23 18:00:46 UTC
Created attachment 620729 [details]
Contains lsusb output and strace

On connecting a USB device, no details except VID and PID are obtained. lsusb also lists only VID and PID, "lsusb -v" doesnt provide details as it has been happening with previous OpenSuse versions.

We see that the USB device is listed under /dev but only after system restart any information other than VID or PID can be queried. "lsusb -v" also works as expected after system restart.

Below are the steps to reproduce:

1)	Install openSUSE 13.2 from the ISO image  or DVD.
2)	Connect any USB device (e.g I connected one HP printer and another SanDisk thumb drive ) 
3)	Now run lsusb -d <VID:PID> -v (Once for HP printer and again for SanDisk and observe the output.) 
4)	Error message “Couldn't open device, some information will be missing” is seen in the output for both cases.
5)	strace command output for lsusb command reports “open("/dev/bus/usb/001/004", O_RDWR)    = -1 EACCES (Permission denied)” error
6)	Output of all commands is attached in the usb_log.txt file
Comment 1 Bernhard Wiedemann 2015-01-24 14:23:43 UTC
EACCES always lets me think of apparmor. Please check with
grep DENIED /var/log/audit/audit.log
Comment 2 Marcus Meissner 2015-01-26 08:20:57 UTC
I do not think apparmor is involved.

lsusb and lsusb -v 
work nicely here.

/dev/bus/usb is mode 644, root:root here. what is it on your system?
Comment 3 Forgotten User BcX7nIFOzy 2015-01-27 10:22:15 UTC
Hi

All the debug information are in the attached file. However I will copy the requested info:

~*~
hptest@linux-qq4j:~> ls -la /dev/bus/usb total 0 drwxr-xr-x 4 root root  80 Jan 23 16:35 .
drwxr-xr-x 3 root root  60 Jan 23 16:35 ..
drwxr-xr-x 2 root root 100 Jan 23 18:40 001 drwxr-xr-x 2 root root  80 Jan 23 16:35 002

hptest@linux-qq4j:~> ls -la /dev/bus/usb/001 total 0
drwxr-xr-x 2 root root    100 Jan 23 18:40 .
drwxr-xr-x 4 root root     80 Jan 23 16:35 ..
crw-rw-r-- 1 root root 189, 0 Jan 23 16:35 001
crw-rw-r-- 1 root lp   189, 2 Jan 23 18:24 003
crw-rw-r-- 1 root root 189, 3 Jan 23 18:40 004

hptest@linux-qq4j:~> ls -la /dev/bus/usb/001/003
crw-rw-r-- 1 root lp 189, 2 Jan 23 18:24 /dev/bus/usb/001/003

hptest@linux-qq4j:~> ls -la /dev/bus/usb/001/004
crw-rw-r-- 1 root root 189, 3 Jan 23 18:40 /dev/bus/usb/001/004 ~*~

Even the strace output clearly mentions Access Denied error. I am attaching the audit.log too.
Comment 4 Forgotten User BcX7nIFOzy 2015-01-27 10:23:05 UTC
Created attachment 620988 [details]
audit.log file
Comment 5 Christian Boltz 2015-01-27 20:51:43 UTC
The audit.log only contains some nscd denials for nscd (writing /run/nscd/*) which will be fixed with the next AppArmor update.

There aren't any other AppArmor denials in the log, especially nothing related to USB devices -> AppArmor is not involved in this bug
Comment 6 Forgotten User BcX7nIFOzy 2015-01-28 11:04:18 UTC
We observe that this problem is happening only with Gnome but not with KDE
Comment 7 Forgotten User S7BaJJXAH- 2015-01-28 16:31:36 UTC
I no longer am contributing to openSUSE, so I don't know why you assigned this bug to me...
Comment 8 Chenzi Cao 2015-01-29 08:31:53 UTC
Hi Oliver, would you please kindly help to have a look at here? I can not find a bugowner for this issue, would you please help here? Thank you!
Comment 9 Oliver Neukum 2015-01-29 09:56:46 UTC
(In reply to Chenzi Cao from comment #8)
> Hi Oliver, would you please kindly help to have a look at here? I can not
> find a bugowner for this issue, would you please help here? Thank you!

Even under 13.1 not all information about a device is open to any user.
From a 13.1 system:

Bus 003 Device 002: ID 138a:003f Validity Sensors, Inc.                                                                                                                                                                           
Couldn't open device, some information will be missing                                                                                                                                                                            
Device Descriptor:                                                                                                                                                                                                                
  bLength                18                                                                                                                                                                                                       
  bDescriptorType         1                                                                                                                                                                                                       
  bcdUSB               1.10                                                                                                                                                                                                       
  bDeviceClass          255 Vendor Specific Class                                                                                                                                                                                 
  bDeviceSubClass        18                                                                                                                                                                                                       
  bDeviceProtocol       255                                                                                                                                                                                                       
  bMaxPacketSize0         8                                                                                                                                                                                                       
  idVendor           0x138a Validity Sensors, Inc.                                                                                                                                                                                
  idProduct          0x003f 
  bcdDevice            1.04
  iManufacturer           0 
  iProduct                0 
  iSerial                 1 
  bNumConfigurations      1
  Configuration Descriptor:


What exactly were you seeing with 13.1?
Comment 10 Oliver Neukum 2015-10-08 09:27:16 UTC
No response in 9 months