mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #175] Server quits #140
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#140
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Other info
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
@naras1mha commented on GitHub (Nov 14, 2018):
The linux pre-compiled version works perfectly though.
And, thanks for making this!
@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
@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?
@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.
@lindgrenj6 commented on GitHub (Nov 16, 2018):
Confirming - Same error. Running KDE 5.13.5 on Fedora 29.
Debug log when running barriers:
@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
for linux I built from git using the example in the wiki
@Jieiku commented on GitHub (Nov 21, 2018):
I got farther with going to a slightly older commit:
now I am trying to debug my connection problem which is likely unrelated:
so since I am no longer getting the segmentation fault, the issue is likely from one of the commits on Nov 12, 2018
@mokibit commented on GitHub (Nov 21, 2018):
Sorry for the crash, it looks like to be caused by my latest changes. Fixed in #180.