[GH-ISSUE #56] altgr modifier #46

New issue

Closed

opened 2026-05-05 04:51:43 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 04:51:43 -06:00

Owner

Originally created by @alvarogf97 on GitHub (Jun 2, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/56

Operating Systems

Server: Ubuntu 18.04

Client: Windows 10

altgr modifier do not work on client side

Originally created by @alvarogf97 on GitHub (Jun 2, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/56 ### Operating Systems ### Server: Ubuntu 18.04 Client: Windows 10 altgr modifier do not work on client side

gitea-mirror closed this issue

2026-05-05 04:51:44 -06:00

gitea-mirror commented

2026-05-05 04:51:46 -06:00

Author

Owner

@dayne commented on GitHub (Jun 7, 2018):

Googled this a bit and turns out synergy-core has this as a well known issue in the fork for barrier and also on their current Synergy 2 (as of June, 2018). So a known issue in this code for over 4 years or more.

Wiki entry: https://github.com/symless/synergy-core/wiki/AltGr

Consolidated issue: https://github.com/symless/synergy-core/issues/4411

More advanced than the altgr = shift fix to consider looking at:

Report back if you find success.

@dayne commented on GitHub (Jun 7, 2018): Googled this a bit and turns out synergy-core has this as a well known issue in the fork for barrier and also on their current Synergy 2 (as of June, 2018). So a known issue in this code for over 4 years or more. Wiki entry: https://github.com/symless/synergy-core/wiki/AltGr Consolidated issue: https://github.com/symless/synergy-core/issues/4411 More advanced than the `altgr = shift` fix to consider looking at: * https://github.com/symless/synergy-core/issues/4411#issuecomment-328800097 * https://github.com/symless/synergy-core/issues/5723#issuecomment-261753394 Report back if you find success.

gitea-mirror commented

2026-05-05 04:51:50 -06:00

Author

Owner

@alvarogf97 commented on GitHub (Jun 20, 2018):

it's work thanks, but I have the following warnings:
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi
I do not want to open GUI, but how can I init barrier with conf file from shell?

@alvarogf97 commented on GitHub (Jun 20, 2018): it's work thanks, but I have the following warnings: *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi I do not want to open GUI, but how can I init barrier with conf file from shell?

gitea-mirror commented

2026-05-05 04:51:52 -06:00

Author

Owner

@alvarogf97 commented on GitHub (Jun 20, 2018):

./barriers --debug DEBUG --no-daemon --enable-crypto --no-tray

it's work. Thanks

@alvarogf97 commented on GitHub (Jun 20, 2018): ./barriers --debug DEBUG --no-daemon --enable-crypto --no-tray it's work. Thanks

gitea-mirror referenced this issue

2026-05-05 07:56:04 -06:00

[PR #48] [MERGED] use pkg-config for finding avahi include dir #1548