github-starred/barrier

Fork 0

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

[GH-ISSUE #1525] Resolved: log file keeps appearing in wrong place #1150

New issue

Open

opened 2026-05-05 07:32:13 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

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

Owner

Originally created by @gth on GitHub (Jan 17, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1525

What happened?

Kept on getting a barrier.log logifle appearing on the desktop, despite the barrier GUI indicating it was disabled and set to a different location. Eventually identified two different settings in the registry:

[HKEY_USERS\[long GUID code]\Software\Debauchee\Barrier]
"logLevel"=dword:00000001
"logToFile"="false"
"logFilename"="C:/Program Files/Barrier/log/barrier.log"

[HKEY_LOCAL_MACHINE\SOFTWARE\Barrier]
"LogFilename"="C:/Users/[username]/Desktop/barrier.log"

Not sure how/when the second entry gets created, given the barrier client correctly displays the information in the first branch. I changed the second LogFilename entry to match the first, and while the log file still appears (despite being disabled), at least it no longer appears on the desktop. Issue created to document issue & work-around.

Version

v2.3.3

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

github.

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

Windows

What OS versions are you using?

Windows 7 Professional (yeah, I know - legacy system)

Relevant log output

server status: active
server status: active
[2022-01-18T09:03:42] ERROR: failed to get desktop path, no drop target available, error=2

connected to server

Any other information

No response

Originally created by @gth on GitHub (Jan 17, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1525 ### What happened? Kept on getting a barrier.log logifle appearing on the desktop, despite the barrier GUI indicating it was disabled and set to a different location. Eventually identified two different settings in the registry: ``` [HKEY_USERS\[long GUID code]\Software\Debauchee\Barrier] "logLevel"=dword:00000001 "logToFile"="false" "logFilename"="C:/Program Files/Barrier/log/barrier.log" ``` ``` [HKEY_LOCAL_MACHINE\SOFTWARE\Barrier] "LogFilename"="C:/Users/[username]/Desktop/barrier.log" ``` Not sure how/when the second entry gets created, given the barrier client correctly displays the information in the first branch. I changed the second LogFilename entry to match the first, and while the log file still appears (despite being disabled), at least it no longer appears on the desktop. Issue created to document issue & work-around. ### Version v2.3.3 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? github. ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? Windows 7 Professional (yeah, I know - legacy system) ### Relevant log output ```shell server status: active server status: active [2022-01-18T09:03:42] ERROR: failed to get desktop path, no drop target available, error=2 connected to server ``` ### Any other information _No response_

No labels

Rows
Columns