mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #563] typing in search text fields of windows taskbar and settings app : not working #441
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#441
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 @imaderaya on GitHub (Feb 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/563
Operating Systems
Server: MacOS Mojave 10.14.6
Client: Windows 10 1909
Barrier Version
2.3.2
Steps to reproduce bug
I can not type or paste ( from server to client) in the search text fields of windows taskbar and settings app. I can do so elsewhere.
the log message is :
barriers[2227:57709] pid(2227)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!@imaderaya commented on GitHub (Feb 24, 2020):
It's seems to be a windows 10 issue, nothing to do with barrier.
@shymega commented on GitHub (Feb 24, 2020):
Hm, what in particular was the Windows 10 issue? Just so we have this as a reference, should others have a similar issue.
@imaderaya commented on GitHub (Feb 24, 2020):
I think an update from Microsoft broke something since my windows has the latest updates. I will investigate more when I can.
the workaround I found is to run : C:\Windows\system32\ctfmon.exe, and add an entry in logon local group policy, so that it runs on logon.