[GH-ISSUE #1044] Barrier.exe fails to launch barriers.exe (resulting in IPC failure), launching manually works fine though. #831

New issue

Open

opened 2026-05-05 07:11:47 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:11:47 -06:00

Owner

Originally created by @caitp on GitHub (Jan 29, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1044

The usual "IPC connection error" stuff, e.g.

[2021-01-29T08:49:42] INFO: starting server
[2021-01-29T08:49:42] DEBUG: command: "C:/Program Files/Barrier/barriers.exe" -f --no-tray --debug DEBUG --name PCName --ipc --stop-on-desk-switch --enable-drag-drop --enable-crypto --profile-dir "C:\Users\username\AppData\Local\Barrier" -c "C:/Users/username/AppData/Local/Temp/Barrier.SDNYao" --address :24800
[2021-01-29T08:49:42] INFO: config file: C:/Users/username/AppData/Local/Temp/Barrier.wDbtDE
[2021-01-29T08:49:42] INFO: log level: DEBUG
[2021-01-29T08:49:42] INFO: connecting to service...
[2021-01-29T08:49:46] ERROR: ipc connection error, connection refused
[2021-01-29T08:49:47] INFO: connecting to service...
[2021-01-29T08:49:52] ERROR: ipc connection error, connection refused
[2021-01-29T08:49:53] INFO: connecting to service...
[2021-01-29T08:49:57] ERROR: ipc connection error, connection refused
[2021-01-29T08:49:58] INFO: connecting to service...
[2021-01-29T08:50:02] ERROR: ipc connection error, connection refused
[2021-01-29T08:50:03] INFO: connecting to service...

I believe the barriers.exe process is failing to launch, or exiting due to being unable to find the profile or config file (which are definitely present and readable). Running the command line manually in the command prompt (replacing the executable name with non-unix format, but leaving the rest in Qt's unixy format) gets it working just fine. I think this is related to the way the process is being launched internally by the GUI app, but I haven't looked into it yet.

This problem didn't materialize on a fresh installation, interestingly. After stopping the GUI app, and relaunching it/restarting the server, this issue comes up.

Originally created by @caitp on GitHub (Jan 29, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1044 The usual "IPC connection error" stuff, e.g. ``` [2021-01-29T08:49:42] INFO: starting server [2021-01-29T08:49:42] DEBUG: command: "C:/Program Files/Barrier/barriers.exe" -f --no-tray --debug DEBUG --name PCName --ipc --stop-on-desk-switch --enable-drag-drop --enable-crypto --profile-dir "C:\Users\username\AppData\Local\Barrier" -c "C:/Users/username/AppData/Local/Temp/Barrier.SDNYao" --address :24800 [2021-01-29T08:49:42] INFO: config file: C:/Users/username/AppData/Local/Temp/Barrier.wDbtDE [2021-01-29T08:49:42] INFO: log level: DEBUG [2021-01-29T08:49:42] INFO: connecting to service... [2021-01-29T08:49:46] ERROR: ipc connection error, connection refused [2021-01-29T08:49:47] INFO: connecting to service... [2021-01-29T08:49:52] ERROR: ipc connection error, connection refused [2021-01-29T08:49:53] INFO: connecting to service... [2021-01-29T08:49:57] ERROR: ipc connection error, connection refused [2021-01-29T08:49:58] INFO: connecting to service... [2021-01-29T08:50:02] ERROR: ipc connection error, connection refused [2021-01-29T08:50:03] INFO: connecting to service... ``` I believe the barriers.exe process is failing to launch, or exiting due to being unable to find the profile or config file (which are definitely present and readable). Running the command line manually in the command prompt (replacing the executable name with non-unix format, but leaving the rest in Qt's unixy format) gets it working just fine. I think this is related to the way the process is being launched internally by the GUI app, but I haven't looked into it yet. This problem didn't materialize on a fresh installation, interestingly. After stopping the GUI app, and relaunching it/restarting the server, this issue comes up.

No labels

Rows
Columns