You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
long long long time paid synergy user who converted over to barrier back in October (my rhlaptop client below did not like synergy and barrier was in the default epel repo)
I have several linux computers connected using barrier -
my server is running on Fedora 35, along with a F35 client (barrier-2.4.0-1.fc35.x86_64)
and then another client (my work laptop) running RHEL8 (barrier-2.4.0-1.el8.x86_64)
I connect the work laptop every morning at 8AM and then later in the afternoon - all of the sudden I will lose the RHEL client. Some times 4PM, sometimes sooner, today it happened at 2:30PM I am not certain enough to say that this happens every day but at least 4 out of 5 days a week.
When this happens, the server barrier.log show s"rhlaptop is dead"
[2022-04-01T14:30:24] DEBUG: close clipboard 1
[2022-04-01T14:30:24] INFO: switch from "optimus" to "hive" at 1919,558
[2022-04-01T14:30:24] INFO: leaving screen [2022-04-01T14:30:24] INFO: switch from "hive" to "rhlaptop" at 4409,588
[2022-04-01T14:30:30] NOTE: client "rhlaptop" is dead
[2022-04-01T14:30:30] DEBUG: Closing socket: 7779CAB0
[2022-04-01T14:30:30] INFO: jump from "rhlaptop" to "optimus" at 960,540
[2022-04-01T14:30:30] INFO: entering screen
[2022-04-01T14:30:33] DEBUG: Opening new socket: 7793A480 [2022-04-01T14:30:33] NOTE: accepted client connection
[2022-04-01T14:30:33] DEBUG: received client "rhlaptop" info shape=0,0 4480x1080 at 2356,785
[2022-04-01T14:30:33] NOTE: client "rhlaptop" has connected
I have a wireless USB keyboard connected so I can ALT+F2 and start barrier to resume the connection.
Later at the end of the day when shutting down the RHEL8 laptop, it reports "barrier is not responding" - which I believe to be the original instance.
I can see 2 instances each of barrier and barrierc
0 R glaw 4629 4132 3 80 0 - 606919 - 08:03 tty2 00:15:23 barrier
0 S glaw 5091 4629 0 80 0 - 47436 - 08:03 tty2 00:02:07 /usr/bin/barrierc -f --no-tray --debug DEBUG2 --name rhlaptop --disable-crypto --log /home/glaw/barrier.log [192.168.29.8]:24800
0 S glaw 64330 4334 0 80 0 - 325653 x64_sy 14:30 tty2 00:00:01 barrier
0 S glaw 64341 64330 0 80 0 - 45520 - 14:30 tty2 00:00:00 /usr/bin/barrierc -f --no-tray --debug DEBUG2 --name rhlaptop --disable-crypto --log /home/glaw/barrier.log [192.168.29.8]:24800
The RHEL8 laptop is the only client I have this issue with. The 2 fedora machines (client + server) stay connected reliably. I can reboot one or the other or both and they always come back up and reconnect.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
long long long time paid synergy user who converted over to barrier back in October (my rhlaptop client below did not like synergy and barrier was in the default epel repo)
I have several linux computers connected using barrier -
my server is running on Fedora 35, along with a F35 client (barrier-2.4.0-1.fc35.x86_64)
and then another client (my work laptop) running RHEL8 (barrier-2.4.0-1.el8.x86_64)
I connect the work laptop every morning at 8AM and then later in the afternoon - all of the sudden I will lose the RHEL client. Some times 4PM, sometimes sooner, today it happened at 2:30PM I am not certain enough to say that this happens every day but at least 4 out of 5 days a week.
When this happens, the server barrier.log show s"rhlaptop is dead"
[2022-04-01T14:30:24] DEBUG: close clipboard 1
[2022-04-01T14:30:24] INFO: switch from "optimus" to "hive" at 1919,558
[2022-04-01T14:30:24] INFO: leaving screen
[2022-04-01T14:30:24] INFO: switch from "hive" to "rhlaptop" at 4409,588
[2022-04-01T14:30:30] NOTE: client "rhlaptop" is dead
[2022-04-01T14:30:30] DEBUG: Closing socket: 7779CAB0
[2022-04-01T14:30:30] INFO: jump from "rhlaptop" to "optimus" at 960,540
[2022-04-01T14:30:30] INFO: entering screen
[2022-04-01T14:30:33] DEBUG: Opening new socket: 7793A480
[2022-04-01T14:30:33] NOTE: accepted client connection
[2022-04-01T14:30:33] DEBUG: received client "rhlaptop" info shape=0,0 4480x1080 at 2356,785
[2022-04-01T14:30:33] NOTE: client "rhlaptop" has connected
I have a wireless USB keyboard connected so I can ALT+F2 and start barrier to resume the connection.
Later at the end of the day when shutting down the RHEL8 laptop, it reports "barrier is not responding" - which I believe to be the original instance.
I can see 2 instances each of barrier and barrierc
0 R glaw 4629 4132 3 80 0 - 606919 - 08:03 tty2 00:15:23 barrier
0 S glaw 5091 4629 0 80 0 - 47436 - 08:03 tty2 00:02:07 /usr/bin/barrierc -f --no-tray --debug DEBUG2 --name rhlaptop --disable-crypto --log /home/glaw/barrier.log [192.168.29.8]:24800
0 S glaw 64330 4334 0 80 0 - 325653 x64_sy 14:30 tty2 00:00:01 barrier
0 S glaw 64341 64330 0 80 0 - 45520 - 14:30 tty2 00:00:00 /usr/bin/barrierc -f --no-tray --debug DEBUG2 --name rhlaptop --disable-crypto --log /home/glaw/barrier.log [192.168.29.8]:24800
The RHEL8 laptop is the only client I have this issue with. The 2 fedora machines (client + server) stay connected reliably. I can reboot one or the other or both and they always come back up and reconnect.
Beta Was this translation helpful? Give feedback.
All reactions