Control: reassign -1 brltty Control: tags -1 + pending Hello,
marcello.carla, le lun. 20 avril 2026 22:59:44 +0200, a ecrit: > The choice that the CP210x is for aid to a visual impaired user and not for > some other device should not be automatic and opaque. Unfortunately, it's the whole computer that is completely opaque to visually-impaired users if their braille device is not automatically detected. And yes, unfortunately some braille device manufacturers do not personalize the USB id so there is no way to auto-detect it properly. > If an USB-uart adapter CP210x is detected during installation, the system > is built-up and configured for a visual impaired user, with brttly and > speech-dispatcher automatically activated at boot. > disabling or de-installing brttly and especially speech-dispatcher is a > nightmare, that normally makes the system unbootable. Ah, that's because when installing with accessibility enabled, a lightdm wrapper is installed for orca, and then removing orca breaks lightdm. I have uploaded a fix, and will see to backport it to trixie. > Alternatively, users should be warned to remove their USB CP210x > during installation. I have now added a question to users when it's the generic ID that is detected for braille, to confirm that it's indeed expected to get accessibility installed etc. That will make the unfortunate owners of such devices have to confirm that yes it's a braille device, but that'll notify users with a USB CP210x about the issue and even allow them to save a reboot without the device. Samuel
