mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #599] Simultaenous client & server being dead #471
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#471
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 @verhimanshu on GitHub (Mar 26, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/599
Operating Systems
Server: Windows 10 Version 1809
Client: macOS 10.14.6
Barrier Version
2.3.2
Steps to reproduce bug
Client log will show - Server is dead
I have Firewall shutoff for the Windows as it was initially causing issues in connection.
While running on Mac I get following error even after connection is made:
2020-03-25 21:57:33.822 barrierc[33620:5128047] pid(33620)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!@github-actions[bot] commented on GitHub (Sep 26, 2020):
This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.
@p12tic commented on GitHub (Jan 10, 2021):
The
2020-03-25 21:57:33.822 barrierc[33620:5128047] pid(33620)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!message has been fixed in #653.This bug report contains too little information about what could have been the cause of the crash, so please try newest Barrier and file an issue if it's still crashing.