[READ FIRST] Hi there! 👋 See here to learn how to properly start a discussion.

[vaxerski]

Hello there! 👋

Thank you for coming here. I'll try to keep it as short and informative as possible.

With our recent changes to how we handle bugs, feature requests and other, it might be a little confusing on how to actually start a discussion. That's why I'm providing a quick tutorial, so that you can start a discussion that helps us all!

As usual, with all discussions, please search first before you open a new one, whatever you need might already have a discussion!

Before anything

Please read the issue guidelines They are short, trust me! 2 minute read.

Questions

Not a bug report or a feature request, but rather a question? Please ask it on our forum instead.

Bugs

Important

If you found a bug, before you do anything, check your hyprctl version. Does the tag match the latest release here? If not, please update first. If you are up to date with your package manager, you might have to wait for your distro to update Hyprland.

If your tag is up to date, then you have to pick the right category. Here are short explanations for each:

• Config - Bugs relating to the config parsing, keywords, and syntax.
• Crashes - Self-explanatory. If you crash, that's your place.
• DRM - This is for issues relating to very low-level rendering stuff. E.g. monitors not working, wrong resolutions, colorful glitches or artifacts, flashes, etc.
• Input - Bugs relating to input: mice, keyboards, touchpads, etc.
• IPC / Plugins - Bugs relating to Hyprland sockets (IPC) and plugins.
• Layout - Bugs relating to dwindle or master layouts. NOT generic window management.
• Performance - Bugs relating to Hyprland's performance
• Renderer - Bugs relating to Hyprland rendering. Effects, animations, damage tracking (e.g. when parts of windows stay on the screen where they shouldn't and don't get updated)
• Window management - Bugs relating to generic window management, e.g. groups, windowrules, dispatchers etc.
• CMake / Meson / Nix - Bugs relating to the build systems and/or Nix.
• XWayland - Bugs relating to X11 apps or XWayland implementation itself.
• Other - For when the above don't fit your bug.

For your discussion, please use this format:

Open to show

## Hyprland version
<!-- paste your version here -->

## Regression
<!-- Is this a regression? (Meaning something used to work, but now doesn't -->

## Describe the bug
<!-- Describe it here -->

## Reproduction steps
<!-- 1. do this, 2. do that -->

## System info and config
<!-- ATTACH the output of `hyprctl systeminfo -c` here. Save the output to a text file, then drag this file into this input box. -->

Useful things to include in your bug reports:

• Crashing? The crash report
• The log
• Your config: hyprctl systeminfo -c

Always attach them as files, do not paste them!

Feature requests

Have a feature request? Let us know. Find an appropriate category and open a discussion if one doesn't exist already.

Here are small explanations of each:

• Config - For features relating the config keywords, arguments and variables. Not the syntax itself, that goes to hyprlang
• Layouts - For features relating to dwindle or master layouts.
• Protocols / Integrations - For features relating to implementing protocols or third-party integrations
• Renderer - For features regarding effects, animations, etc.
• Window management - For features relating to general window management, e.g. window rules, dispatchers, etc.
• Other - For when the above don't fit your feature request.

For your discussion, please use this format:

Open to show

## Describe the feature
<!-- Describe it here -->

## Why would it be beneficial
<!-- because ... -->

Made a discussion, now what?

If you've made a discussion, great! Thank you. We'll take a look at it. If we don't have anything to add or suggest, we might not say anything.

If we find your discussion complete, important, and understand it, a member of the org will promote it to an issue and link the discussion.

If we don't, you will have to provide more information, or just wait for other people to give a 👍 on your discussion. Once your discussion reaches 5 likes, you can ping a member to take a second look.

Please do not spam our discord or other forums, but rather, when you see someone complain about the exact same problem, give them the link to your discussion!