Barrier: “stopped client” when interacting with UAC and lock screens

Created on 10 Mar 2019  Â·  7Comments  Â·  Source: debauchee/barrier

Operating Systems

Server: NixOS 19.03pre170287.19eedaf867d

Client: Windows 1809 (17763.348)

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

  1. run something that needs UAC and notice cursor snap back to the server
  2. click yes on the UAC prompt and notice cursor snap back to the server
  3. lock the screen on the client and notice cursor snap back to the server
  4. click to pull up the cover screen and notice cursor snap back to the server
  5. click sign in on the lock screen and notice cursor snap back to the server

Other info

  • bug doesn’t prevent me from using Barrier entirely
  • bug can be worked around by waiting a few seconds and returning the cursor

Info-level server log (UAC)

[2019-03-11T02:36:19] INFO: switch from "uranus" to "redmond" at 0,411
[2019-03-11T02:36:19] INFO: leaving screen
[2019-03-11T02:36:48] NOTE: client "redmond" has disconnected
[2019-03-11T02:36:48] INFO: jump from "redmond" to "uranus" at 683,384
[2019-03-11T02:36:48] INFO: entering screen
[2019-03-11T02:36:51] NOTE: accepted client connection
[2019-03-11T02:36:51] NOTE: client "redmond" has connected
[2019-03-11T02:36:52] INFO: switch from "uranus" to "redmond" at 0,905
[2019-03-11T02:36:52] INFO: leaving screen
[2019-03-11T02:36:54] NOTE: client "redmond" has disconnected
[2019-03-11T02:36:54] INFO: jump from "redmond" to "uranus" at 683,384
[2019-03-11T02:36:54] INFO: entering screen
[2019-03-11T02:36:57] NOTE: accepted client connection
[2019-03-11T02:36:57] NOTE: client "redmond" has connected
[2019-03-11T02:36:58] INFO: switch from "uranus" to "redmond" at 0,658
[2019-03-11T02:36:58] INFO: leaving screen

Info-level client log (UAC)

[2019-03-11T02:36:48] INFO: leaving screen
[2019-03-11T02:36:48] NOTE: stopped client
[2019-03-11T02:36:49] WARNING: detected application not running, pid=9140
[2019-03-11T02:36:50] INFO: backing off, wait=2s, failures=1
[2019-03-11T02:36:52] INFO: starting new process as privileged user
[2019-03-11T02:36:52] INFO: drag and drop enabled
[
2019-03-11T02:3
6:52
]
 ERROR: 
f
ailed t
o
 get desktop

path,

no drop 
t
arget 
avai
l
able,

error=2
[2019-03-11T02:36:52] NOTE: started client
[2019-03-11T02:36:52] NOTE: connecting to 'uranus.home.daz.cat': 172.19.128.33:24800
[2019-03-11T02:36:52] INFO: server status: active
[2019-03-11T02:36:52] NOTE: connected to server
[2019-03-11T02:36:53] INFO: entering screen
[2019-03-11T02:36:53] INFO: clipboard was updated
[2019-03-11T02:36:53] INFO: clipboard was updated
[2019-03-11T02:36:54] INFO: leaving screen
[2019-03-11T02:36:54] NOTE: stopped client
[2019-03-11T02:36:55] WARNING: detected application not running, pid=7076
[2019-03-11T02:36:56] INFO: backing off, wait=2s, failures=1
[2019-03-11T02:36:58] INFO: starting new process as privileged user
[2019-03-11T02:36:58] INFO: drag and drop enabled
[
2019-03-11T02:36
:58] ERROR: failed to get desktop path
,
 no dr
o
p target available, error=2
[2019-03-11T02:36:58] NOTE: started client
[2019-03-11T02:36:58] NOTE: connecting to 'uranus.home.daz.cat': 172.19.128.33:24800
[2019-03-11T02:36:58] INFO: server status: active
[2019-03-11T02:36:58] NOTE: connected to server
[2019-03-11T02:36:58] INFO: entering screen
[2019-03-11T02:36:58] INFO: clipboard was updated
[2019-03-11T02:36:58] INFO: clipboard was updated

Info-level server log (lock screen)

