Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

Hello,

Mariusz Gronczewski, on Thu 13 Oct 2016 13:06:22 +0200, wrote:
> Looks like it came from installer:

Ok, that makes sense.

> in what circumstances installer starts brltty ?

When udev detects a usb device looking like a braille device. The
problem is that we have a few generic entries: 0403:6001, 10c4:ea60,
and 10c4:ea80.  Braille devices using them are quite common, so we do
want to detect them.  We thought it would be fine doing so from the
installer, but apparently you had your device plugged at that time.

> My guess is that installer detected "braille" device (my usb<->1wire
> converter was plugged into that machine during install) on install and
> decided to install the package.

Yep.

> So the problem should go away if detection is correct.

Yes.  I have now uploaded version 5.4-3 of brltty which additionally
matches the manufacturer id, so that should shrink the issue a lot.

> IMO *if* braille device was detected but not used at all during
> install it it should ask if package should be installed

If it was not used during install, there is usually no use to install
brltty :)

Samuel

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Mariusz Gronczewski]

2016-10-13 0:08 GMT+02:00 Samuel Thibault :
> Mariusz Gronczewski, on Thu 13 Oct 2016 00:03:18 +0200, wrote:
>> Hard to tell, server in question was installed from preseed file and
>> it was only one having that package...
>
> Ok, perhaps /var/log/dpkg.log or /var/log/installer/syslog would show
> the circumstances where it got installed?
>
> Samuel

Looks like it came from installer:

Start-Date: 2016-09-22  12:20:12
Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o
APT::Keep-Fds::=6 -q -y --no-remove install grub-common
Install: gettext-base:amd64 (0.19.3-2, automatic), libpng12-0:amd64
(1.2.50-2+deb8u2, automatic), libfreetype6:amd64 (2.5.2-3+deb8u1,
automatic), grub-common:amd64 (2.02~beta2-22+deb8u1),
libasprintf0c2:amd64 (0.19.3-2, automatic), libfus
e2:amd64 (2.9.3-15+deb8u2, automatic)
End-Date: 2016-09-22  12:20:12

Start-Date: 2016-09-22  12:20:16
Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o
APT::Keep-Fds::=6 -q -y --no-remove install grub-pc
Install: grub2-common:amd64 (2.02~beta2-22+deb8u1, automatic),
grub-pc-bin:amd64 (2.02~beta2-22+deb8u1, automatic), grub-pc:amd64
(2.02~beta2-22+deb8u1), ucf:amd64 (3.0030, automatic)
End-Date: 2016-09-22  12:20:17

Start-Date: 2016-09-22  12:20:25
Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o
APT::Keep-Fds::=6 -q -y --no-remove install brltty
Install: libasound2-data:amd64 (1.0.28-1, automatic),
libbluetooth3:amd64 (5.23-2+b1, automatic), libbrlapi0.6:amd64
(5.2~20141018-5, automatic), brltty:amd64 (5.2~20141018-5),
libasound2:amd64 (1.0.28-1, automatic), libgpm2:amd64 (1.20.4-6.1+b2,
automatic)
End-Date: 2016-09-22  12:20:26


in what circumstances installer starts brltty ?

My guess is that installer detected "braille" device (my usb<->1wire
converter was plugged into that machine during install) on install and
decided to install the package.
So the problem should go away if detection is correct.

IMO *if* braille device was detected but not used at all during
install it it should ask if package should be installed (with no as
default to not screw over automatic install). That way it would be no
difference for someone using it but would allow whoever is installing
it to catch any bugs like that.

-- 
Mariusz Gronczewski (XANi) 
GnuPG: 0xEA8ACE64

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

Mariusz Gronczewski, on Thu 13 Oct 2016 00:03:18 +0200, wrote:
> Hard to tell, server in question was installed from preseed file and
> it was only one having that package...

Ok, perhaps /var/log/dpkg.log or /var/log/installer/syslog would show
the circumstances where it got installed?

Samuel

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Mariusz Gronczewski]

2016-10-12 17:26 GMT+02:00 Samuel Thibault :
> Hello,

