[GH-ISSUE #175] Server quits #140

Closed
opened 2026-05-05 05:22:00 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @naras1mha on GitHub (Nov 14, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/175

Operating Systems

Server: openSuse Tumbleweed

Client: Windows 10

2.2.0 (latest as of 14th Nov, 2018)

Steps to reproduce bug

  1. Compiled the latest version of barrier on openSuse Tumbleweed
  2. When the server is started, it keeps quitting with an error code 11

Other info

  • Does this bug prevent you from using Barrier entirely? Yes

Server Log

[2018-11-14T15:46:10] INFO: starting server
[2018-11-14T15:46:10] INFO: config file: /tmp/Barrier.cKWgbS
[2018-11-14T15:46:10] INFO: log level: INFO
[2018-11-14T15:46:10] ERROR: process exited with error code: 11
[2018-11-14T15:46:10] INFO: detected process not running, auto restarting

[2018-11-14T15:46:11] INFO: starting server
[2018-11-14T15:46:11] INFO: config file: /tmp/Barrier.UCChxJ
[2018-11-14T15:46:11] INFO: log level: INFO
[2018-11-14T15:46:12] ERROR: process exited with error code: 11
[2018-11-14T15:46:12] INFO: detected process not running, auto restarting

Originally created by @naras1mha on GitHub (Nov 14, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/175 ### Operating Systems ### Server: openSuse Tumbleweed Client: Windows 10 2.2.0 (latest as of 14th Nov, 2018) ### Steps to reproduce bug ### 1. Compiled the latest version of barrier on openSuse Tumbleweed 2. When the server is started, it keeps quitting with an error code 11 ### Other info ### * Does this bug prevent you from using Barrier entirely? Yes **Server Log** [2018-11-14T15:46:10] INFO: starting server [2018-11-14T15:46:10] INFO: config file: /tmp/Barrier.cKWgbS [2018-11-14T15:46:10] INFO: log level: INFO [2018-11-14T15:46:10] ERROR: process exited with error code: 11 [2018-11-14T15:46:10] INFO: detected process not running, auto restarting [2018-11-14T15:46:11] INFO: starting server [2018-11-14T15:46:11] INFO: config file: /tmp/Barrier.UCChxJ [2018-11-14T15:46:11] INFO: log level: INFO [2018-11-14T15:46:12] ERROR: process exited with error code: 11 [2018-11-14T15:46:12] INFO: detected process not running, auto restarting
gitea-mirror 2026-05-05 05:22:00 -06:00
  • closed this issue
  • added the
    bug
    linux
    labels
Author
Owner

@naras1mha commented on GitHub (Nov 14, 2018):

The linux pre-compiled version works perfectly though.

And, thanks for making this!

<!-- gh-comment-id:438570601 --> @naras1mha commented on GitHub (Nov 14, 2018): The linux pre-compiled version works perfectly though. And, thanks for making this!
Author
Owner

@naras1mha commented on GitHub (Nov 14, 2018):

Sorry for spamming, did not realize there are different levels of logging.
Here's an excerpt of the log with debug2 when running the compiled version:

[2018-11-14T16:02:48] DEBUG1: logging to file (/home/narasimha/apps/barrier/barrier.log) enabled
/home/narasimha/apps/barrier/src/lib/barrier/App.cpp,146
[2018-11-14T16:02:48] DEBUG: opening configuration "/tmp/Barrier.mmYAIW"
/home/narasimha/apps/barrier/src/lib/barrier/ServerApp.cpp,221
[2018-11-14T16:02:48] DEBUG: configuration read successfully
/home/narasimha/apps/barrier/src/lib/barrier/ServerApp.cpp,232
[2018-11-14T16:02:48] DEBUG1: starting server
/home/narasimha/apps/barrier/src/lib/barrier/ServerApp.cpp,870
[2018-11-14T16:02:48] DEBUG1: thread 0x00000002 entry
/home/narasimha/apps/barrier/src/lib/mt/Thread.cpp,156
[2018-11-14T16:02:48] DEBUG: XOpenDisplay(":0")
/home/narasimha/apps/barrier/src/lib/platform/XWindowsScreen.cpp,885
[2018-11-14T16:02:48] DEBUG2: can't read property 545 on window 0x0240000d
/home/narasimha/apps/barrier/src/lib/platform/XWindowsUtil.cpp,1378
[2018-11-14T16:02:48] DEBUG2: can't read property 545 on window 0x024000e2
/home/narasimha/apps/barrier/src/lib/platform/XWindowsUtil.cpp,1378
[2018-11-14T16:02:48] DEBUG2: can't read property 545 on window 0x0240004e

<!-- gh-comment-id:438573305 --> @naras1mha commented on GitHub (Nov 14, 2018): Sorry for spamming, did not realize there are different levels of logging. Here's an excerpt of the log with debug2 when running the compiled version: [2018-11-14T16:02:48] DEBUG1: logging to file (/home/narasimha/apps/barrier/barrier.log) enabled /home/narasimha/apps/barrier/src/lib/barrier/App.cpp,146 [2018-11-14T16:02:48] DEBUG: opening configuration "/tmp/Barrier.mmYAIW" /home/narasimha/apps/barrier/src/lib/barrier/ServerApp.cpp,221 [2018-11-14T16:02:48] DEBUG: configuration read successfully /home/narasimha/apps/barrier/src/lib/barrier/ServerApp.cpp,232 [2018-11-14T16:02:48] DEBUG1: starting server /home/narasimha/apps/barrier/src/lib/barrier/ServerApp.cpp,870 [2018-11-14T16:02:48] DEBUG1: thread 0x00000002 entry /home/narasimha/apps/barrier/src/lib/mt/Thread.cpp,156 [2018-11-14T16:02:48] DEBUG: XOpenDisplay(":0") /home/narasimha/apps/barrier/src/lib/platform/XWindowsScreen.cpp,885 [2018-11-14T16:02:48] DEBUG2: can't read property 545 on window 0x0240000d /home/narasimha/apps/barrier/src/lib/platform/XWindowsUtil.cpp,1378 [2018-11-14T16:02:48] DEBUG2: can't read property 545 on window 0x024000e2 /home/narasimha/apps/barrier/src/lib/platform/XWindowsUtil.cpp,1378 [2018-11-14T16:02:48] DEBUG2: can't read property 545 on window 0x0240004e
Author
Owner

@AdrianKoshka commented on GitHub (Nov 15, 2018):

What DE are you using? If it's GNOME/KDE, are you using them on wayland? Also, 2.20 doesn't exist yet, so I assume you're building from master?

<!-- gh-comment-id:438907413 --> @AdrianKoshka commented on GitHub (Nov 15, 2018): What DE are you using? If it's GNOME/KDE, are you using them on wayland? Also, 2.20 doesn't exist yet, so I assume you're building from master?
Author
Owner

@naras1mha commented on GitHub (Nov 15, 2018):

I am using KDE with Plasma, SDDM and X11. No wayland.

Yes, I cloned and compiled the code as it is yesterday when I posted.

<!-- gh-comment-id:438924918 --> @naras1mha commented on GitHub (Nov 15, 2018): I am using KDE with Plasma, SDDM and X11. No wayland. Yes, I cloned and compiled the code as it is yesterday when I posted.
Author
Owner

@lindgrenj6 commented on GitHub (Nov 16, 2018):

Confirming - Same error. Running KDE 5.13.5 on Fedora 29.
Debug log when running barriers:

12:28:05 [scyther] ~ $ barriers -f --debug DEBUG -c .barrier.conf
[2018-11-16T12:28:10] DEBUG: opening configuration ".barrier.conf"
[2018-11-16T12:28:10] DEBUG: configuration read successfully
[2018-11-16T12:28:10] DEBUG: XOpenDisplay(":0")
[2018-11-16T12:28:10] DEBUG: xscreensaver window: 0x00000000
Segmentation fault (core dumped)
<!-- gh-comment-id:439468790 --> @lindgrenj6 commented on GitHub (Nov 16, 2018): Confirming - Same error. Running KDE 5.13.5 on Fedora 29. Debug log when running barriers: ``` 12:28:05 [scyther] ~ $ barriers -f --debug DEBUG -c .barrier.conf [2018-11-16T12:28:10] DEBUG: opening configuration ".barrier.conf" [2018-11-16T12:28:10] DEBUG: configuration read successfully [2018-11-16T12:28:10] DEBUG: XOpenDisplay(":0") [2018-11-16T12:28:10] DEBUG: xscreensaver window: 0x00000000 Segmentation fault (core dumped) ```
Author
Owner

@Jieiku commented on GitHub (Nov 21, 2018):

I just learned of barrier today, was going to use it for my gpu passthrough setup to use my keyboard and mouse on both the host and guest. I started the barriers as server on the windows guest.

On Windows the barrier server seems to be running fine, for the linux barrier client I am trying to run on Ubuntu 18.04 with kde plasma

also confirmed im using x11 and NOT wayland

loginctl
loginctl show-session 1 -p Type

Type=x11

for linux I built from git using the example in the wiki

barrierc -n ubuntu -f --debug DEBUG 192.168.122.219:24800
[2018-11-21T06:37:55] DEBUG: XOpenDisplay(":0")
    /home/batman/barrier/src/lib/platform/XWindowsScreen.cpp,885
[2018-11-21T06:37:55] DEBUG: xscreensaver window: 0x00000000
    /home/batman/barrier/src/lib/platform/XWindowsScreenSaver.cpp,350
Segmentation fault (core dumped)
<!-- gh-comment-id:440685522 --> @Jieiku commented on GitHub (Nov 21, 2018): I just learned of barrier today, was going to use it for my gpu passthrough setup to use my keyboard and mouse on both the host and guest. I started the barriers as server on the windows guest. On Windows the barrier server seems to be running fine, for the linux barrier client I am trying to run on Ubuntu 18.04 with kde plasma also confirmed im using x11 and NOT wayland loginctl loginctl show-session 1 -p Type Type=x11 for linux I built from git using the example in the wiki barrierc -n ubuntu -f --debug DEBUG 192.168.122.219:24800 [2018-11-21T06:37:55] DEBUG: XOpenDisplay(":0") /home/batman/barrier/src/lib/platform/XWindowsScreen.cpp,885 [2018-11-21T06:37:55] DEBUG: xscreensaver window: 0x00000000 /home/batman/barrier/src/lib/platform/XWindowsScreenSaver.cpp,350 Segmentation fault (core dumped)
Author
Owner

@Jieiku commented on GitHub (Nov 21, 2018):

I got farther with going to a slightly older commit:

sudo apt update && sudo apt upgrade
sudo apt install git cmake make xorg-dev g++ libcurl4-openssl-dev libavahi-compat-libdnssd-dev libssl-dev libx11-dev libqt4-dev qtbase5-dev
git clone https://github.com/debauchee/barrier.git
cd barrier
sudo git checkout 65172ebd608e929651544057d942a7cf8d74847c
./clean_build.sh
cd build
sudo make install
barrierc -f --debug DEBUG 192.168.122.219:24800

now I am trying to debug my connection problem which is likely unrelated:

WARNING: failed to connect to server: Timed out

so since I am no longer getting the segmentation fault, the issue is likely from one of the commits on Nov 12, 2018

<!-- gh-comment-id:440698049 --> @Jieiku commented on GitHub (Nov 21, 2018): I got farther with going to a slightly older commit: sudo apt update && sudo apt upgrade sudo apt install git cmake make xorg-dev g++ libcurl4-openssl-dev libavahi-compat-libdnssd-dev libssl-dev libx11-dev libqt4-dev qtbase5-dev git clone https://github.com/debauchee/barrier.git cd barrier sudo git checkout 65172ebd608e929651544057d942a7cf8d74847c ./clean_build.sh cd build sudo make install barrierc -f --debug DEBUG 192.168.122.219:24800 now I am trying to debug my connection problem which is likely unrelated: WARNING: failed to connect to server: Timed out so since I am no longer getting the segmentation fault, the issue is likely from one of the commits on Nov 12, 2018
Author
Owner

@mokibit commented on GitHub (Nov 21, 2018):

Sorry for the crash, it looks like to be caused by my latest changes. Fixed in #180.

<!-- gh-comment-id:440703839 --> @mokibit commented on GitHub (Nov 21, 2018): Sorry for the crash, it looks like to be caused by my latest changes. Fixed in #180.
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#140
No description provided.