[Bug 1092839] New: brltty hogs USB serial ports without obvious way to disable
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 Bug ID: 1092839 Summary: brltty hogs USB serial ports without obvious way to disable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: afaerber@suse.com QA Contact: qa-bugs@suse.de CC: lnussel@suse.com Found By: --- Blocker: --- On Leap 15.0 certain /dev/ttyUSBx devices are not showing up as expected. For example, I attach a hub with e.g. two USB UART adapters: Bus 004 Device 012: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family] Bus 004 Device 011: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family] but there's only a /dev/ttyUSB0 and no /dev/ttyUSB1. This appears to be related to brltty, because "zypper rm brltty" and re-plugging the hub fixes the issue. However, brltty appears to come back with the next "zypper dup", so it's no permanent fix. The actual brltty@foo service instance cannot be stopped either. The accessibility pane in GNOME Control Center does not appear to offer any options to disable this behavior. No related YaST module that I can spot either. Can we please get sane defaults again like in 42.3 and only activate such destructive accessibility services when explicitly requested by the user? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 Andreas Färber <afaerber@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c1 --- Comment #1 from Andreas Färber <afaerber@suse.com> --- For now "zypper addlock brltty" made the next "zypper dup" keep it working. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c2 Oliver Neukum <oneukum@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |mgorse@suse.com --- Comment #2 from Oliver Neukum <oneukum@suse.com> --- This is essentially bsc#1007652 for another device ID. Adding Michael Gorse. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c3 --- Comment #3 from Ludwig Nussel <lnussel@suse.com> --- brltty is recommended by orca which is recommended by gdm -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c4 Stanislav Brabec <sbrabec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com Assignee|sbrabec@suse.com |ro@suse.com --- Comment #4 from Stanislav Brabec <sbrabec@suse.com> --- Maintainer of brttty is Ruediger Oertel. Reassigning. The problem is indeed the USB id. USB id 10c4:ea60 is registered in brltty-5.5/Autostart/Udev/rules. 10C4:EA80 has the same problem: # Device: 10C4:EA60 # Generic Identifier # Vendor: Cygnal Integrated Products, Inc. # Product: CP210x UART Bridge / myAVR mySmartUSB light # BrailleMemo [Pocket] # Seika [Braille Display] ENV{PRODUCT}=="10c4/ea60/*", ENV{BRLTTY_BRAILLE_DRIVER}="mm,sk", GOTO="brltty_usb_run" # Device: 10C4:EA80 # Generic Identifier # Vendor: Cygnal Integrated Products, Inc. # Product: CP210x UART Bridge # Seika [Note Taker] ENV{PRODUCT}=="10c4/ea80/*", ENV{BRLTTY_BRAILLE_DRIVER}="sk", GOTO="brltty_usb_run" According to kroesche from Silicon Labs, the correct assignment for these two USB ids are: 10C4:EA60 CP210x UART Bridge https://usb-ids.gowdy.us/read/UD/10c4/ea60 10C4:EA80 CP2110 HID UART Bridge https://usb-ids.gowdy.us/read/UD/10c4/ea80 So this is cleanly a fault of Braille device manufacturer. Vendor ignored rules and released their devices with the unchanged default UART Bridge USB id. They even did not request custom product id from Silicon Labs. https://www.silabs.com/products/interface/request-product-id brltty udev rule either has to add a helper to identify the Braille device (without breaking of other serial devices), or we have to live with a Braille device that does not work out of the box and needs configuration. As CP210x are very common, it is even possible that brltty udev configuration would require to configure exact USB connector. Otherwise the user of Braille device would not be able to use a wide set of devices (GPSes, AVR programmers, serial converters etc.). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c5 --- Comment #5 from Stanislav Brabec <sbrabec@suse.com> --- Testing package disabling these two: https://build.opensuse.org/project/show/home:sbrabec:branches:openSUSE:Leap:... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c6 --- Comment #6 from Oliver Neukum <oneukum@suse.com> --- (In reply to Stanislav Brabec from comment #5)
Testing package disabling these two: https://build.opensuse.org/project/show/home:sbrabec:branches:openSUSE:Leap: 15.0
That will likely fix this bug. But will you do this again and again for every new abused device ID? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c7 --- Comment #7 from Stanislav Brabec <sbrabec@suse.com> --- Comment 6 (Oliver Neukum): I read the whole rules file and found one another broken device, which abuses FTDI USB ud: # Device: 0403:6001 # Generic Identifier # Vendor: Future Technology Devices International, Ltd # Product: FT232 USB-Serial (UART) IC # Albatross [all models] # Cebra [all models] # HIMS [Sync Braille] # HandyTech [FTDI chip] # MDV [all models] ENV{PRODUCT}=="403/6001/*", ENV{BRLTTY_BRAILLE_DRIVER}="at,ce,hm,ht,md", GOTO="brltty_usb_run" I will comment this out as well. Some vendors of generic USB chips even offer USB ids for free for devices based on their hardware, so it is a fault of the Braille device manufacturer. This is not the first application and not the first USB id where it happened. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c8 --- Comment #8 from Stanislav Brabec <sbrabec@suse.com> --- If the manufacturer sets at least textual USB name, it is still possible to add auto-detection. But I don't have any of these devices to check and add such rule. Reference to FT232: https://usb-ids.gowdy.us/read/UD/0403/6001 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 http://bugzilla.opensuse.org/show_bug.cgi?id=1092839#c12 --- Comment #12 from Stanislav Brabec <sbrabec@suse.com> --- Moving the discussion to the upstream, as it has a heavy impact to blind people. https://brltty.app/pipermail/brltty/2018-May/015936.html Revoking the request. I just found that the proposed patch is not sufficient. it also hooks to the kernel. My GPS Qstarz BT-1000P is also broken, so I can test it. Even with the patch, it still fails: [48419.996278] usb 1-1.3: new full-speed USB device number 5 using ehci-pci [48420.106379] usb 1-1.3: New USB device found, idVendor=10c4, idProduct=ea60 [48420.106386] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [48420.106390] usb 1-1.3: Product: CP2102 USB to UART Bridge Controller [48420.106394] usb 1-1.3: Manufacturer: Silicon Labs [48420.106397] usb 1-1.3: SerialNumber: 0001 [48420.133630] usbcore: registered new interface driver usbserial_generic [48420.133644] usbserial: USB Serial support registered for generic [48420.135750] usbcore: registered new interface driver cp210x [48420.135763] usbserial: USB Serial support registered for cp210x [48420.135788] cp210x 1-1.3:1.0: cp210x converter detected [48420.137735] usb 1-1.3: cp210x converter now attached to ttyUSB0 [48420.188395] usb 1-1.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [48420.189018] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [48420.189041] cp210x 1-1.3:1.0: device disconnected [48424.103414] input: BRLTTY 5.6 Linux Screen Driver Keyboard as /devices/virtual/input/input10 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092839 Stanislav Brabec <sbrabec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1093378 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com