Nemo hangs when PTP is unable to return friendly name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nemo (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
NOTE: I think this is probably so low priority it may never make sense to fix, but I wanted to document it in case others are stumbling across this and to ensure a web search leads those users somewhere.
Expected behavior: Nemo to open with a USB device connected.
# Actual Behavior
When a specific low-quality, proprietary tablet device is connected to my computer, Nemo rarely opens. Nemo usually times out, but it occasionally opens after a multi-minute delay. Also, disconnecting the low-quality hardware resolves the issue. I'm guessing that Nemo is blocked attempting to fetch the "friendly device name" in the logs below.
# Logs
Doing my best to identify some logging, I typically see these symptoms:
when attempting to launch Nemo from the terminal: `Could not register Nemo as a remote: Timeout was reached`
in Syslog:
```
Nov 12 20:51:43 dell-XPS-15-7590 gvfsd[542176]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Nov 12 20:51:43 dell-XPS-15-7590 gvfsd[542176]: Error 2: Error 02ff: PTP I/O Error
Nov 12 20:52:47 dell-XPS-15-7590 gvfsd[542176]: PTP: reading event an error 0x01 occurred
```
# Technical Context
Architecture: amd64
Nemo:
Installed: 4.6.5+ulyana
Candidate: 4.6.5+ulyana
Version table:
*** 4.6.5+ulyana 500
500 http://
100 /var/lib/
4.4.2-2 500
500 http://
Description: Linux Mint 20
Release: 20
Same here.
Except I didn't get the text `Could not register Nemo as a remote: Timeout was reached`
Plus nemo grabs the keyboard access for its own exclusive use.
So, for lambda user, it looks like the only solution is to switch off your computer.
ubuntu 18.04
nemo 3.6.5