Barrier.exe : no configuration avilable #444
Comments
ghost
closed this as
ghost
pushed a commit
that referenced
this issue
Nov 10, 2021
ghost
pushed a commit
that referenced
this issue
Nov 10, 2021
This fixes #976, fixes #974, fixes #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 issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Os : windows 10
Issues ;
Shortcut is not created on dekstop.
When barriers is launched from folder ,
No configuration available is displayed
Just need a few more details:
Are you building Barrier from Git? If so, please provide the commit hash
you're building form.
Which build number of Windows 10 are you running?
Have you made a configuration yet?
On this date - Wed, Sep 25, 2019 at 11:25:28PM -0700, sohanlal1234 wrote:
--
Sincerely,
Dom Rodriguez (shymega).
I downloaded latest exe file in windows . After installing exe , in Windows 10 shortcut is broken .But when I. Installed old version ( 2 version old) of barrier it worked fine .
Right. The latest release is v2.3.2 - that's the one you've tried, right? And presumably the one that does work is v2.2.0, correct? What happens when you try to install v2.3.1, could you try that for me?
Thanks.
ok @shymega , I am using v2.3.1 on Windows 10 with the same issue
here is the log while it starts as server
it seems it can't find the config file.
screenshot : https://prnt.sc/rz0kxo
so I tried to change the config file location on my desktop , but with no success
I get
Ok, could fix the issue, first of all, my theory is, that barrier can't handle characters like öäü that good, my windows username had one in it. Barrier saves the config into the TEMP directory which is located here: "C:\Users<username>\AppData\Local\Temp". After changing the username and reinstalling barrier (by using IObit Uninstaller to make sure no data from barrier is left) it worked. I can't really tell if that's the issue on your computer but I would give it a try. Also I have to warn you, some Programs wouldn't work that good after that (because they're used to the old path) and also had to be reinstalled.
Also I've read in a issue from synergys that it would be possible to just save the config file out of your User folder, like C:\config.scg. Link to the possible solution
Hey guys, i found a good solution, after having this same problem i went to the above described "Temp" directory and found those files, after that i copied them to the root of my C drive and renamed them to "Barrier.sgc", after that i went to Barrier, changed the option on running server to "use existing configuration", then i pointed to the copied file on C root and now it's working without any problems, so it is very likely that it has to do with word with special characters on the user name, because i also have them on my user and was having the same problem.
Hope it helps someone 👍
I have the same issue but my user name does not contain any special characters. Moving my config file to C:\ did not resolve the issue.
Can't believe this still isn't fixed. Took me half an hour to figure out the issue upon first install. I have the "é" character in my user profile name.
Having to copy the config back and forth from the temp folder is time consuming.
C:\Users\xxxéxxx\barrier.sgc was the default suggested path for the configuration file
Also, windows uses backslash and not forward slash as directory separator character...
I haven't been involved with Barrier for some time now, and I'm rather apathetic towards the project. There's really not many developers now. In fact, when I was involved, it was just me and @p12tic, IIRC. No one else is a member of the debauchee organisation as a developer. So we basically rely on PRs and one organisation developer now that I'm not wanting to be invovled.
The text was updated successfully, but these errors were encountered: