Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting Hotkeys via GUI creates invalid config file #778

Closed
aoikato opened this issue Jul 4, 2020 · 2 comments
Closed

Setting Hotkeys via GUI creates invalid config file #778

aoikato opened this issue Jul 4, 2020 · 2 comments

Comments

@aoikato
Copy link

aoikato commented Jul 4, 2020

Operating Systems

Server: Arch Linux

Client: Ubuntu 18.04.01 LTS

Barrier Version

2.3.2

Steps to reproduce bug

  1. Open 'Barrier' GUI application.
  2. Select 'Configure interactively' if not, and click 'Configure Server.'
  3. Create a hotkey of 'keystroke(Control+,)' for any action such as 'switchInDirection(up).'
  4. Click 'OK' and 'Start.'
  5. Barrier never starts, and log says 'cannot read configuration.'
  6. After a while, dialog appears and says 'Program can not be started.'

Other info

  • work around:
  1. After the step 6 above, save current nonfunctional configuration as a file by clicking 'Barrier' and 'Save configuration.'
  2. Substitute keystroke(Control+comma) forkeystroke(Control+,) in that file.
  3. Load this file, and <C+,> can be used as a hotkey properly.
@zeorin
Copy link

zeorin commented Sep 17, 2020

Thanks, this really helped me out.
I was trying to bind a key using Super, which it put in the config as Meta. Following your steps, but changing Meta to Super made it work.

@p12tic
Copy link
Member

p12tic commented Jan 10, 2021

Fixed in #916, thanks for reporting the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants