mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #785] "SHIFT-clears-CAPS-LOCK" option makes shift break on clients #619
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#619
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 @richwalker on GitHub (Jul 8, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/785
Operating Systems
Server: Debian 10
Linux tc 5.5.0-0.bpo.2-amd64 #1 SMP Debian 5.5.17-1~bpo10+1 (2020-04-23) x86_64 GNU/Linux
Client: Debian 10
Linux tc 5.5.0-0.bpo.2-amd64 #1 SMP Debian 5.5.17-1~bpo10+1 (2020-04-23) x86_64 GNU/Linux
Barrier Version
2.3.2 updated to master @ 20200704
Steps to reproduce bug
In KDE System settings of the Server, Input Devices -> Keyboard Hardware -> Enable Miscellaneous Compatibility Options, enable "Shift cancels Caps Lock"
On the client, type letters without and with SHIFT. After the first SHIFT, only letters typed with SHIFT held down work.
Other info
When did the problem start to occur? Always happened
Is there a way to work around it? Yes, two ways:
Move pointer off client and back again and it reverts to traditional behaviour.
Press both shift keys once and it clears the problem
Don't enable "SHIFT clears CAPS LOCK" and it goes away.
Does this bug prevent you from using Barrier entirely? No but it's a pain
Log files attached show it happening.. tc is the client, t560 is the server
barrier.t560.log.gz
barrier.tc.log.gz
@github-actions[bot] commented on GitHub (Sep 18, 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):
Let's not close valid bug reports.