[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Sebastien Bacher
1958224 at bugs.launchpad.net
Wed Jun 29 07:23:08 UTC 2022
I've uploaded a new SRU, updating the description according.
The new revision handle the situation by asking a debconf question to
users updating from a version which included the conflicting rules which
ask them if they want to keep that config or not. The question is only
asked if a device matching one of those IDs is found on the system, the
answer default to 'yes' to avoid accidentally disabling a working screen
reader for people who rely on those.
After the SRU will be in updates people upgrading from earlier serie to
22.04 will not see the question nor having the conflicting rules. New
installations from 22.04.1 when it's out will also not have the issue
** Description changed:
* Impact
The brltty udev rules are claiming generic devices IDs which makes some
other devices like Arduino cards not able to interact with the serial
port anymore
* Test Case
Try to use an Arduino over a cp210x or FTDI serial port, it should be
able to talk to the computer
+
+ - upgrades from focal/impish to the SRU version should have no question
+ and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
+
+ - upgrades from brltty 6.4-4ubuntu2
+ 1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is connectect at the time of the upgrade it should prompt with the debconf question
+ 1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should be generated
+ 1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not installed
+
+ 2. if no matching device is connected
+ there should be no debconf question nor /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
+
+ - installing brltty when it was not installed
+ no question and no config generated
* Regression potential
There are some braille devices on the market using generic IDs which are
going to stop working out of the box. Those devices are uncommon and
it's arguably an hardware bugs they are using those IDs.
-------------------
Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy
brltty: Installed: 6.4-2ubuntu1
brltty appears once again to be claiming cp210x devices with the
vendor/product ID of:
idVendor=10c4, idProduct=ea60
Example dmesg output:
999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
[ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs
[ 999.215978] usb 3-6.3: SerialNumber: 0005
[ 999.234070] usbcore: registered new interface driver usbserial_generic
[ 999.234081] usbserial: USB Serial support registered for generic
[ 999.235262] usbcore: registered new interface driver cp210x
[ 999.235272] usbserial: USB Serial support registered for cp210x
[ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected
[ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
[ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
[ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42
[ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
[ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 999.995066] cp210x 3-6.3:1.0: device disconnected
** Description changed:
* Impact
The brltty udev rules are claiming generic devices IDs which makes some
other devices like Arduino cards not able to interact with the serial
port anymore
* Test Case
Try to use an Arduino over a cp210x or FTDI serial port, it should be
able to talk to the computer
- upgrades from focal/impish to the SRU version should have no question
and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- - upgrades from brltty 6.4-4ubuntu2
+ - upgrades from brltty 6.4-4ubuntu2
1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is connectect at the time of the upgrade it should prompt with the debconf question
1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should be generated
1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not installed
2. if no matching device is connected
there should be no debconf question nor /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- installing brltty when it was not installed
no question and no config generated
* Regression potential
- There are some braille devices on the market using generic IDs which are
- going to stop working out of the box. Those devices are uncommon and
- it's arguably an hardware bugs they are using those IDs.
+ If the debconf logic is wrong users could be prompted with the question
+ when not needed or not prompted when they should. If the udev rules was
+ incorrect or wrongly installed it could lead to have brltty not starting
+ when it should
-------------------
Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy
brltty: Installed: 6.4-2ubuntu1
brltty appears once again to be claiming cp210x devices with the
vendor/product ID of:
idVendor=10c4, idProduct=ea60
Example dmesg output:
999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
[ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs
[ 999.215978] usb 3-6.3: SerialNumber: 0005
[ 999.234070] usbcore: registered new interface driver usbserial_generic
[ 999.234081] usbserial: USB Serial support registered for generic
[ 999.235262] usbcore: registered new interface driver cp210x
[ 999.235272] usbserial: USB Serial support registered for cp210x
[ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected
[ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
[ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
[ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42
[ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
[ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 999.995066] cp210x 3-6.3:1.0: device disconnected
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brltty claiming cp210x devices on 22.04
Status in brltty package in Ubuntu:
Fix Released
Status in brltty source package in Jammy:
In Progress
Status in brltty package in Debian:
Confirmed
Bug description:
* Impact
The brltty udev rules are claiming generic devices IDs which makes
some other devices like Arduino cards not able to interact with the
serial port anymore
* Test Case
Try to use an Arduino over a cp210x or FTDI serial port, it should be
able to talk to the computer
- upgrades from focal/impish to the SRU version should have no
question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- upgrades from brltty 6.4-4ubuntu2
1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is connectect at the time of the upgrade it should prompt with the debconf question
1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should be generated
1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not installed
2. if no matching device is connected
there should be no debconf question nor /etc/udev/rules.d/86-brltty-usbgeneric.rules generated
- installing brltty when it was not installed
no question and no config generated
* Regression potential
If the debconf logic is wrong users could be prompted with the
question when not needed or not prompted when they should. If the udev
rules was incorrect or wrongly installed it could lead to have brltty
not starting when it should
-------------------
Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy
brltty: Installed: 6.4-2ubuntu1
brltty appears once again to be claiming cp210x devices with the
vendor/product ID of:
idVendor=10c4, idProduct=ea60
Example dmesg output:
999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
[ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs
[ 999.215978] usb 3-6.3: SerialNumber: 0005
[ 999.234070] usbcore: registered new interface driver usbserial_generic
[ 999.234081] usbserial: USB Serial support registered for generic
[ 999.235262] usbcore: registered new interface driver cp210x
[ 999.235272] usbserial: USB Serial support registered for cp210x
[ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected
[ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
[ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
[ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42
[ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
[ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 999.995066] cp210x 3-6.3:1.0: device disconnected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions
More information about the foundations-bugs
mailing list