> That's still one of the things we'd need to determine.
>
> apt-cache rdepends brltty
>
> doesn't show anything that depends on or recommends brltty,
> except brltty-{espeak,flite,speechd}, which nobody depends on or
> recommends. When removing brltty, does it not uninstall anything?
>
> Samuel

Hard to tell, server in question was installed from preseed file and
it was only one having that package... but I've recently installed its
twin (same repos, same Puppet manifest, same purpose) and it didn't
had it

-- 
Mariusz Gronczewski (XANi) 
GnuPG: 0xEA8ACE64

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

Hello,

Mariusz Gronczewski, on Wed 12 Oct 2016 15:18:46 +0200, wrote:
> At this points it grabs devices that are definitely NOT a generic
> non-customized FTDI device, for example it grabbed my USB<->1wire
> adapter which had "manufacturer"  and "product" field customized:

Oh, I didn't know about these fields.  I'll see with upstream how to
filter on these values.  That said, normally it's the USB ID which is
customised, not manufacturer and product.

> and I also got it as suprise dependency to... *something* but it is
> hard to tell what

That's still one of the things we'd need to determine.

apt-cache rdepends brltty

doesn't show anything that depends on or recommends brltty,
except brltty-{espeak,flite,speechd}, which nobody depends on or
recommends. When removing brltty, does it not uninstall anything?

Samuel

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Mariusz Gronczewski]

At this points it grabs devices that are definitely NOT a generic
non-customized FTDI device, for example it grabbed my USB<->1wire
adapter which had "manufacturer"  and "product" field customized:

Device: ID 0403:6001 Future Technology Devices International, Ltd
FT232 USB-Serial (UART) IC
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x0403 Future Technology Devices International, Ltd
  idProduct  0x6001 FT232 USB-Serial (UART) IC
  bcdDevice6.00
  iManufacturer   1 MERA-PROJEKT
  iProduct2 USB <-> 1Wire (MP00202)
  iSerial 3 MPYRNJYY
  bNumConfigurations  1

and I also got it as suprise dependency to... *something* but it is
hard to tell what

so at least that should be fixed

-- 
Mariusz Gronczewski (XANi) 
GnuPG: 0xEA8ACE64

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Borja Duran]

Package: brltty
Followup-For: Bug #667616

Dear Maintainer,
I'm having the same issue on debian jessie (up to date), fresh install (today),
kde desktop.

Couldn't use my serial port till I uninstalled brltty.

My log on dmesg;
[ ...] usb 1-1.2: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets
config #1
[ ...] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from
ttyUSB0

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

Hello,

Borja Duran, le Wed 03 Sep 2014 15:45:10 +0200, a écrit :
 I'm having the same issue on debian jessie (up to date), fresh install 
 (today),
 kde desktop.
 
 Couldn't use my serial port till I uninstalled brltty.

Well, the question is still the same: how did brltty end up getting
installed on your system?  I don't see what can lead to this situation.
It is expected that you have xbrlapi installed, it is not expected that
you have brltty-x11 or brltty installed.  Did some other packages got
removed when you requested the removal of brltty?

It is *expected* that having brltty installed grabs these kind of serial
ports, because some of our users need that support to be able to use
their computer _at all_.

Samuel


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection [ OFF TOPIC: gnome/gnome-orca dependencies pull brltty unacassarly ]

[Samuel Thibault]

Witold Baryluk, le Sat 09 Jun 2012 02:13:07 +0200, a écrit :
 gnome-desktop-environment is obsolate meta-package, but it Depends just
 on gnome package, which Depends on gnome-orca, which Recommends (IMHO
 should be just Suggests) brltty-x11,

No.  It should instead recommend xbrlapi, which was precisely meant to
avoid that dependency chain.  I've requested it as a follow-up to bug
#653663, but it has apparently been lost in the mboxes.

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection [ OFF TOPIC: gnome/gnome-orca dependencies pull brltty unacassarly ]

[Witold Baryluk]

