21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices
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-
```
[ 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-
[1]: https:/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckR
CrashDB: ubuntu
CrashReports:
644:0:
644:0:
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-
ProcVersionSign
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
VarLogDistupgra
INFO:root:
INFO:root:No xorg.conf, exiting
_MarkForUpload: True
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