mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #264] “stopped client” when interacting with UAC and lock screens #211
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#211
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 @delan on GitHub (Mar 10, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/264
Operating Systems
Server: NixOS 19.03pre170287.19eedaf867d
Client: Windows 1809 (17763.348)
Barrier Version
2.1.0-RELEASE-0b2dfd80
Steps to reproduce bug
Other info
Info-level server log (UAC)
Info-level client log (UAC)
Info-level server log (lock screen)
Info-level client log (lock screen)
@noisyshape commented on GitHub (Apr 9, 2019):
Barrier starts an elevated process to interact with certain UI elements and starts a regular process when it's done. Every time there's a new process, a new session has to be created which takes 2-3 seconds. It gets you coming and going and it's a terrible user experience. The easiest fix would be to run one elevated process. I have no idea how reasonable that would be. The next easiest thing might be to have one session exchanged between processes.
There is a workaround for UAC. You can lower the settings so that notifications don't dim the screen.
@TRowbotham commented on GitHub (May 6, 2019):
I was able to work around this by going to Barrier -> Settings, then changing the Elevate setting to Always on the client. I didn't have to change UAC.
@ar1a commented on GitHub (May 7, 2019):
What's the barrier.conf version of that?
@TRowbotham commented on GitHub (May 7, 2019):
I don't think you can do this with barrier.conf. The Elevate setting is stored in the registry.
@ar1a commented on GitHub (May 7, 2019):
Oh, a client option?
@delan commented on GitHub (May 7, 2019):
Yeah client option, worked for me!
@NotSnowyy commented on GitHub (Aug 25, 2020):
The issue still persists today, another 'fix' is setting UAC to not dim the desktop:
@ghostlitao commented on GitHub (Jul 28, 2021):
Worked for me!
@pv2b commented on GitHub (Dec 30, 2021):
Hi!
This happens for me, also, and Elevate: Always does not work for me.
My setup:
Barrier server: Windows 11 (21H2) running Barrier 2.4.0
Barrier client: Windows 10 (21H1) running Barrier 2.3.4
(I'm running 2.3.4 on the client because of a different bug with multi-screen setups with different scaling not working correctly on 2.4.0.)
The Barrier client is set up as Elevate: Always, but this does not solve the issue. When a UAC dialog pops up on the client, there is a delay of a few seconds where I lose keyboard/mouse control of the client. This also happens on login.
However, the workaround of setting UAC to the setting that doesn't dim the desktop does seem to work around the issue at me, at least for UAC prompts.
Edit: Strange, I was going to edit the post and upload some logs, but now suddenly it's working correctly... so whatever this is, it's intermittent.