mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #966] Barrier windows service still running after stop and exit from GUI #777
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#777
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @blamarche on GitHub (Dec 3, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/966
This is a feature request, technically.
There should be an option to have the Windows service be set to manual instead of automatic, and only start when the user starts the barrier client, and stops when the barrier client is closed and stopped.
@yume-chan commented on GitHub (Oct 5, 2021):
I think starting services needs Administrator privilege, so the client will trigger UAC dialogs.
@yume-chan commented on GitHub (Oct 5, 2021):
Also see #346
@yume-chan commented on GitHub (Oct 5, 2021):
The service should be mainly for client mode, to control high-privilege windows (like Task Manager, Login Screens, etc.), so a better UX might be only checking (and starting) service when clicking the "Start" button for client mode.