On 05-23 15:04, Jason White wrote:
 Witold Baryluk bary...@smp.if.uj.edu.pl wrote:
  
  I just wanted to add, that I and my few other friends living on sid have
  similar problem. Various serial devices (microcontroler programators, 3d
  printers, usb-serial converters) stoped working due brltty messup. And 
  brltty
  installed automatically on some upgrade due to the some dependencies of 
  other
  packages, like text2spearch packages probably.
  
  After detecting problem it was matter of uninstalling brltty, but still why 
  it
  need to make live harder to some people?
 
 Because some device manufacturers don't obtain unique vendor/product ids for
 their products and thus BRLTTY can't distinguish between genuine braille
 devices and certain other hardware.
 
 The solution is simple: if you don't have a braille display then make sure
 that BRLTTY is not installed. Those who do have a braille display really need
 it for accessing their systems.
 
 Dependency resolution shouldn't result in installation of BRLTTY for users who
 don't request it, though. Would it be possible to find and fix those
 dependencies?
 
Hello again,

Just trying to install gnome-desktop-environment package, brings by
dependencies a brltty (probably via gnome-accessibility).

gnome-desktop-environment is obsolate meta-package, but it Depends just
on gnome package, which Depends on gnome-orca, which Recommends (IMHO
should be just Suggests) brltty-x11, and it brings whole brltty
machinery.


So it looks that it is subtle bug in orca dependencies. Adding one of
orca maintainers to CC, to see what they think about it about
possibility of chaning Recommends: brltty-x11 to Suggests: brltty-x11 ?

Regards,
Witek

-- 
Witold Baryluk



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Mario Lang]

Jason White ja...@jasonjgw.net writes:

 Witold Baryluk bary...@smp.if.uj.edu.pl wrote:

 I just wanted to add, that I and my few other friends living on sid have
 similar problem. Various serial devices (microcontroler programators, 3d
 printers, usb-serial converters) stoped working due brltty messup. And brltty
 installed automatically on some upgrade due to the some dependencies of other
 packages, like text2spearch packages probably.
 
 After detecting problem it was matter of uninstalling brltty, but still why 
 it
 need to make live harder to some people?

 Because some device manufacturers don't obtain unique vendor/product ids for
 their products and thus BRLTTY can't distinguish between genuine braille
 devices and certain other hardware.

True.

 The solution is simple: if you don't have a braille display then make sure
 that BRLTTY is not installed.

No, I strongly disagree and find your reply counterproductive.
We are already discussing a real solution with Dave upstream.

BRLTTY should be installable by default without giving anyone trouble,
thats one of your really big goals for long term.

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Debian Developer URL:http://debian.org/
  .''`. | Get my public key via finger mlang/k...@db.debian.org
 : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
 `. `'
   `-  URL:http://delysid.org/  URL:http://www.staff.tugraz.at/mlang/



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Jason White]

Mario Lang ml...@debian.org wrote:
 
 BRLTTY should be installable by default without giving anyone trouble,
 thats one of your really big goals for long term.

That's fine, but meanwhile the only solution is not to install it.

In general, I don't think BRLTTY should be installed unless the user
explicitly installs the package or uses braille during the Debian
installation.

The issue isn't just the current problem under discussion, but also the
probing of serial ports (although I suppose that can be turned off if it
happens by default).




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

Jason White, le Wed 23 May 2012 20:43:39 +1000, a écrit :
 Mario Lang ml...@debian.org wrote:
  
  BRLTTY should be installable by default without giving anyone trouble,
  thats one of your really big goals for long term.
 
 That's fine, but meanwhile the only solution is not to install it.
 
 In general, I don't think BRLTTY should be installed unless the user
 explicitly installs the package or uses braille during the Debian
 installation.

In general, we do think that BRLTTY should be installed by default.  Just
like we have drivers for USB keyboards installed by default.  You
shouldn't have to ask the administrator to install some additional
software before being able to use a machine.

 The issue isn't just the current problem under discussion, but also the
 probing of serial ports (although I suppose that can be turned off if it
 happens by default).

Yes, we only want to auto probe safe devices, i.e. USB devices which
known-to-be-unique IDs.

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Witold Baryluk]

Package: brltty
Version: 4.3-3
Followup-For: Bug #667616

Hi,

I just wanted to add, that I and my few other friends living on sid have
similar problem. Various serial devices (microcontroler programators, 3d
printers, usb-serial converters) stoped working due brltty messup. And brltty
installed automatically on some upgrade due to the some dependencies of other
packages, like text2spearch packages probably.

