problem to register hotkey

zurekl commented 4 years ago

Operating Systems

Server: Arch Linux 5.6.14 64-bit Client: Windows 8.1 Pro version 6.3 64-bit

Barrier Version

Barrier 2.3.2

Steps to reproduce bug

Configure hotkey either in config file or with Configure Server button:

section: options
    keystroke(F12) = keystroke(F12,arch)
end

Start server.

Log:

[2020-06-10T18:03:30] INFO: starting server
[2020-06-10T18:03:30] INFO: config file: /home/***/configuration.sgc
[2020-06-10T18:03:30] INFO: log level: INFO
[2020-06-10T18:03:30] INFO: log file: /var/log/barrier.log
[2020-06-10T18:03:30] WARNING: failed to register hotkey F12 (id=efc9 mask=0000)
[2020-06-10T18:03:30] NOTE: started server (IPv4/IPv6), waiting for clients

Hotkey feature does not work at all.

github-actions[bot] commented 3 years ago

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.

curiousercreative commented 3 years ago

I was having the same problem with hotkey registration failures. In my case, I was able to isolate the problem to another application that was registering the same hotkey (Autokey in my case). Fortunately for me, Autokey didn't have any trouble registering its hotkey after Barrier, so I just modified my startup commands to delay Autokey a few seconds and allow Barrier to register first.

p12tic commented 3 years ago

Let's not close valid bug reports for no reason.

p12tic commented 3 years ago

@curiousercreative Could you point to autokey website so that there's no ambiguity over which program you were using? I think we could learn from Autokey and if we setup hotkeys in the same way then this bug would be fixed.

curiousercreative commented 3 years ago

https://github.com/autokey/autokey

debauchee / barrier