Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1473415 - RQR12.07_B0029 update hangs, and breaks Logitech wireless USB mouse
Summary: RQR12.07_B0029 update hangs, and breaks Logitech wireless USB mouse
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupd
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-20 18:26 UTC by Paul Eggert
Modified: 2019-01-08 02:40 UTC (History)
8 users (show)

Fixed In Version: fwupd-1.2.3-1.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-08 02:40:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul Eggert 2017-07-20 18:26:01 UTC 
Description of problem:

Attempting to install the latest Fedora 26 patches caused my Logitech wireless mouse to stop working.

Version-Release number of selected component (if applicable):

The update that hanged was labeled "Logitech Unifying Receiver RQR12.01_B0019 -> RQR12.07_B0029" in the software update GUI. Presumably either one version or the other is installed, or perhaps a mixed-up mixture of the two versions. I don't know how to check.

How reproducible:

My desktop uses an ASUSTeK M4A87TD/USB3 motherboard. I have a Dell SK-8110 PS/2 keyboard (my Logitech keyboard died and this is a replacement). I have a Logitech M510 wireless USB mouse, P/N 810-001897.

Steps to Reproduce:
1. Run the Software Update GUI.
2. Click on "Updates".
3. There is a row saying "Logitech Unifying Receiver / RQR12.01_B0019 -> RQR12.07_B0029 / This release addresses an unencrypted keystroke injection issue known as Bastille security issue #11...." In the row there is an "Update" button. Click on it.

Actual results:

Nothing happens. The mouse stops working. I waited several minutes. Eventually I rebooted by using the keyboard. The mouse still doesn't work.

Expected results:

I expected the update to work, perhaps by rebooting the system.

Additional info:

I would appreciate being given a command-line way to do the update, and to monitor its progress. I tried this:

dnf --enablerepo=updates-debuginfo update
reboot

but it does not seem to suffice; the mouse still does not work after rebooting, and the updates GUI still lists the Logitech Unifying Receiver patch as not being installed.

To work around the problem I substituted a Logitech B100 (P/N 810-001397) wired USB mouse, which works fine. At least now I know no nearby attackers are injecting mouse movements....
Comment 1 Richard Fearn 2017-07-20 18:29:39 UTC 
The unifying-receiver-udev package contains udev rules for Logitech receivers. It allows Solaar to access these devices.