[2019-03-11T02:37:16] NOTE: client "redmond" has disconnected
[2019-03-11T02:37:16] INFO: jump from "redmond" to "uranus" at 683,384
[2019-03-11T02:37:16] INFO: entering screen
[2019-03-11T02:37:20] NOTE: accepted client connection
[2019-03-11T02:37:20] NOTE: client "redmond" has connected
[2019-03-11T02:37:20] INFO: switch from "uranus" to "redmond" at 0,611
[2019-03-11T02:37:20] INFO: leaving screen
[2019-03-11T02:37:21] NOTE: client "redmond" has disconnected
[2019-03-11T02:37:21] INFO: jump from "redmond" to "uranus" at 683,384
[2019-03-11T02:37:21] INFO: entering screen
[2019-03-11T02:37:25] NOTE: accepted client connection
[2019-03-11T02:37:25] NOTE: client "redmond" has connected
[2019-03-11T02:37:25] INFO: switch from "uranus" to "redmond" at 0,805
[2019-03-11T02:37:25] INFO: leaving screen
[2019-03-11T02:37:25] INFO: switch from "redmond" to "uranus" at 1349,503
[2019-03-11T02:37:25] INFO: entering screen
[2019-03-11T02:37:25] INFO: switch from "uranus" to "redmond" at 0,791
[2019-03-11T02:37:25] INFO: leaving screen
[2019-03-11T02:37:30] NOTE: client "redmond" has disconnected
[2019-03-11T02:37:30] INFO: jump from "redmond" to "uranus" at 683,384
[2019-03-11T02:37:30] INFO: entering screen
[2019-03-11T02:37:34] NOTE: accepted client connection
[2019-03-11T02:37:34] NOTE: client "redmond" has connected
[2019-03-11T02:37:35] INFO: switch from "uranus" to "redmond" at 0,857
[2019-03-11T02:37:35] INFO: leaving screen

Info-level client log (lock screen)

[2019-03-11T02:37:16] INFO: leaving screen
[2019-03-11T02:37:16] NOTE: stopped client
[2019-03-11T02:37:17] WARNING: detected application not running, pid=6396
[2019-03-11T02:37:18] INFO: backing off, wait=2s, failures=1
[2019-03-11T02:37:20] INFO: starting new process as privileged user
[2019-03-11T02:37:20] INFO: drag and drop enabled
[
2019-03-11T02:37:20] 
ER
R
OR: fai
led to get desktop path, no drop target available, error=2
[2019-03-11T02:37:20] NOTE: started client
[2019-03-11T02:37:20] NOTE: connecting to 'uranus.home.daz.cat': 172.19.128.33:24800
[2019-03-11T02:37:20] INFO: server status: active
[
2019-03-11T02:37:20] W
ARNING: failed to open clipboard: 5
[
2019-03-11T0
2
:37:20
] WARNING: failed to 
op
e
n clipboa
r
d: 5
[2019-03-11T02:37:20] NOTE: connected to server
[2019-03-11T02:37:20] INFO: entering screen
[
2019-03-11T02:37:20]
 WARNI
NG: fa
i
led to open clipboard: 5
[2019-03-11T02:37:20] INFO: clipboard was updated
[
201
9
-03-1
1
T02:37:20]
 WARNI
N
G: f
a
iled to open

clipboard: 5
[2019-03-11T02:37:20] INFO: clipboard was updated
[2019-03-11T02:37:22] INFO: leaving screen
[2019-03-11T02:37:22] NOTE: stopped client
[2019-03-11T02:37:22] WARNING: detected application not running, pid=8576
[2019-03-11T02:37:23] INFO: backing off, wait=2s, failures=1
[2019-03-11T02:37:25] INFO: starting new process as privileged user
[2019-03-11T02:37:25] INFO: drag and drop enabled
[
2019-03-11T02:
3
7:25] 
E
RROR: 
f
ailed to get

desktop path, 
n
o drop target available, 
error=2
[2019-03-11T02:37:25] NOTE: started client
[2019-03-11T02:37:25] NOTE: connecting to 'uranus.home.daz.cat': 172.19.128.33:24800
[2019-03-11T02:37:25] INFO: server status: active
[2019-03-11T02:37:25] NOTE: connected to server
[2019-03-11T02:37:25] INFO: entering screen
[2019-03-11T02:37:25] INFO: clipboard was updated
[2019-03-11T02:37:25] INFO: clipboard was updated
[2019-03-11T02:37:25] INFO: leaving screen
[2019-03-11T02:37:26] INFO: entering screen
[2019-03-11T02:37:31] INFO: leaving screen
[2019-03-11T02:37:31] NOTE: stopped client
[2019-03-11T02:37:31] WARNING: detected application not running, pid=6452
[2019-03-11T02:37:32] INFO: backing off, wait=2s, failures=1
[2019-03-11T02:37:34] INFO: starting new process as privileged user
[2019-03-11T02:37:34] INFO: drag and drop enabled
[
2019-03-11T02:37
:
3
4] ER
R
OR: failed to get desktop path, no drop target
 available
,
 error=2
[2019-03-11T02:37:34] NOTE: started client
[2019-03-11T02:37:34] NOTE: connecting to 'uranus.home.daz.cat': 172.19.128.33:24800
[2019-03-11T02:37:34] INFO: server status: active
[2019-03-11T02:37:34] NOTE: connected to server
[2019-03-11T02:37:35] INFO: entering screen
[2019-03-11T02:37:35] INFO: clipboard was updated
[2019-03-11T02:37:35] INFO: clipboard was updated
bug windows

Most helpful comment

Yeah client option, worked for me!

Elevate

All 7 comments

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.

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.

What's the barrier.conf version of that?

I don't think you can do this with barrier.conf. The Elevate setting is stored in the registry.

Oh, a client option?

Yeah client option, worked for me!

Elevate

The issue still persists today, another 'fix' is setting UAC to not dim the desktop:

image

Was this page helpful?
0 / 5 - 0 ratings