[GH-ISSUE #382] Debian 10 - barrier only works in foreground #301

Open
opened 2026-05-05 05:59:41 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @martinwag on GitHub (Aug 2, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/382

Operating Systems

Server: Windows 10

Client: Debian 10

Barrier Version

2.3 (build from source)

Steps to reproduce bug

Problem occurs on Linux Client

add start script to KDE auto start menu

#!/bin/bash
sleep 10
barrierc  -f --no-tray -d DEBUG2 -l /tmp/barrierc 192.168.2.3 

Other info

  • this worked on debian 9, just updated to debian 10
  • barrierc works when started in foreground
  • also doesn't work when removing "-f" (start as daemon)

log on linux client

barrierc.txt

[2019-08-02T09:44:00] DEBUG1: registered event type connectionFailed as 11
/home/mwagner/workspace/barrier/src/lib/base/EventQueue.cpp,143

relevant log on windows server:

[2019-08-02T09:44:00] DEBUG: Opening new socket: EEB5C1A0
[2019-08-02T09:44:00] DEBUG1: registered event type ClientListenerEvents::accepted as 44
[2019-08-02T09:44:00] DEBUG1: registered event type IStreamEvents::inputShutdown as 45
[2019-08-02T09:44:00] NOTE: accepted client connection
[2019-08-02T09:44:00] DEBUG1: registered event type IStreamEvents::outputError as 46
[2019-08-02T09:44:00] DEBUG1: registered event type IStreamEvents::outputShutdown as 47
[2019-08-02T09:44:00] DEBUG1: saying hello
[2019-08-02T09:44:00] DEBUG2: writef(Barrier%2i%2i)
[2019-08-02T09:44:00] DEBUG2: wrote 11 bytes
[2019-08-02T09:44:00] DEBUG1: registered event type ClientProxyUnknownEvents::success as 48
[2019-08-02T09:44:00] DEBUG1: registered event type ClientProxyUnknownEvents::failure as 49
[2019-08-02T09:44:00] NOTE: new client disconnected

Originally created by @martinwag on GitHub (Aug 2, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/382 ### Operating Systems ### Server: Windows 10 Client: Debian 10 ### Barrier Version ### 2.3 (build from source) ### Steps to reproduce bug ### Problem occurs on Linux Client add start script to KDE auto start menu ``` #!/bin/bash sleep 10 barrierc -f --no-tray -d DEBUG2 -l /tmp/barrierc 192.168.2.3 ``` ### Other info ### - this worked on debian 9, just updated to debian 10 - barrierc works when started in foreground - also doesn't work when removing "-f" (start as daemon) log on linux client [barrierc.txt](https://github.com/debauchee/barrier/files/3460173/barrierc.txt) > [2019-08-02T09:44:00] DEBUG1: registered event type connectionFailed as 11 /home/mwagner/workspace/barrier/src/lib/base/EventQueue.cpp,143 relevant log on windows server: > [2019-08-02T09:44:00] DEBUG: Opening new socket: EEB5C1A0 [2019-08-02T09:44:00] DEBUG1: registered event type ClientListenerEvents::accepted as 44 [2019-08-02T09:44:00] DEBUG1: registered event type IStreamEvents::inputShutdown as 45 [2019-08-02T09:44:00] NOTE: accepted client connection [2019-08-02T09:44:00] DEBUG1: registered event type IStreamEvents::outputError as 46 [2019-08-02T09:44:00] DEBUG1: registered event type IStreamEvents::outputShutdown as 47 [2019-08-02T09:44:00] DEBUG1: saying hello [2019-08-02T09:44:00] DEBUG2: writef(Barrier%2i%2i) [2019-08-02T09:44:00] DEBUG2: wrote 11 bytes [2019-08-02T09:44:00] DEBUG1: registered event type ClientProxyUnknownEvents::success as 48 [2019-08-02T09:44:00] DEBUG1: registered event type ClientProxyUnknownEvents::failure as 49 [2019-08-02T09:44:00] NOTE: new client disconnected
gitea-mirror added the
bug
windows
linux
labels 2026-05-05 05:59:41 -06:00
Author
Owner

@twotic commented on GitHub (Sep 22, 2019):

Same behaviour with barriers
barriers --version
barriers 2.3.1-snapshot
Protocol version 1.6
/ compiled 2019-09-22

<!-- gh-comment-id:533860632 --> @twotic commented on GitHub (Sep 22, 2019): Same behaviour with barriers barriers --version barriers 2.3.1-snapshot Protocol version 1.6 / compiled 2019-09-22
Author
Owner

@truatpasteurdotfr commented on GitHub (Sep 22, 2019):

this works for me --enable-crypto
barriers -f -d INFO --enable-crypto -c barriers

<!-- gh-comment-id:533915433 --> @truatpasteurdotfr commented on GitHub (Sep 22, 2019): this works for me **--enable-crypto** ` barriers -f -d INFO --enable-crypto -c barriers`
Author
Owner

@martinwag commented on GitHub (Sep 23, 2019):

--enable-crypto doesn't change the behaviour for me.

<!-- gh-comment-id:533967954 --> @martinwag commented on GitHub (Sep 23, 2019): --enable-crypto doesn't change the behaviour for me.
Author
Owner

@nareo2 commented on GitHub (Feb 4, 2020):

this open pr works for me #390

<!-- gh-comment-id:581855382 --> @nareo2 commented on GitHub (Feb 4, 2020): this open pr works for me [#390](https://github.com/debauchee/barrier/pull/390)
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

It seems that #390 has fixed this issue. Please reopen if this is not the case. Thanks!

<!-- gh-comment-id:757519220 --> @p12tic commented on GitHub (Jan 10, 2021): It seems that #390 has fixed this issue. Please reopen if this is not the case. Thanks!
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

Ah, the PR is not merged yet :(

<!-- gh-comment-id:757519327 --> @p12tic commented on GitHub (Jan 10, 2021): Ah, the PR is not merged yet :(
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#301
No description provided.