After detecting problem it was matter of uninstalling brltty, but still why it
need to make live harder to some people?




-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.4.0-t43-devel-smp-01513-g9daeaa3-dirty (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to pl_PL.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages brltty depends on:
ii  libbrlapi0.5  4.3-3
ii  libc6 2.13-32
ii  libgpm2   1.20.4-4
ii  libicu48  4.8.1.1-6
ii  libncursesw5  5.9-7
ii  libtinfo5 5.9-7
ii  lsb-base  4.1+Debian4

brltty recommends no packages.

Versions of packages brltty suggests:
pn  brltty-speechd   none
pn  brltty-x11   4.3-3
pn  console-braille  none

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Jason White]

Witold Baryluk bary...@smp.if.uj.edu.pl wrote:
 
 I just wanted to add, that I and my few other friends living on sid have
 similar problem. Various serial devices (microcontroler programators, 3d
 printers, usb-serial converters) stoped working due brltty messup. And brltty
 installed automatically on some upgrade due to the some dependencies of other
 packages, like text2spearch packages probably.
 
 After detecting problem it was matter of uninstalling brltty, but still why it
 need to make live harder to some people?

Because some device manufacturers don't obtain unique vendor/product ids for
their products and thus BRLTTY can't distinguish between genuine braille
devices and certain other hardware.

The solution is simple: if you don't have a braille display then make sure
that BRLTTY is not installed. Those who do have a braille display really need
it for accessing their systems.

Dependency resolution shouldn't result in installation of BRLTTY for users who
don't request it, though. Would it be possible to find and fix those
dependencies?




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Arthur Magill]

Package: brltty
Severity: important

Dear Maintainer,

I discovered this bug when connecting a Prologix GPIB-USB device to my
computer. Internally, the device uses the common FTDI USB-RS232 bridge. When I
connect the device, brltty takes control of the serial port, forcing the
ftdi_sio driver to drop the link, making the adapter unavailable. The solution
was to apt-get remove brltty.

Here is the log when I connect the device with brltty installed:

Apr  4 12:03:28 svalbard kernel: [54345.419899] usb 3-4: New USB device found,
idVendor=0403, idProduct=6001
Apr  4 12:03:28 svalbard kernel: [54345.419905] usb 3-4: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Apr  4 12:03:28 svalbard kernel: [54345.419911] usb 3-4: Product: Prologix
GPIB-USB Controller
Apr  4 12:03:28 svalbard kernel: [54345.419915] usb 3-4: Manufacturer: Prologix
Apr  4 12:03:28 svalbard kernel: [54345.419919] usb 3-4: SerialNumber: PXFO2LEF
Apr  4 12:03:28 svalbard kernel: [54345.437991] xhci_hcd :0f:00.0: WARN:
short transfer on control ep
Apr  4 12:03:28 svalbard mtp-probe: checking bus 3, device 2:
/sys/devices/pci:00/:00:1c.6/:0f:00.0/usb3/3-4
Apr  4 12:03:28 svalbard mtp-probe: bus: 3, device: 2 was not an MTP device
Apr  4 12:03:28 svalbard kernel: [54345.532164] usbcore: registered new
interface driver usbserial
Apr  4 12:03:28 svalbard kernel: [54345.532199] USB Serial support registered
for generic
Apr  4 12:03:28 svalbard kernel: [54345.532276] usbcore: registered new
interface driver usbserial_generic
Apr  4 12:03:28 svalbard kernel: [54345.532282] usbserial: USB Serial Driver
core
Apr  4 12:03:28 svalbard kernel: [54345.535686] USB Serial support registered
for FTDI USB Serial Device
Apr  4 12:03:28 svalbard kernel: [54345.535761] ftdi_sio 3-4:1.0: FTDI USB
Serial Device converter detected
Apr  4 12:03:28 svalbard kernel: [54345.535807] usb 3-4: Detected FT232RL
Apr  4 12:03:28 svalbard kernel: [54345.535809] usb 3-4: Number of endpoints 2
Apr  4 12:03:28 svalbard kernel: [54345.535812] usb 3-4: Endpoint 1
MaxPacketSize 64
Apr  4 12:03:28 svalbard kernel: [54345.535815] usb 3-4: Endpoint 2
MaxPacketSize 64
Apr  4 12:03:28 svalbard kernel: [54345.535817] usb 3-4: Setting MaxPacketSize
64
Apr  4 12:03:28 svalbard kernel: [54345.540873] usb 3-4: FTDI USB Serial Device
converter now attached to ttyUSB0
Apr  4 12:03:28 svalbard kernel: [54345.540897] usbcore: registered new
interface driver ftdi_sio
Apr  4 12:03:28 svalbard kernel: [54345.540901] ftdi_sio: v1.6.0:USB FTDI
Serial Converters Driver
Apr  4 12:03:29 svalbard kernel: [54346.971965] usb 3-4: usbfs: interface 0
claimed by ftdi_sio while 'brltty' sets config #1
Apr  4 12:03:29 svalbard kernel: [54346.981436] xhci_hcd :0f:00.0: WARN:
short transfer on control ep
Apr  4 12:03:29 svalbard kernel: [54346.982641] ftdi_sio ttyUSB0: FTDI USB
Serial Device converter now disconnected from ttyUSB0
Apr  4 12:03:29 svalbard kernel: [54346.982668] ftdi_sio 3-4:1.0: device
disconnected

