21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices

Bug #1976293 reported by Paul Menzel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On a default Ubuntu desktop installation (with GNOME) doing `do-release-upgrade` from 21.10 to 22.04 installed *brltty* breaking FTDI USB serial devices.

```
[ 2435.150025] usb 1-2: new full-speed USB device number 6 using xhci_hcd
[ 2435.305646] usb 1-2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 2435.305660] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2435.305666] usb 1-2: Product: USB Serial Converter
[ 2435.305671] usb 1-2: Manufacturer: FTDI
[ 2435.305675] usb 1-2: SerialNumber: FTFCV4W7
[ 2435.311747] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected
[ 2435.311824] usb 1-2: Detected FT232RL
[ 2435.313260] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0

[ 2437.583625] usb 1-2: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1
[ 2437.585095] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 2437.585168] ftdi_sio 1-2:1.0: device disconnected
```

The brltty problem is tracked in the Debian BTS as #667616 [1], and the solution is to remove the package with `sudo apt purge brltty`.

The question is though, why `do-release-upgrade` installed it in the first place. I do not remember the problem from earlier release upgrades.

[1]: https://bugs.debian.org/667616
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
 644:0:116:0:2022-05-31 15:11:54.155275593 +0200:2022-05-31 15:11:53.683275612 +0200:/var/crash/kdump_lock
 644:0:116:325:2022-05-31 15:11:57.819275442 +0200:2019-08-23 14:33:45.567141279 +0200:/var/crash/kexec_cmd
CurrentDesktop: GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2017-03-20 (1898 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Package: ubuntu-release-upgrader (not installed)
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Tags: wayland-session jammy dist-upgrade
Uname: Linux 5.15.0-33-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-05-06 (26 days ago)
UserGroups: adm lpadmin sambashare sudo
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting
_MarkForUpload: True

Revision history for this message
Sebastien Bacher (seb128) wrote :

Jeremy, that's not a duplicate. The other bug is about brltty claiming the device, the report here is about the package being installed on upgrade which doesn't sound like it should

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Hi Paul,

Please run `apport-collect 1976293` from a terminal on the affected system. This will attach the relevant log files from your system to this bug report.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

ubuntu-desktop-minimal recommends brltty but it also did that for Ubuntu 21.10 so the upgrade logs might be helpful in determining if the package was previously installed or not.

Revision history for this message
Paul Menzel (paulmenzel) wrote : CurrentDmesg.txt.txt

apport information

tags: added: apport-collected dist-upgrade jammy wayland-session
description: updated
Revision history for this message
Paul Menzel (paulmenzel) wrote : JournalErrors.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : ProcEnviron.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : VarLogDistupgradeAptHistorylog.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : VarLogDistupgradeAptclonesystemstate.tar.gz

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : VarLogDistupgradeAptlog.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : VarLogDistupgradeApttermlog.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : VarLogDistupgradeLspcitxt.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : VarLogDistupgradeMainlog.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote : VarLogDistupgradeScreenlog.txt

apport information

Revision history for this message
Paul Menzel (paulmenzel) wrote :
Download full text (5.3 KiB)

My bad, actually looking on the device, *brltty* was installed for a long time. :-(

    /var/log/dpkg.log.12.gz:2020-06-24 18:24:40 upgrade brltty:amd64 5.6-11ubuntu2 6.0+dfsg-4ubuntu6

Sorry about the confusion. It looks like the user tested this exact USB serial converter (0403:6001) the first time.

```
Mai 30 12:14:14 Ixpees kernel: Linux version 5.15.0-33-generic (buildd@lcy02-amd64-037) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #34-Ubuntu SMP Wed May 18 13:34:26 UTC 2022 (Ubuntu 5.15.0-33.34-generic 5.15.30)
[…]
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: new full-speed USB device number 4 using xhci_hcd
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: Product: USB Serial Converter
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: Manufacturer: FTDI
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: SerialNumber: FTFCV4W7
Mai 30 12:16:13 Ixpees mtp-probe[3062]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1"
Mai 30 12:16:13 Ixpees mtp-probe[3062]: bus: 3, device: 4 was not an MTP device
Mai 30 12:16:13 Ixpees snapd[1117]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mai 30 12:16:13 Ixpees snapd[1117]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mai 30 12:16:13 Ixpees systemd[1]: Starting Braille Device Support...
Mai 30 12:16:13 Ixpees kernel: calling usb_serial_init+0x0/0x1000 [usbserial] @ 3008
Mai 30 12:16:13 Ixpees kernel: usbcore: registered new interface driver usbserial_generic
Mai 30 12:16:13 Ixpees kernel: usbserial: USB Serial support registered for generic
Mai 30 12:16:13 Ixpees kernel: initcall usb_serial_init+0x0/0x1000 [usbserial] returned 0 after 105 usecs
Mai 30 12:16:13 Ixpees kernel: calling usb_serial_module_init+0x0/0x1000 [ftdi_sio] @ 3008
Mai 30 12:16:13 Ixpees kernel: usbcore: registered new interface driver ftdi_sio
Mai 30 12:16:13 Ixpees kernel: usbserial: USB Serial support registered for FTDI USB Serial Device
Mai 30 12:16:13 Ixpees kernel: ftdi_sio 3-1.1:1.0: FTDI USB Serial Device converter detected
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: Detected FT232RL
Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB0
Mai 30 12:16:13 Ixpees kernel: initcall usb_serial_module_init+0x0/0x1000 [ftdi_sio] returned 0 after 2817 usecs
Mai 30 12:16:13 Ixpees mtp-probe[3069]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1"
Mai 30 12:16:13 Ixpees mtp-probe[3069]: bus: 3, device: 4 was not an MTP device
Mai 30 12:16:13 Ixpees snapd[1117]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mai 30 12:16:13 Ixpees brltty[3064]: BRLTTY 6.4 rev BRLTTY-6.4 [https://brltty.app/]
Mai 30 12:16:13 Ixpees brltty[3064]: BRLTTY 6.4 rev BRLTTY-6.4 [https://...

Read more...

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.