Thanks, understood.
Took that into consideration for the 6.7-1 merge:
https://code.launchpad.net/~aleasto/ubuntu/+source/brltty/+git/brltty/+merge/477046
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Merge proposal linked:
https://code.launchpad.net/~aleasto/ubuntu/+source/brltty/+git/brltty/+merge/477046
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brltty claiming cp210x
> Perhaps something like 1A86/7523 plugged on 1A40/0101. That being said
it seems like both are generic ids
Ah, but this 1A86/7523 line is properly emitted by upstream in the `usb-
generic.rules` file, so it shouldn't be enabled by default, to avoid
matching such combination of generic devices.
T
> Are you saying we re-enable lines:
> ENV{PRODUCT}=="10c4/ea60
I didn't talk about these lines, but the 403/6001 ones, that do match a
proper Braille manufacturer string:
ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Hedo Reha Technik GmbH",
ENV{BRLTTY_BRAILLE_DRIVER}="hd", GOTO="brltty_u
> aren't the identifiers in ENV{PRODUCT} already idVendor/idProduct?
I don't know the details. From what I gather from the upstream source
code, this device has a special rule to appear like this in the udev
file:
Drivers/Braille/Baum/braille.c:
{ /* NLS eReader Zoomax (20 cells) */
.v
@samuel-thibault, regarding comment #42
1. I don't understand how a device can match both
ENV{PRODUCT}=="1a86/7523/*"
and
ATTRS{idVendor}=="1a40", ATTRS{idProduct}=="0101"
aren't the identifiers in ENV{PRODUCT} already idVendor/idProduct?
2. Are you saying we re-enable lines:
ENV{PRODUCT}==
Confirming this exists still on a fully upgraded system of 22.04 LTS for
vanilla online RS485 converters using the CH340 USB to 485 chip.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
This bug was fixed in the package brltty - 6.4-6ubuntu1
---
brltty (6.4-6ubuntu1) kinetic; urgency=medium
* Resynchronize on Debian
- Remaining changes:
+ add brltty-setup
- debian/brltty-setup
- debian/brltty.install
- debian/rules
+ add init
we funnily have removed these udev rules before (but i guess the patch
was dropped when syncing a new version)
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Changed in: brltty (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brltty claiming cp210x devices on 22.04
To manage notifications about
1. This is Debian bug report #667616.
2. *brltty* was installed when doing `do-release-upgrade` from 21.10 to 22.04
[2].
[1]: https://bugs.debian.org/667616
[2]:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293
** Bug watch added: Debian Bug tracker #667616
h
Hi Steve, would you he able to describe how the patch worked Vs current
behaviour?
If we can’t touch the package, can we remove it from standard install
(like in Debian) to minimise the number of people impacted and/or make
it incompatible with every other package which might be incompatible
with
I understand the importance of fixing this conflict, and I agree it's
bad behavior on the part of the hardware manufacturer that retail
devices were shipped using these generic USB IDs, but the consequence of
the proposed SRU - disabling the use of brltty on the USB ids in
question - is that a blin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: brltty (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
Given that some braille devices are going to stop working with this
update I think this should be release noted and information provided on
how to reenable the devices if necessary.
** Also affects: brltty (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notifi
We should review how the package works but meanwhile the udev rules
change is going to resolve the conflict
** 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
+ por
Thanks Samuel, I've uploaded the changes now.
I also checked a bit the package history since I'm not really familiar
with the package (we used to have Luke working on accessibility but
since he left we mostly carried the status over and don't have anyone
really familiar those changes) and it seems
> it's a bit unclear to me which entries there should be considered
'generic USB IDs'?
They are marked "Generic Identifier", that's
0403:6001
10C4:EA60
10C4:EA80
> I also don't understand why those rules are debian specific
See the diff between ./debian/brltty-udeb.udev.rules and
./Autostart/Ud
@Samuel so I was checking debian/brltty.udev.rules following your
suggestion, but it's a bit unclear to me which entries there should be
considered 'generic USB IDs'?
I also don't understand why those rules are debian specific. How does
upstream handle the devices?
We should stop installing brltt
It also affects FTDI USB to Serial adapters!
$ lsusb
Bus 002 Device 013: ID 0403:6001 Future Technology Devices International, Ltd
FT232 Serial (UART) IC
$ grep -i ftdi /lib/udev/rules.d/*
85-brltty.rules:# HandyTech [FTDI chip]
85-brltty.rules:ENV{PRODUCT}=="403/6001/*", ATTRS{manufacturer}=="F
I have the same issue connecting to Onion Omega2 IoT devices, since they
use cp210x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brltty claiming cp210x devices on 22.04
To manage no
Unfortunately its not just Arduino - its pretty much anything that uses
a cp210x serial device, of which there are many many different things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Tit
I believe that the best course of action would be for the offending
package (brtty) to get fixed. Until it is, perhaps mark is as a conflict
and delete it when people install Arduino.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: brltty (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brl
I might suggest that, for ease of use by end users, if disabling such
devices in the default install, it may be worth packaging a brltty-
conflictingdevices or similar to un-disable them, as opposed to
requiring manual un-disabling of the udev rules.
--
You received this bug notification because
Thanks Samuel for sharing your expertise here!
I would need to check why it has been historically installed by default
but I would expect that's because we want the default installation as
friendly as possible to users that need accessibility. Doing what Debian
is doing is nice but gives an incons
orca only suggests brltty, it's the *-desktop packages which seem to be
recommending brltty.
If Ubuntu really wants to install brltty by default, it should disable
the udev entries for the generic USB IDs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
As mentioned by Sebastien above, I have a smiliar issue which is
blocking the use of the USB as serial port for use with Arduino. If this
helps, my dist-upgrade log is available in another bug report if you
want to have a look: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
release-upgrader/+bug
bug #1970408 is similar with arduino devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
Title:
brltty claiming cp210x devices on 22.04
To manage notifications about this bug go to:
https
> In this case, brltty appeared (or at least the device claim) after a
dist-upgrade
Ah, do you happen to have a log of that dist-upgrade, so we can
determine what brought it in?
> It still feels very bad form for a vendor device to use the default
VID/PID of the underlying converter chip
Yes. Un
In this case, brltty appeared (or at least the device claim) after a
dist-upgrade. I would have had no cause to use it through the initial
installation.
It still feels very bad form for a vendor device to use the default
VID/PID of the underlying converter chip as opposed to the (very easy)
step o
Debian is installing the brltty package only when brltty was used during
installation.
Brltty gets started during installation either through the udev rules,
or started manually from the kernel command line. The finish-install
script just checks out /var/run/brltty.pid to determine whether a brltt
@Samuel, the Ubuntu installer isn't having such smart logic, is Debian
actual doing that and adapting the package set according to the
hardware?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224
T
Yes, but it is meant to be so: the Seika Braille device is announced as
such, so we have to recognize such devices in brltty, otherwise the
Seika Braille devices would not work at all.
The question is rather: why is brltty installed on your system? It is
supposed to be installed only if you instal
34 matches
Mail list logo
