github-starred/barrier

Fork 0

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

[GH-ISSUE #639] unknown screen name in switchToScreen #507

New issue

Open

opened 2026-05-05 06:33:21 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 06:33:21 -06:00

Owner

Originally created by @acbramley on GitHub (Apr 27, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/639

Operating Systems

Server: macOS High Sierra 10.13.6

Client: Windows 10

Barrier Version

2.3.2

Steps to reproduce bug

This bug started happening after I installed barrier on a new PC on the network. Barrier was working fine on an old PC I was using before this one. Both are Windows 10.

Start Barrier
Barrier remains in status "Barrier is starting"
Even when clicking Stop, Barrier returns to "Barrier is starting"
When viewing the logs, the following error message is printed over and over again with different hashes of configuration (e.g Barrier.foo, Barrier.bar, etc)
When doing an ls /private/var/folders/pp/7cs5_vt50mx23195kzf2rf440000gn/T/Barrier.* there are over 200 files and it seems that these keep being created as long as Barrier is open.

[2020-04-27T11:27:19] INFO: starting server
[2020-04-27T11:27:19] INFO: config file: /private/var/folders/pp/7cs5_vt50mx23195kzf2rf440000gn/T/Barrier.QksmVr
[2020-04-27T11:27:19] INFO: log level: INFO
[2020-04-27T11:27:19] INFO: drag and drop enabled
[2020-04-27T11:27:19] ERROR: cannot read configuration "/private/var/folders/pp/7cs5_vt50mx23195kzf2rf440000gn/T/Barrier.IjeFxC": read error: line 27: unknown screen name in switchToScreen
barriers: no configuration available
[2020-04-27T11:27:19] ERROR: process exited with error code: 4
[2020-04-27T11:27:19] INFO: detected process not running, auto restarting

Other info

Only when switching to a new PC
I have tried uninstalling and reinstalling Barrier on the Mac, rebooting, etc but nothing fixes it.
When configuring the server interactively the only screen shown is the mac in the middle, all other squares are empty.

Originally created by @acbramley on GitHub (Apr 27, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/639 ### Operating Systems ### Server: macOS High Sierra 10.13.6 Client: Windows 10 ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### This bug started happening after I installed barrier on a new PC on the network. Barrier was working fine on an old PC I was using before this one. Both are Windows 10. 1. Start Barrier 1. Barrier remains in status "Barrier is starting" 1. Even when clicking Stop, Barrier returns to "Barrier is starting" 1. When viewing the logs, the following error message is printed over and over again with different hashes of configuration (e.g Barrier.foo, Barrier.bar, etc) 1. When doing an `ls /private/var/folders/pp/7cs5_vt50mx23195kzf2rf440000gn/T/Barrier.*` there are over 200 files and it seems that these keep being created as long as Barrier is open. ``` [2020-04-27T11:27:19] INFO: starting server [2020-04-27T11:27:19] INFO: config file: /private/var/folders/pp/7cs5_vt50mx23195kzf2rf440000gn/T/Barrier.QksmVr [2020-04-27T11:27:19] INFO: log level: INFO [2020-04-27T11:27:19] INFO: drag and drop enabled [2020-04-27T11:27:19] ERROR: cannot read configuration "/private/var/folders/pp/7cs5_vt50mx23195kzf2rf440000gn/T/Barrier.IjeFxC": read error: line 27: unknown screen name in switchToScreen barriers: no configuration available [2020-04-27T11:27:19] ERROR: process exited with error code: 4 [2020-04-27T11:27:19] INFO: detected process not running, auto restarting ``` ### Other info ### * Only when switching to a new PC * I have tried uninstalling and reinstalling Barrier on the Mac, rebooting, etc but nothing fixes it. * When configuring the server interactively the only screen shown is the mac in the middle, all other squares are empty.

gitea-mirror added the

bug

label 2026-05-05 06:33:21 -06:00

gitea-mirror commented

2026-05-05 06:33:25 -06:00

Author

Owner

@acbramley commented on GitHub (Apr 27, 2020):

I've just found what was causing this, my hotkeys configuration still had the name of the old PC in a switchToScreen action. This could hopefully be made to fail gracefully instead of breaking the whole application.

@acbramley commented on GitHub (Apr 27, 2020): I've just found what was causing this, my hotkeys configuration still had the name of the old PC in a switchToScreen action. This could hopefully be made to fail gracefully instead of breaking the whole application.

gitea-mirror commented

2026-05-05 06:33:27 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 23, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:33:30 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

This is a valid bug, let's not close it.

@p12tic commented on GitHub (Jan 10, 2021): This is a valid bug, let's not close it.

gitea-mirror commented

2026-05-05 06:33:33 -06:00

Author

Owner

@Tony2 commented on GitHub (Apr 26, 2021):

thank you so much for posting the cause; this was driving me mad since Barrier keeps crashing and re-starting because of this. Removing the hotkeys did it for me.

@Tony2 commented on GitHub (Apr 26, 2021): thank you so much for posting the cause; this was driving me mad since Barrier keeps crashing and re-starting because of this. Removing the hotkeys did it for me.

gitea-mirror commented

2026-05-05 06:33:35 -06:00

Author

Owner

@AymenFJA commented on GitHub (Mar 14, 2022):

The solution for me was:

press configure server
Delete the existing screen(s)
Setup your screens and make sure that you entered the correct names for your host (in my case it was windows 11) and the client (MacBook air)
Stop barrier and rerun it again on both client and server and you should be fine to go.

@AymenFJA commented on GitHub (Mar 14, 2022): The solution for me was: 1. press `configure server` 2. Delete the existing screen(s) 3. Setup your screens and make sure that you entered the correct names for your host (in my case it was windows 11) and the client (MacBook air) 4. Stop barrier and rerun it again on both client and server and you should be fine to go.

gitea-mirror commented

2026-05-05 06:33:37 -06:00

Author

Owner

@leomeza1 commented on GitHub (Jan 1, 2023):

Similar issue happened with me. Installed version 2.4.0 on a new Laptop (Linux), configured it as a client. My desktop (Linux) is the Barrier server. I changed the name of my server using the "Configure Server.." dialog. When starting the server, Barrier is failing/restarting repeatedly on "unknown screen name ..." as described above. I found that I needed to go into Barrier>Server Settings on the server/desktop and also change the screen name there. Maybe the log could have been more verbose and explicitly stated "Unknown screen name found in Barrier>Server Settings" or something to that effect.

@leomeza1 commented on GitHub (Jan 1, 2023): Similar issue happened with me. Installed version 2.4.0 on a new Laptop (Linux), configured it as a client. My desktop (Linux) is the Barrier server. I changed the name of my server using the "Configure Server.." dialog. When starting the server, Barrier is failing/restarting repeatedly on "unknown screen name ..." as described above. I found that I needed to go into Barrier>Server Settings on the server/desktop and also change the screen name there. Maybe the log could have been more verbose and explicitly stated "Unknown screen name found in Barrier>Server Settings" or something to that effect.

gitea-mirror referenced this issue

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

[PR #507] [MERGED] Man page: fix incorrect name of user conf file in barriers.1 #1647