debauchee / barrier

Open-source KVM software
Other
27.61k stars 1.52k forks source link

Windows Lock screen shortcut (win+L) causing program to stop working #677

Open ThinkSalat opened 4 years ago

ThinkSalat commented 4 years ago

Operating Systems

Server: Windows 10 v1909

Client: MacOS Catalina

So, the win+L shortcut is registering on my server even though I'm locked into my Mac. I use that shortcut to open the address bar in chrome, and it seems like every time I do it, it locks my server, which causes the keyboard shortcut to switch back to my mac to stop working.

I use only one monitor and switch between them, so this makes me go back to my windows machine, unlock it, and then hit the keyboard shortcut again. It's a really annoying experience.

Are there any workarounds to this? Or any options that can prevent it?

hiuwo commented 4 years ago

Yes there is a workaround way on your windows to just disable the workstation lock keyboard shortcut:

(source: https://www.itprotoday.com/windows-78/how-can-i-disable-lock-workstation-when-i-press-ctrl-alt-del)

  1. Start the registry editor (regedit.exe)
  2. Move to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System.
  3. From the Edit menu select New - DWORD value.
  4. Enter a name of DisableLockWorkstation and press Enter.
  5. Double click on the new value and set to 1. Click OK.
  6. Close the registry editor.

Hope this helps

PS I hope the above will suffice. There is also away to prevent certain keys to be sent to server/client but I don't remember where it is set, might be command line or some obscure settings, or you could try Configure Server > Hotkeys (tab) New (Keystroke), OK> New (Actions), OK > Press and relase a hotkey > check Only on these screens and choose which screen.

github-actions[bot] commented 4 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.

p12tic commented 3 years ago

I think this should be at least documented. Until this is not done, this bug should stay up.