And with brltty removed:

Apr  4 12:11:47 svalbard kernel: [54844.693331] usb 1-1.2: New USB device
found, idVendor=0403, idProduct=6001
Apr  4 12:11:47 svalbard kernel: [54844.693338] usb 1-1.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Apr  4 12:11:47 svalbard kernel: [54844.693344] usb 1-1.2: Product: Prologix
GPIB-USB Controller
Apr  4 12:11:47 svalbard kernel: [54844.693349] usb 1-1.2: Manufacturer:
Prologix
Apr  4 12:11:47 svalbard kernel: [54844.693353] usb 1-1.2: SerialNumber:
PXFO2LEF
Apr  4 12:11:47 svalbard kernel: [54844.697499] ftdi_sio 1-1.2:1.0: FTDI USB
Serial Device converter detected
Apr  4 12:11:47 svalbard kernel: [54844.697556] usb 1-1.2: Detected FT232RL
Apr  4 12:11:47 svalbard kernel: [54844.697561] usb 1-1.2: Number of endpoints
2
Apr  4 12:11:47 svalbard kernel: [54844.697565] usb 1-1.2: Endpoint 1
MaxPacketSize 64
Apr  4 12:11:47 svalbard kernel: [54844.697569] usb 1-1.2: Endpoint 2
MaxPacketSize 64
Apr  4 12:11:47 svalbard kernel: [54844.697573] usb 1-1.2: Setting
MaxPacketSize 64
Apr  4 12:11:47 svalbard kernel: [54844.697964] usb 1-1.2: FTDI USB Serial
Device converter now attached to ttyUSB0

With brltty removed, the interface functions normally. This appears to be a
known problem. I found the solution here:
http://www.ladyada.net/learn/arduino/lesson0-lin.html. See also Ubuntu bug
#175182. Can brltty be convinced not to grab this connection?



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages brltty depends on:
ii  libbrlapi0.5  4.3-2
ii  libc6 2.13-27
ii  libgpm2   1.20.4-4
ii  libicu48  4.8.1.1-5
ii  libncursesw5  5.9-4
ii  libtinfo5 5.9-4
ii  lsb-base  3.2+Debian31

brltty recommends no packages.

Versions of packages 

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

tags 667616 + wontfix
thanks

Hello,

Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :
 Can brltty be convinced not to grab this connection?

It could, but we don't want to, as it would break brltty for people who
use the braille devices with chips using that ID, making the computer
completely unusable for them, really not a good thing.

How brltty ended up being installed on your system?  Was it brought
through some dependency?

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

Samuel Thibault, le Thu 05 Apr 2012 14:26:26 +0100, a écrit :
 Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :
  Can brltty be convinced not to grab this connection?
 
 It could, but we don't want to, as it would break brltty for people who
 use the braille devices with chips using that ID, making the computer
 completely unusable for them, really not a good thing.
 
 How brltty ended up being installed on your system?  Was it brought
 through some dependency?

