Files app: USB device is not detected after eject and re-insert |
|||||||||
Issue descriptionChromeOS 10452.74.0, 66.0.3359.137 beta-channel elm What steps will reproduce the problem? (1) Insert USB device. USB device can be viewed from Files app (2) Eject USB device by clicking on 'Eject' icon from Files app (3) Remove USB device and re-insert it What is the expected result? Files app should detect the USB drive What happens instead? Nothing happens. Files app does not display USB device entry. Feedback report: https://listnr.corp.google.com/report/85361805558 Issue also reproduced on M67 10575.16.0, 67.0.3396.19 Issue not reproduced on Eve device.
,
Apr 26 2018
Issue 837296 has been merged into this issue.
,
Apr 26 2018
weifangsun@ Sorry about the duplicates. There was a problem with chromium yesterday.
,
Apr 26 2018
No worries! :)
,
Apr 30 2018
,
May 1 2018
Can't access the feedback report for now. Not reproducible on Samus, 66.0.3359.137 beta Acer Chromebook R13 (Elm) specific bug, probably?
,
May 1 2018
,
May 2 2018
,
May 6 2018
From the logs I can see the connect/disconnect, but not the subsequent reconnect. 2018-04-25T16:06:41.322929-07:00 INFO kernel: [ 39.749705] usb 1-2.1: new high-speed USB device number 4 using xhci-mtk 2018-04-25T16:06:41.538936-07:00 INFO kernel: [ 39.966970] usb 2-1.1: new SuperSpeed USB device number 3 using xhci-mtk 2018-04-25T16:06:41.563061-07:00 INFO kernel: [ 39.992001] usb 2-1.1: New USB device found, idVendor=13fe, idProduct=5500 2018-04-25T16:06:41.563101-07:00 INFO kernel: [ 39.992041] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=8 2018-04-25T16:06:41.563106-07:00 INFO kernel: [ 39.992049] usb 2-1.1: Product: Patriot Memory 2018-04-25T16:06:41.563111-07:00 INFO kernel: [ 39.992056] usb 2-1.1: Manufacturer: 2018-04-25T16:06:41.563115-07:00 INFO kernel: [ 39.992062] usb 2-1.1: SerialNumber: 9 2018-04-25T16:06:41.563119-07:00 INFO kernel: [ 39.993691] usb-storage 2-1.1:1.0: USB Mass Storage device detected 2018-04-25T16:06:41.566941-07:00 INFO kernel: [ 39.995010] scsi host0: usb-storage 2-1.1:1.0 2018-04-25T16:06:41.666935-07:00 DEBUG kernel: [ 40.096218] SELinux: initialized (dev proc, type proc), uses genfs_contexts 2018-04-25T16:06:41.669146-07:00 INFO permission_broker[1662]: ProcessPath(/dev/bus/usb/002/003) 2018-04-25T16:06:41.982433-07:00 INFO permission_broker[1662]: AllowUsbDeviceRule: ALLOW 2018-04-25T16:06:41.982453-07:00 INFO permission_broker[1662]: AllowTtyDeviceRule: IGNORE 2018-04-25T16:06:42.086929-07:00 DEBUG kernel: [ 40.514661] SELinux: initialized (dev proc, type proc), uses genfs_contexts 2018-04-25T16:06:42.189809-07:00 INFO permission_broker[1662]: DenyClaimedUsbDeviceRule: DENY 2018-04-25T16:06:42.189833-07:00 INFO permission_broker[1662]: Verdict for /dev/bus/usb/002/003: DENY 2018-04-25T16:06:42.189861-07:00 ERR permission_broker[1662]: OpenPath(...): Domain=permission_broker, Code=permission_denied, Message=Permission to open '/dev/bus/usb/002/003' denied 2018-04-25T16:07:37.558979-07:00 INFO kernel: [ 95.989020] usb 2-1.1: USB disconnect, device number 3 Weifang - do we have an elm device (Acer Chromebook R13) we can reproduce this on? What is the process for working on bugs like these?
,
May 16 2018
Wondering if this ARM vs. Intel related? Is there an ARM-based device in SYD? We should definitely ship you guys one if not :)
,
May 22 2018
No ARM device here (as far as I know, I didn't look too hard).
,
Jun 15 2018
What's happening with this? It's M-67 so I guess we should move the milestone? Can we pick up an ARM device next week when folks are in MTV?
,
Jun 21 2018
,
Jun 22 2018
ARM devices have been requested!
,
Jul 9
Unable to repro on a Hana (same reference board as elm) on 67.0.3396.99
,
Jul 12
Marking this as Won't Fix for now. Please reopen if we continue to see this. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by weifangsun@chromium.org
, Apr 26 2018