debauchee / barrier

Open-source KVM software
Other
27.7k stars 1.52k forks source link

Stuck on "Barrier is starting" #1836

Open Doom972 opened 2 years ago

Doom972 commented 2 years ago

What happened?

Recently, I started getting an issue in which Barrier won't start successfully. When I click on "Start". It stays on "Barrier is starting". If I click on "Stop", it still keeps trying.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Installed using pacman from the official Manjaro repo.

What OSes are you seeing the problem on? (Check all that apply)

Linux

What OS versions are you using?

Manjaro 22.0.0 Sikaris I tried different Linux kernels: 5.10 LTS, 5.15 LTS AND 6.0.8.

Relevant log output

[2022-11-22T00:09:58] INFO: starting server
[2022-11-22T00:09:58] INFO: config file: /tmp/Barrier.SaYXdY
[2022-11-22T00:09:58] INFO: log level: INFO
[2022-11-22T00:09:58] NOTE: clipboard sharing is disabled
/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = unsigned char; _Alloc = std::allocator<unsigned char>; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
[2022-11-22T00:09:58] ERROR: process exited with error code: 6
[2022-11-22T00:09:58] INFO: detected process not running, auto restarting

[2022-11-22T00:09:58] INFO: starting server
[2022-11-22T00:09:58] INFO: config file: /tmp/Barrier.oeuXfn
[2022-11-22T00:09:58] INFO: log level: INFO
[2022-11-22T00:09:58] NOTE: clipboard sharing is disabled
/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = unsigned char; _Alloc = std::allocator<unsigned char>; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
[2022-11-22T00:09:58] ERROR: process exited with error code: 6
[2022-11-22T00:09:58] INFO: detected process not running, auto restarting

[2022-11-22T00:09:59] INFO: starting server
[2022-11-22T00:09:59] INFO: config file: /tmp/Barrier.LXOvaQ
[2022-11-22T00:09:59] INFO: log level: INFO
[2022-11-22T00:09:59] NOTE: clipboard sharing is disabled
/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = unsigned char; _Alloc = std::allocator<unsigned char>; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
[2022-11-22T00:09:59] ERROR: process exited with error code: 6
[2022-11-22T00:09:59] INFO: detected process not running, auto restarting

Any other information

No response

VijayKM01 commented 2 years ago

Have been facing the same issue since two weeks on Arch, ( https://github.com/debauchee/barrier/issues/1829 ). Kindly post any workaround or fix you come across, in this thread.

Doom972 commented 2 years ago

I don't think that it is the same as #1829. The log looks different. It seems to work fine on other Manjaro machines for me.I tried reinstalling Barrier and its dependencies and deleting the configuration file, but I keep getting this issue on this specific machine. Is there anything else that I can do to make a clean install of Barrier?

VijayKM01 commented 2 years ago

The log file I attached in #1829 was actually the debug output, and the program crashes because of the C++ STL error, if I select the Log Level to be Info instead of Debug2, I get the same log output as yours, which is also shown when I click on the (show log) menu item in the GUI.

I had also tried reinstalling the package and all its dependencies, but that didn't fix the issue, initially I was pretty inclined to try the snap or flatpak version to get it running, but have switched to rust desk as a workaround until this issue is fixed.

Have you tried downgrading Barrier to an older version ?

itsmohmans commented 1 year ago

I had the same issue with Barrier 2.3.2 on Linux Mint 20.3 + Barrier 2.4.0 Windows 10. It worked after downgrading windows version to 2.3.2.

y4my4my4m commented 8 months ago

Same here, manjaro I fixed it by manually naming the client's PC in the server config then it accepted the connection.