fwupd breaking access to certain usb devices

Bug #1717009 reported by TheOnlyJoey
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fwupd
Fix Released
Unknown
fwupd (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Since this version, some devices can not be opened as normal anymore.

In this case devices with 0483:5750 STMicroelectronics chips will be claimed by fwupd and get stuck in a error state.
fwupd should check the usb descriptor to see if it is actually the right device, since chips can be re-used for multiple devices (this one being use in the Deepoon E2, NOLO CV1 and to name 2) while being claimed for a 8bitdo controller.

kernel: usb 1-1: New USB device found, idVendor=0483, idProduct=5750
kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 1-1: Product: NOLO
kernel: usb 1-1: Manufacturer: LYRobotix
kernel: usb 1-1: SerialNumber: 56E2805B3035
kernel: hid-generic 0003:0483:5750.0010: hiddev2,hidraw6: USB HID v1.10 Device [LYRobotix NOLO] on usb-0000:00:14.0-1/input0
mtp-probe[23555]: checking bus 1, device 25: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
mtp-probe[23555]: bus: 1, device: 25 was not an MTP device
fwupd[2667]: Failed to add 8Bitdo device: unexpected device response

It gets stuck in this state and no other applications are able to use the devices, i guess that fwupd does not exit correctly.
Checking the name of the device should fix this.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: fwupd 0.9.7-2
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 13 21:29:15 2017
InstallationDate: Installed on 2017-06-15 (89 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613)
SourcePackage: fwupd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
TheOnlyJoey (theonlyjoey) wrote :
description: updated
Revision history for this message
Richard Hughes (richard-hughes) wrote :

Can you file an upstream report please.

Changed in fwupd (Ubuntu):
importance: Undecided → High
tags: added: rls-aa-incoming
Revision history for this message
TheOnlyJoey (theonlyjoey) wrote :

@richard-hughes My apologies for the delay, bugreport done at https://github.com/hughsie/fwupd/issues/275

Changed in fwupd (Ubuntu):
status: New → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in fwupd (Ubuntu):
status: Triaged → In Progress
Revision history for this message
jondecker76 (jondecker76-gmail) wrote :

I'm having the same problem in Ubuntu 17.04 and 17.10 with a Saga vinyl cutter/plotter that uses a STMicroelectronics chip.

I see that there is a fix upstream; How can I go about applying the fix myself so I can get things working again?

Revision history for this message
Mario Limonciello (superm1) wrote :

The fix is included in the 1.0.1 release in bionic.

Changed in fwupd (Ubuntu):
status: In Progress → Fix Released
Changed in fwupd:
status: Unknown → Fix Released
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.