Confirming that this fixes the conflict bug. Cannot speak to the gnome-keyring issue that the original package update here was for; instructions on testing that would be helpful.
So, FWIW: I have a F31 system where I just applied the Firefox update and didn't apply a bunch of other updates, and I was getting just white pages. Updating everything else (except the kernel, as I didn't reboot) seems to make it work fine. Maybe some missing dep?
@whot Yeah. As soon as you touch it, it jumps to the top left corner, and no manipulation of the pointer causes other movement. However, using the Logitech mouse works fine.
It's reproducable on multiple systems (by plugging in the USB keyboard). On one, I actually had three mice: there's one on the keyboard of the laptop in the docking station plus the external-keyboard mouse plus an additional Logitech mouse I plugged in to debug. Only the USB Keyboard Mouse exhibited the problem. I'll file a bug but it won't be until tomorrow evening as I have a lot of meetings during the day.
Yeah, 1.10.902-1 has the same failure. Note that
evtest seems to show completely reasonable
type 2 (EV_REL), code 1 (REL_Y), value -12 type 2 (EV_REL), code 0 (REL_X), value 1
events, even as the cursor fails to move.
There is currently a released update for docker which relies on a version of atomic-registries newer than the released version of that. (Like, for example this one.) Assuming the functionality checks out (and it looks like it does from comments), please expedite this update.
Confirmed that the reproducer in bug #1440287 no longer hangs on 100 runs. Also, rest of system seems to work.