Name Description Open Bugs Total Bugs
accessibility Keyword for bugs related to accessibility issues. Search 7433
AffectsTails Affects Tails OS. It is a live operating system which uses GNOME and Tor. You can use Tails on almost any computer from a DVD, USB stick, or SD card. It aims at preserving your privacy and anonymity see https://tails.boum.org/. Search 26
API Application Programming Interface Search 1223
bisected (For a regression) the specific git commit introducing the regression has been identified Search 26
BLOCKED_BY_FREEZE This keyword should be used for bugs for which action can be taken by the maintainer once feature/ui/string/code freeze is removed, but for which all further actions are blocked until that time. Should be reserved for bugs containing a patch. Search 79
build problems with the build system, source tree, broken testsuite, non-UI regressions, etc (except packages) Search 1198
documentation This bug (or something in it) needs documenting. Search 1991
HELPWANTED Usually added by component owner: help appreciated here! Search 269
HIG Bug reporting an area where an application does not follow the HIG. Search 629
I18N This is a internationalization issue. This includes strings not marked for translation, things not working in certain locales etc. This is the infrastructure to support L10N. Search 4292
keynav Bug involves keyboard navigation (or lack of). Search 994
L10N This is a localisation issue. Including errors in localisations, typos, etc. Adding locations and weather stations is one example. Correcting date and time formats is another. Search 3774
memory Keyword for bugs filed about various problems regarding memory, from excessive memory use due to poor design to usage of uninitialized values identified by a tool such as valgrind. Search 838
mozilla Caused by mozilla bugs Search 187
multihead Keyword for bugs related to multihead displays. Search 139
newcomers 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 4788
perf A keyword for performance bugs. Search 895
portability This keyword indicates that this bug is related to the porting of GNOME to non-linux platforms, to compilers other than gcc, or to architectures other than ia32. Search 629
pref The bug is a request for adding a configuration option. Search 109
printing printing / preview issues Search 355
probabledup This bug is probably a duplicate of another bug but the person who added the designation doesn't have the time to search for the original offhand. Search 1827
qa bugs that describe testing that needs to be done (and can be done by non-programmers) Search 253
regression_test_needed The QA team or an engineer feels that this bug should be added to the regression test suite for this product. Search 21
relnote Keyword to indicate that this bug should be discussed in the release notes for the next release. Search 30
security To be added for potentially security-related bugs. Search 366
sm keyword for session management bugs in an application. Search 41
STACKTRACE Decent stack trace (i.e. one with debugging symbols) attached to bug Search 3981
string This bug involves string changes in the user interface [but not including documentation] Search 3109
sun_patches A keyword for Wipro and other sun employees who have attached patches that they wish to be tracked in a distinct manner. Search 260
ui-review Indicates a bug filed as part of the ui-review. Should be used only by the ui-review team. Search 1836
usability This keyword describes a usability/user interface change where the correct behavior is not necessarily obvious and input from the usability team is desired. Search 13310