obsproject / obsproject/obs-studio

OBS Flatpack causing issues with some USB devices if they are replugged via hardware KVM

Open
#12,883 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Other

Other OS

Manjaro Linux

OBS Studio Version

32.0.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/BC5MQK9B98m0aKFu

OBS Studio Crash Log URL

No response

Expected Behavior

I expect my mouse and keyboard to continue working when replugged when OBS is running.

Current Behavior

If my mouse is unplugged and replugged while OBS is running the underlying system refuses to recognize it. Rebooting the system will temporarily suppress this behavior, but only for a little while.

This is a massive issue, because swapping to and from my stream machine with a KVM is viewed as unplugging and replugging my mouse. The keyboard is generally unaffected because it is plugged through a HID emulator port, and so the system does not see it fully disappear most of the time. If the keyboard is replugged for any reason the issue will hit it as well.

This behavior only occurs if the device is plugged through the KVM (a tesMART DKS202-M24), and only while OBS is running. Both client systems plugged into the KVM are Manjaro Linux, and both work flawlessly so long as OBS is not running.

Swapping systems with the KVM and physically pulling and reinserting the cable from the port produce the same effect if OBS is running, and once the issue has begun to occur.

Steps to Reproduce
  1. Wait for the issue to begin after a reboot. This may take a few hours or a few days, but it will happen.
  2. Start OBS.
  3. Physically unplug the mouse or KVM swap to a second system
  4. Replug the cable or swap back, the device will not be recognized by the system until OBS is closed and the device is replugged once again.
Anything else we should know?

I would be happy to provide any logs, or run any debug programs needed. This is a very weird issue, and I cannot imagine it would happen to many people. However, there are few things worse than swapping back to my stream machine to ban a bot or make a change to OBS, only to find out that my mouse isn't working.

A reboot does solve the issue for a little while but it does reoccur consistently, which just makes the whole thing weirder.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the OBS log at https://obsproject.com/logs/BC5MQK9B98m0aKFu and reproduce the failure using the tesMART DKS202-M24 KVM on Manjaro Linux. No source file or test is identified, so the first task is to locate the Linux USB/device handling involved while OBS is running. Done means identifying and fixing the cause so mouse and keyboard devices are recognized after KVM swaps or physical replugging.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
desktop-dev, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.