If updating the firmware stopped the mouse working completely, I don't think it's anything to do with this package - rather it's a problem with the firmware upgrade, which I think is handled by the fwupd package.
Comment 2 Paul Eggert 2017-07-20 18:39:56 UTC 
(In reply to Richard Fearn from comment #1)

Thanks for fixing the package - this stuff is all unfamiliar ground to me.

In further news, unplugging the wireless mouse's tiny USB dongle, and plugging it back in again, makes the wireless mouse start working again. However, the software updates GUI for a while listed no updates, and now is listing the Logitech Unifying Receiver update again. For now I'm going to assume that the update hasn't entirely taken and that I'm vulnerable to the security problem, so I will revert to the wired mouse.

I can test the wireless mouse if you give me further instructions. Although I expect someone around here has a device that would let me exploit the security hole if it's still present (for testing purposes only of course), I'd rather not have to do that....
Comment 3 Richard Fearn 2017-07-21 13:13:55 UTC 
> In further news, unplugging the wireless mouse's tiny USB dongle, and
> plugging it back in again, makes the wireless mouse start working again.

I read this recently:

  https://blogs.gnome.org/hughsie/2017/05/22/updating-logitech-hardware-on-linux/

  ..which talks about how fwupd controls the receiver in order to update the firmware on it. My guess is that fwupd is putting it into a different state so that it can update the firmware, but that the update is then not working. While in this state, the receiver doesn't function normally. But when you unplug/replug it, the receiver starts up normally again, and you can use the mouse.

> However, the software updates GUI for a while listed no updates, and now is
> listing the Logitech Unifying Receiver update again. For now I'm going to
> assume that the update hasn't entirely taken

Sounds exactly like the update hasn't worked.

I only saw this bug because you originally filed it against unifying-receiver-udev, but I'm no expert on fwupd. We should probably wait for Richard Hughes to respond, as he *is* the fwupd expert.
Comment 4 Richard Hughes 2017-07-21 15:08:03 UTC 
Does "fwupdmgr get-updates" list anything for the device?
Comment 5 Richard Hughes 2017-07-21 15:22:08 UTC 
Also, are you perhaps hitting https://github.com/hughsie/fwupd/issues/155 too?
Comment 6 Paul Eggert 2017-08-01 16:01:17 UTC 
(In reply to Richard Hughes from comment #4)
> Does "fwupdmgr get-updates" list anything for the device?

That shell command outputs the following:

Unifying Receiver has firmware updates:
ID:                      com.logitech.Unifying.RQR12.firmware
GUID:                    77d843f7-682c-57e8-8e29-584f5b4f52a1
GUID:                    9d131a0c-a606-580f-8eda-80587250b8d6
Update Version:          RQR12.07_B0029
Update Remote ID:        lvfs
Update Checksum:         SHA1(d0d33e760ab6eeed6f11b9f9bd7e83820b29e970)
Update Location:         https://secure-lvfs.rhcloud.com/downloads/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cab
Update Description:      This release addresses an unencrypted keystroke injection issue known as Bastille security issue #11. The vulnerability is complex to replicate and would require a hacker to be physically close to a target.
Comment 7 Paul Eggert 2017-08-01 16:05:57 UTC 
(In reply to Richard Hughes from comment #5)
> Also, are you perhaps hitting https://github.com/hughsie/fwupd/issues/155
> too?

That looks plausible. Is there something simple that I could run, to check? (I won't have physical access to the machine until tomorrow.)
Comment 8 Richard Hughes 2017-08-19 12:49:46 UTC 
What's the number laser-printed on the USB plug? It starts with U00xxxxx -- thanks.
Comment 9 J. Alexander Jacocks 2017-11-06 21:23:31 UTC 
Not sure what happened to Paul, but I have the same issue on my Logitech Pico receiver (that you have mentioned in https://github.com/hughsie/fwupd/issues/169).  My receiver has the following etched on it:

FCC ID: JNZCU0012
IC: 4418A-CU0012

I'm also running Fedora 26, on my laptop, and have F27-beta on my desktop.  I've been holding off updating the firmware, using the desktop, to monitor for the fix on F26.

Is there anything else that I can get you, information-wise?
Comment 10 Fedora End Of Life 2018-05-03 07:54:26 UTC 
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 11 Paul Eggert 2018-05-03 22:07:07 UTC 
I no longer use that serial mouse (I lost it when I moved offices; sorry) and so I do not know whether the problem still exists in Fedora 28.
Comment 12 Toby Drake 2018-05-04 01:44:35 UTC 
This issue was present in Fedora 26.

I don't see the same issue in Fedora 28.
Comment 13 Herbert Carl Meyer 2018-05-05 17:48:17 UTC 
I have this issue in F28. I have apparently broken two receivers, they no longer function on F28 or other systems. I have a logitech mouse and a trackball that use this.

If there is a resolution, I will purchase another receiver to test it.
Comment 14 Paul Eggert 2018-05-05 18:14:09 UTC 
(In reply to Herbert Carl Meyer from comment #13)
> I have this issue in F28.

OK, updating the bug report's Fedora version number to F28.
Comment 15 Richard Hughes 2018-09-10 19:33:11 UTC 
> I have apparently broken two receivers

Can you try with 1.1.2? That should recover the devices from the bootloader state.
Comment 16 Herbert Carl Meyer 2018-09-10 20:20:36 UTC 
I have to find the old receivers, I have packed up to move. I have a new receiver, that is functioning well. When I find the old ones, I will report.
Comment 17 Fedora Update System 2018-12-30 15:56:25 UTC 
fwupd-1.2.2-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-862c9c5502
Comment 18 Fedora Update System 2018-12-31 04:57:00 UTC 
fwupd-1.2.2-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-862c9c5502
Comment 19 Fedora Update System 2019-01-04 13:09:09 UTC 
fwupd-1.2.3-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a7990b5eee
Comment 20 Fedora Update System 2019-01-05 18:51:50 UTC 
fwupd-1.2.3-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a7990b5eee
Comment 21 Fedora Update System 2019-01-08 02:40:53 UTC 
fwupd-1.2.3-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.