-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Windows10 client: unable to open trustetedServersFile - Username with space #976
Comments
Would you be willing to test this beta build? If that fixes it, the problem was the nordic character and not the space. |
Pushed a fix for an additional related issue; when enabling the drag-drop functionality it would not find the desktop path where it will drop files for the same reason as the previous fix. Edit: Tracked down another issue, this time in the windows service (deamon) communication. If you want to test your exact case, the beta is here: Edit 2: Aaaaand another issue, this time in the client: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=388&view=artifacts&pathAsName=false&type=publishedArtifacts PS: The issue were non-ascii characters in user name, space did not seem be problematic. |
Hello albertony |
Thank you for your feedback! That error is the same as #974 (comment) (I think that issue and yours are essentially duplicates, and is about non-ascii characters). I have not been able to reproduce that in my test setup, unfortunately, latest beta works with special characters (and space), but will have another look. |
That build works with non-ascii characters and solved my issue - thank you. |
Great!! |
…ixes debauchee#976, fixes debauchee#974, fixes debauchee#444)" This reverts commit 402801e.
This fixes debauchee#976, fixes debauchee#974, fixes debauchee#444.
This fixes debauchee#976, fixes debauchee#974, fixes debauchee#444. On Windows the standard stream open() functions expect bytes encoded in current system encoding, not UTF8. Since we're dealing with UTF8 throughout the application this results in wrong paths being passed and failure to open files. As a solution, we convert the paths to UTF16 via the WCHAR character type and use the special Windows-specific overloads of open() functions.
This fixes debauchee#976, fixes debauchee#974, fixes debauchee#444. On Windows the standard stream open() functions expect bytes encoded in current system encoding, not UTF8. Since we're dealing with UTF8 throughout the application this results in wrong paths being passed and failure to open files. As a solution, we convert the paths to UTF16 via the WCHAR character type and use the special Windows-specific overloads of open() functions.
on a Windows Client i have a space and "ä" in the username.
The File trustedServers.txt is written correctly, fingerprint is ok.
The log on client shows continuously: Unable to open trustetedServersFile: C:\Users\xxx xäx\AppData\Local\Barrier...
someone has similar problems with linux client and chinese symbols i think. New issue do to win client.
Thanks for your help in advance
The text was updated successfully, but these errors were encountered: