| Name | Description | Open Bugs | Total Bugs |
|---|---|---|---|
| bisected | The bug has been successfully connected to a code commit that introduced the bug (such as with "git bisect"). | Search | 760 |
| bisect_pending | The bug seems likely to benefit from bisecting, (such as easy to reproduce, etc.), but the bisect has not yet been performed. See also the "bisected" keyword. | Search | 64 |
| cleanup0407 | April 2007 bug cleanup. | Search | 14 |
| have-backtrace | bugs that have a useful backtrace | Search | 380 |
| i18n | Xorg Internationalisation issues (i18n) | Search | 128 |
| janitor | Cleanup bugs, usually trivial. | Search | 263 |
| l10n | Xorg/X11 Localisation issues | Search | 138 |
| licence | Files with licence problems (e.g. mixing incompatible licences, missing/non-permissive copyrights, et al) | Search | 24 |
| love | Marking a bug with this keyword means that you're willing to help someone fix the bug, or that it should be fixable by a beginner without any help. This should ONLY be set by a maintainer or people familiar with the code base, and ONLY when it looks like a project suitable for a new developer looking for a task. | Search | 167 |
| movetoxkc | Bugs that should be moved to xkeyboard-config, if still applicable. | Search | 37 |
| NEEDINFO | The bug does not have enough information in order to solve the problem. Please read the comments and add the relevant information required to aid in solving the problem. | Search | 1153 |
| notourbug | It's not really our bug, but we might work around it anyway. | Search | 13 |
| patch | Bugs with a valid patch. | Search | 3284 |
| regression | Xorg bug regressions (issues previously fixed but somehow broken again) | Search | 4714 |
| security | Security-sensitive bugs | Search | 93 |
| want-backtrace | Bugs whose triage could be greatly accelerated with the addition of a backtrace from the crash. | Search | 54 |
| x12 | Bugs that require a protocol version bump. | Search | 5 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.