And still, ideally we'd want brltty installed by default on all systems,
ready to be triggered by udev (but not for all devices, all those which
are known not to conflict with other serial/USB converters).

What Ubuntu did was to disable brltty startup by default, which we don't
want either.

Let me summarize the scenario I can see:

- brltty is used during the Debian Installer, and shall thus be
installed and enabled on the target system.
- brltty is not used during the Debian Installer, but should still be
installed on the target system, but not enabled, and rather just
triggered by udev.
- someone installs brltty by hand. I believe in that case we want
to enable it too (all it takes to make braille work in consoles is
installing brltty).

So perhaps we should ship brltty enabled by default, and make the Debian
Installer disable it when it was not used during installation?

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Arthur Magill]

Hi Samuel,


Can brltty be convinced not to grab this connection?


It could, but we don't want to, as it would break brltty for people who
use the braille devices with chips using that ID, making the computer
completely unusable for them, really not a good thing.


True. But as it stands, it makes all FTDI based serial devices unusable, 
except braille devices. This doesn't seem great either. There must be a 
way to further differentiate these devices? Or is this intended to catch 
older braille devices being used via an RS232-USB adapter?



How brltty ended up being installed on your system?  Was it brought
through some dependency?


That's a good question. I never explicitly asked for it, so I assumed it 
came as part of the standard installation? My system says:


# apt-cache rdepends brltty
brltty
Reverse Depends:
  speechd-el
  brltty-x11
  brltty-speechd
  brltty-flite
  speechd-el
  brltty-x11
  brltty-speechd
  brltty-flite
  brltty-espeak

Thanks for looking into this.

  Arthur



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Mario Lang]

Arthur Magill arthur.mag...@epfl.ch writes:

 Hi Samuel,

 Can brltty be convinced not to grab this connection?

 It could, but we don't want to, as it would break brltty for people who
 use the braille devices with chips using that ID, making the computer
 completely unusable for them, really not a good thing.

 True. But as it stands, it makes all FTDI based serial devices
 unusable, except braille devices. This doesn't seem great
 either.

I agree.

 There must be a way to further differentiate these devices? Or is this
 intended to catch older braille devices being used via an RS232-USB
 adapter?

No.  Its actually a genuine fuckup of the manufacturer for this
particular braille display.  They simply put an FTDI chip in for
providing their USB connectivity, but totally neglected to do any
branding. :(

 How brltty ended up being installed on your system?  Was it brought
 through some dependency?

 That's a good question. I never explicitly asked for it, so I assumed
 it came as part of the standard installation?

Either way, we actually aim for brltty being installable per default in
the long run, so we need to resolve this in some way.

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Debian Developer URL:http://debian.org/
  .''`. | Get my public key via finger mlang/k...@db.debian.org
 : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
 `. `'
   `-  URL:http://delysid.org/  URL:http://www.staff.tugraz.at/mlang/



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

[Samuel Thibault]

Arthur Magill, le Thu 05 Apr 2012 15:43:29 +0200, a écrit :
 Can brltty be convinced not to grab this connection?
 
 It could, but we don't want to, as it would break brltty for people who
 use the braille devices with chips using that ID, making the computer
 completely unusable for them, really not a good thing.
 
 True. But as it stands, it makes all FTDI based serial devices unusable,
 except braille devices. This doesn't seem great either.

Agreed, but it does not make the machine completely unusable.

 There must be a way to further differentiate these devices?

Unfortunately, no.

 Or is this intended to catch older braille devices being used via an
 RS232-USB adapter?

No, these would be configured through /dev/ttyUSB0.

 How brltty ended up being installed on your system?  Was it brought
 through some dependency?
 
 That's a good question. I never explicitly asked for it, so I assumed it
 came as part of the standard installation? My system says:
 
 # apt-cache rdepends brltty
 brltty
 Reverse Depends:
   speechd-el
   brltty-x11

Ooh, I see why. That's because orca now recommends brltty-x11, which
happens to depend on brltty just because it contains a driver. We'll
have a look at avoiding that.

Samuel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org