Hyprland Bug Report and Contribution Request

[tahabouassida82-beep]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

Hyprland Bug Report and Contribution Request

Hello,

My name is SMTB. I am a Computer Science student and I have been using Hyprland for about 12 days.

During my testing, I discovered an issue related to keyboard layouts. When using a non-US keyboard layout (for example, French - FR), workspace keybindings do not work correctly. After extensive debugging, I found that the problem appears to be related to keybindings constructed with:

mainMod .. "+" .. key

Under certain keyboard layouts, the expected workspace switching behavior fails.

I spent approximately 7 days investigating this issue because at first I believed the problem was in my own configuration. After testing multiple configurations and comparing behavior across keyboard layouts, I concluded that the issue is likely related to how key names are interpreted when building bindings dynamically.

I am willing to continue investigating and potentially provide a fix if the developers are interested. Since I am studying Computer Science, I would also like to contribute to the project and help identify similar issues in the future.

In only 12 days of using Hyprland, I have already encountered and documented several problems and would be happy to assist with testing and debugging.

Additionally, if possible, I would appreciate receiving a contributor or tester role/rank on the Discord server under the username "smtb" as recognition for the time spent investigating this issue and my willingness to help improve the project.

Thank you for your time and for the amazing work on Hyprland.

Best regards,

SMTB
Computer Science Student

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[RAAJK20Pro]

If you've identified a reproducible issue, it would help to provide:

• The exact keyboard layout affected
• A minimal config that reproduces the problem
• Expected vs actual behavior
• Hyprland version and system information
• Relevant logs or debug output

Maintainers are more likely to investigate when a bug can be reproduced easily. If you already have a potential fix, opening a pull request is usually the best way to contribute.

[v-coder247]

Hi @tahabouassida82-beep,

Thanks for being a part of the GitHub Community!

If you're looking for help, you might want to try asking for help somewhere that focuses on this specific topic. It's possible that another GitHub user might have run into this same issue and can help, but the GitHub Community Discussions focuses primarily on topics related to GitHub itself or collaboration on project development and ideas. We want to make sure you’re getting the best support you can, but this space may not be the right place for this particular topic.

Best of luck!