github-starred/barrier

Fork 0

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

[GH-ISSUE #1793] Unicode Default Screen Names #1318

New issue

Open

opened 2026-05-05 07:43:40 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:43:40 -06:00

Owner

Originally created by @rioki on GitHub (Oct 4, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1793

What happened?

My machine is named märs (instead of mars) because a while back I was testing crashes in an application that could not handle Unicode characters in hostnames. When installing barrier the screen name defaults to the hostname; including all non ACSII characters.

On the server side barrier strips all non ACSII characters from the screen name making it impossible to configure the screen.

I did resolve the issue by renaming the screen (after a short while of frustration); so for me the issue is resolved.

For consistency's sake it would be advisable to run the default screen name creation through the same sanitization code to remain consistent; as long as barrier does not support Unicode screen names.

Version

v2.4.0

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?

Version 10.0.19043 Build 19043

Relevant log output

No response

Any other information

No response

Originally created by @rioki on GitHub (Oct 4, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1793 ### What happened? My machine is named märs (instead of mars) because a while back I was testing crashes in an application that could not handle Unicode characters in hostnames. When installing barrier the screen name defaults to the hostname; including all non ACSII characters. On the server side barrier strips all non ACSII characters from the screen name making it impossible to configure the screen. I did resolve the issue by renaming the screen (after a short while of frustration); so for me the issue is resolved. For consistency's sake it would be advisable to run the default screen name creation through the same sanitization code to remain consistent; as long as barrier does not support Unicode screen names. ### Version v2.4.0 ### 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? Version 10.0.19043 Build 19043 ### Relevant log output _No response_ ### Any other information _No response_

No labels

Rows
Columns