[GH-ISSUE #1252] Optional screen-locking with Scroll Lock on #1009

Open
opened 2026-05-05 07:22:49 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @TheYuriG on GitHub (Aug 19, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1252

Hello!

This is not exactly an issue, but a request.
I have one of those LED colored keyboards and the lights turn on and off based off scroll lock status. This means i need to consistently turn off the lights to change the screens and then turn on again to be able to see my keyboard (First World problems, i know).

Could it possibly be added an option in the settings to ignore Scroll Lock status and always change screens? Make it enabled by default and disabled by choice, so it's not a breaking change or different behavior for new users.

Thank you!

Originally created by @TheYuriG on GitHub (Aug 19, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1252 Hello! This is not exactly an issue, but a request. I have one of those LED colored keyboards and the lights turn on and off based off scroll lock status. This means i need to consistently turn off the lights to change the screens and then turn on again to be able to see my keyboard (First World problems, i know). Could it possibly be added an option in the settings to ignore Scroll Lock status and always change screens? Make it enabled by default and disabled by choice, so it's not a breaking change or different behavior for new users. Thank you!
Author
Owner

@echo-bravo-yahoo commented on GitHub (Dec 1, 2021):

+1. I'm having some issues because none of my keyboards (a laptop keyboard, a standard 60%, and a custom QMK with an unusual layout) have a scroll lock button, and for some reason, my Ubuntu laptop appears to have scroll lock ON. I'll probably dig another keyboard out of the closet to turn scroll lock off on my laptop and hope it's not set ON during boot, but it's a big hassle (and not a feature I plan on using, since it's bound to a key I can't press!..)

EDIT: Turns out the issue was (some combination of) Barrier@2.4.0 on Windows 10 as a server, and/or Wayland on the Linux box. I've changed both (downgrade to 2.3.3 on server, disabled Wayland on the laptop), and it's now working.

<!-- gh-comment-id:983836224 --> @echo-bravo-yahoo commented on GitHub (Dec 1, 2021): +1. I'm having some issues because none of my keyboards (a laptop keyboard, a standard 60%, and a custom QMK with an unusual layout) have a scroll lock button, and for some reason, my Ubuntu laptop appears to have scroll lock ON. I'll probably dig another keyboard out of the closet to turn scroll lock off on my laptop and hope it's not set ON during boot, but it's a big hassle (and not a feature I plan on using, since it's bound to a key I can't press!..) EDIT: Turns out the issue was (some combination of) Barrier@2.4.0 on Windows 10 as a server, _and/or_ Wayland on the Linux box. I've changed both (downgrade to 2.3.3 on server, disabled Wayland on the laptop), and it's now working.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1009
No description provided.