[GH-ISSUE #98] Mouse clicking doesn't work on clients when OBS is open #75

New issue

Closed

opened 2026-05-05 04:57:24 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 04:57:24 -06:00

Owner

Originally created by @arctair on GitHub (Jul 19, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/98

Hey y'all. I'm having a problem using Barrier and OBS (Open Broadcaster Software) at the same time on my server. When I launch OBS on the server, mouse clicks stop registering on my clients via Barrier. When I close OBS, mouse clicks start working again. Has anyone seen this behavior with other software? What could be going on here?

Operating Systems

Server: Microsoft Windows 10 (Version 1803, OS Build 17134.165)

Client: Ubuntu 18.04 (two of these clients)

Barrier Version

2.1.0

Steps to reproduce bug

Open OBS (21.1.2)

Other info

When did the problem start to occur? When I started using OBS
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? No

Originally created by @arctair on GitHub (Jul 19, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/98 Hey y'all. I'm having a problem using Barrier and OBS (Open Broadcaster Software) at the same time on my server. When I launch OBS on the server, mouse clicks stop registering on my clients via Barrier. When I close OBS, mouse clicks start working again. Has anyone seen this behavior with other software? What could be going on here? ### Operating Systems ### Server: Microsoft Windows 10 (Version 1803, OS Build 17134.165) Client: Ubuntu 18.04 (two of these clients) ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### Open OBS (21.1.2) ### Other info ### * When did the problem start to occur? When I started using OBS * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? No

gitea-mirror

2026-05-05 04:57:24 -06:00

closed this issue
added the
wontfix
label

gitea-mirror commented

2026-05-05 04:57:33 -06:00

Author

Owner

@walker0643 commented on GitHub (Jul 26, 2018):

Hi @arctair - Conflicts between Barrier and other software are usually the result of one of two things:

Both programs are attempting to do the same thing (system-wide capture and control of keybaord/mouse events)
The other program is running elevated.

Either way it amounts to being that the two programs are mutually exclusive. There are exceptions, of course, for little workarounds - eg. clicking off the elevated window before switching screens allows Barrier to see the input again - but for the most part it's just best not to use both apps simultaneously.

If you do find a workaround please feel free to ammed this issue with the details. For now I'm not seeing this as a bug because Barrier has to do what it has to do. Thanks!

@walker0643 commented on GitHub (Jul 26, 2018): Hi @arctair - Conflicts between Barrier and other software are usually the result of one of two things: 1. Both programs are attempting to do the same thing (system-wide capture and control of keybaord/mouse events) 2. The other program is running elevated. Either way it amounts to being that the two programs are mutually exclusive. There are exceptions, of course, for little workarounds - eg. clicking off the elevated window before switching screens allows Barrier to see the input again - but for the most part it's just best not to use both apps simultaneously. If you do find a workaround please feel free to ammed this issue with the details. For now I'm not seeing this as a bug because Barrier has to do what it has to do. Thanks!

gitea-mirror referenced this issue

2026-05-05 07:56:13 -06:00

[PR #75] [MERGED] pull in recent patches from master #1553

gitea-mirror referenced this issue

2026-05-05 07:56:24 -06:00

[PR #86] [MERGED] Merge pkgconfig branch into master #1560