Ubuntu 18.04 Update Breaks KVM Wireless Mouse

Bug #1889114 reported by Joe Herko
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly.

I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro.

The KVM (ConnectPro 14+)

    • Has a video cable from each computer to the KVM
    • Has a USB control cable from each computer to the KVM
    • Has a video cable from the KVM to the display
    • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard
    • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector.

The extension cable is used to locate the receiver in proximity to the wireless mouse.

I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated.

KVM Wireless Mouse function matrix (see attached image)

I replaced the mouse battery, so that is not the problem.

I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop.

I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates).

So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch.

    1. Can I provide any additional configuration information, and, if so, what terminal commands should I run?
    2. How do I recover from this problem?
    3. Can I back-out the update? If so, how will this impact future updates?
    4. What else can I try to restore the wireless mouse functionality?

Thank you in advance for your assistance.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 27 14:29:36 2020
InstallationDate: Installed on 2020-03-18 (130 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: joe_admin 7605 F.... pulseaudio
 /dev/snd/controlC1: joe_admin 7605 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-03-18 (134 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IwConfig:
 eno1 no wireless extensions.

 lo no wireless extensions.
MachineType: LENOVO 10ALCTO1WW
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic N/A
 linux-firmware 1.173.19
RfKill:

Tags: bionic
Uname: Linux 5.4.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/24/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: FBKTDBAUS
dmi.board.name: SHARKBAY
dmi.board.vendor: LENOVO
dmi.board.version: NOK
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnLENOVO:bvrFBKTDBAUS:bd12/24/2019:svnLENOVO:pn10ALCTO1WW:pvrThinkCentreM83:rvnLENOVO:rnSHARKBAY:rvrNOK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 10ALCTO1WW
dmi.product.sku: LENOVO_MT_10AL
dmi.product.version: ThinkCentre M83
dmi.sys.vendor: LENOVO

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote :
affects: ubuntu → ubuntu-release-upgrader (Ubuntu)
affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1889114

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : CRDA.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : Lspci.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : Lsusb.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : ProcModules.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : PulseList.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : UdevDb.txt

apport information

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote :

I executed the apport-collect 1889114 command as instructed. It appears that a number of txt files were uploaded.

However, the instructions also said to change the status to "Confirmed". I was not able to change the status. The "status" info pulldown seems to indicate that the "reporter" can not change the status to "Confirmed".

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

What packages got update on July 21st?

Can you please check /var/log/apt/history.log?

Revision history for this message
Joe Herko (joe-ubuntu-fla) wrote :

Sorry for the delay in responding. We were helping a relative pack and move. The history log had already been moved to a .gz file. The file is attached. It covers the dates from 1 Jul to 22 Jul.

Revision history for this message
Ben Bell (bellb300) wrote :

I am encountering this issue with my setup too after updating

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.