mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1648] client "XXX" is dead #1217
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#1217
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 @geolaw on GitHub (Apr 19, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1648
What happened?
Originally started this discussion which contains all of my info
https://github.com/debauchee/barrier/discussions/1631
3 linux machines connected - 2 fedora 35 (server "optimus" and client 2 "hive") and one RHEL8 (client 1 "rhlaptop")
server :
[glaw@optimus ~]$ rpm -qa |grep barrier
barrier-2.4.0-1.fc35.x86_64
client 1:
[glaw@optimus ~]$ ssh rhlaptop rpm -qa |grep barrier
barrier-2.4.0-1.el8.x86_64
client 2:
[glaw@optimus ~]$ ssh hive rpm -qa |grep barrier
barrier-2.4.0-1.fc35.x86_64
I will be working along and randomly the barrier connection from the RHEL8 machine will drop
server log :
[2022-04-19T12:08:53] INFO: screen "rhlaptop" updated clipboard 0
[2022-04-19T12:08:53] DEBUG: sending clipboard 0 to "hive"
[2022-04-19T12:08:53] DEBUG: sent clipboard size=48
[2022-04-19T12:08:53] INFO: screen "rhlaptop" updated clipboard 1
[2022-04-19T12:08:53] DEBUG: sending clipboard 1 to "hive"
[2022-04-19T12:08:53] DEBUG: sent clipboard size=139
[2022-04-19T12:08:55] INFO: switch from "hive" to "rhlaptop" at 4437,549
[2022-04-19T12:09:01] INFO: switch from "rhlaptop" to "hive" at 2,717
[2022-04-19T12:09:01] INFO: switch from "hive" to "rhlaptop" at 4478,790
[2022-04-19T12:09:01] INFO: switch from "rhlaptop" to "hive" at 17,798
[2022-04-19T12:09:11] INFO: switch from "hive" to "rhlaptop" at 4440,838
[2022-04-19T12:09:33] NOTE: client "rhlaptop" is dead <<<<<<<<<<<<<<<<<<
[2022-04-19T12:09:33] DEBUG: Closing socket: 020397D0
[2022-04-19T12:09:33] INFO: jump from "rhlaptop" to "optimus" at 960,540
[2022-04-19T12:09:33] INFO: entering screen
[2022-04-19T12:09:34] INFO: switch from "optimus" to "hive" at 1919,1011
[2022-04-19T12:09:34] INFO: leaving screen
[2022-04-19T12:09:35] INFO: switch from "hive" to "optimus" at 1,779
[2022-04-19T12:09:35] INFO: entering screen
[2022-04-19T12:09:35] DEBUG: open clipboard 0
[2022-04-19T12:09:35] DEBUG: empty clipboard 0
[2022-04-19T12:09:35] DEBUG: grabbed clipboard 0
I really can't relate this to any specific keystroke or something I am trying to do on the rhlaptop machine and it happens at various times throughout the day. Sometimes after 6 hours, today after about 4 hours.
The logs have rotated out on the rhlaptop client so I don't have them, but next time I will grab them before I restart
The 2 fedora machines (client/server) stay connected without any problems. I can reboot one or the other (or both) and barrier reconnects. the RHEL8 machine is the only one that has this issue.
Sometimes when the connection drops, a key will appear to get "stuck" - e.g. if I am in hexchat I will get a string of whatever character I was typing when barrier dropped
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
installed from yum - fedora / epel repos
barrier-2.4.0-1.el8.x86_64
barrier-2.4.0-1.fc35.x86_64
What OSes are you seeing the problem on? (Check all that apply)
Linux
What OS versions are you using?
barrier-2.4.0-1.el8.x86_64 (client)
barrier-2.4.0-1.fc35.x86_64 (server)
Relevant log output
Any other information
https://github.com/debauchee/barrier/discussions/1631
@carlosman commented on GitHub (May 27, 2022):
I have the same problem. I have 3 computers:
@MM502 commented on GitHub (Jun 6, 2023):
For me it helped to turn off drag and drop. I am running an older CLI version on an older client Mac alongside the latest release on two W10Pro machines and had forgotten that that I once had enabled it specifically in the Mac's config (
--enable-drag-drop).Once I switched it off everything went back to normal.