github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1491] Bug: Barrier's "Open Source KVM" process continues after exiting via taskbar icon #1134

New issue

Open

opened 2026-05-05 07:31:22 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 07:31:22 -06:00

Owner

Originally created by @JaredKreft on GitHub (Dec 31, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1491

What happened?

STR:
Run and set up barrier on two windows computers.
Use taskbar icon to quit on both computers.

Actual result: Barrier is still running using an "Open Source KVM" Process in the background, without an icon or a window. Mouse still moves between computers.

Expected result: Telling it to quit via the taskbar icon kills all of its processes.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

What OSes are you seeing the problem on? (Check all that apply)

Windows

What OS versions are you using?

Win 10

Relevant log output

No response

Any other information

No response

Originally created by @JaredKreft on GitHub (Dec 31, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1491 ### What happened? STR: Run and set up barrier on two windows computers. Use taskbar icon to quit on both computers. Actual result: Barrier is still running using an "Open Source KVM" Process in the background, without an icon or a window. Mouse still moves between computers. Expected result: Telling it to quit via the taskbar icon kills all of its processes. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? Win 10 ### Relevant log output _No response_ ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:31:25 -06:00

Author

Owner

@JaredKreft commented on GitHub (Dec 31, 2021):

Even worse: it starts up silently on a reboot, even though I have "Start Barrier on Startup" unchecked in the settings. AND it isn't listed in the startup items under task manager.

@JaredKreft commented on GitHub (Dec 31, 2021): Even worse: it starts up silently on a reboot, even though I have "Start Barrier on Startup" *unchecked* in the settings. AND it isn't listed in the startup items under task manager.

gitea-mirror commented

2026-05-05 07:31:26 -06:00

Author

Owner

@fecet commented on GitHub (Jun 20, 2022):

Same issue

@fecet commented on GitHub (Jun 20, 2022): Same issue

gitea-mirror commented

2026-05-05 07:31:28 -06:00

Author

Owner

@adam4235 commented on GitHub (Dec 16, 2022):

I'm a new user but I'm wondering if this might be a feature. Upon reflection the checkbox "Start barrier on startup" is ambiguous because there are 2 different executables: barrier, which is the configuration dialog, and barrierd, which is the background process that makes it work. It seems to be the background process that always persists across reboots (at least on Windows). Is the checkbox intended to control whether that background process starts at startup, or whether the dialog appears at startup either as a window or as a system tray icon? If the behaviour is intended, then at the very least the checkbox should be clarified.

@adam4235 commented on GitHub (Dec 16, 2022): I'm a new user but I'm wondering if this might be a feature. Upon reflection the checkbox "Start barrier on startup" is ambiguous because there are 2 different executables: barrier, which is the configuration dialog, and barrierd, which is the background process that makes it work. It seems to be the background process that always persists across reboots (at least on Windows). Is the checkbox intended to control whether that background process starts at startup, or whether the dialog appears at startup either as a window or as a system tray icon? If the behaviour is intended, then at the very least the checkbox should be clarified.

No labels

Rows
Columns