From Peter's description of the problem I guessed that it was wireshark setting promiscuous state on the virtual usbmon interface that caused the keyboard to go back to working state, which I knew should also be possible via tcpdump -i usbmon3 where usbmon3 is the interface that corresponds to the usb device in question.
This works as a short term hack.
sudo modprobe usbmon && sudo tcpdump -i usbmon3
Then you will be able to use the keyboard to ctrl-c out of it. Once the state has been set it appears to be permanent and persistent until next reboot.
From Peter's description of the problem I guessed that it was wireshark setting promiscuous state on the virtual usbmon interface that caused the keyboard to go back to working state, which I knew should also be possible via tcpdump -i usbmon3 where usbmon3 is the interface that corresponds to the usb device in question.
This works as a short term hack.
sudo modprobe usbmon && sudo tcpdump -i usbmon3
Then you will be able to use the keyboard to ctrl-c out of it. Once the state has been set it appears to be permanent and persistent until next reboot.