mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1688] Mays keys not working with a Kubuntu server and a Windows 10 client with Spanish keyboard #1243
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#1243
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 @jaimedicer on GitHub (Jun 8, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1688
What happened?
I can't write capital letters from a Kubuntu server in a Windows 10 client. It's just like I wasn't pressing the Mays key. It's very annoying because I still can write in capital letters using the Bloq Mays key but there's no way to type some symbols like $ (Mays-4 in my Spanish keyboard). AltGr wasn't working either, but I found a workaround. Not with the Mays keys problem. Sorry for my English.
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
I installed Barrier from the repository in Kubuntu 22.04 (not snap), and from the assets in github in Windows 10. Same version in both machines.
What OSes are you seeing the problem on? (Check all that apply)
Linux, Windows
What OS versions are you using?
Kubuntu 22.04 (server) and Windows 10 (client)
Relevant log output
No response
Any other information
I added shift = altgr and altgr = shift at the end of the screen section in the barrier.conf file to workaround the same problem with AltGr, which is working well right now.