Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a commented workaround section in the user Hyprland bindings config to support Logitech MX Keys “special” keys that report as regular key events rather than XF86 keysyms, so users can uncomment bindings to restore expected behavior.
Changes:
- Add a “Logitech MX Keys” commented section in
~/.config/hypr/bindings.conf. - Provide example bindings for Print Screen, Dictation, and Emoji keys.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Instead of just reporting the XF86 convention Logitech had the great idea to report those keys as you can see in the binding.conf. I would prefer a firmware update to fix this but we will never have it.
I also don't want to install Solaar and don't think it should be installed by default just because a Logitech USB Receiver was detected during OS install.
The mute button is not there because it does not report anything at all that I could catch using wev.
Adding this commented so when Logitech MX Keys users went looking for why the PrintScn button is not working they will find this and then they can uncomment.