This wiki was updated to MediaWiki 1.37. If you notice any issues, please report them to admin[at]

openSUSE:Bug Squashing KDE

Jump to: navigation, search

KDE Bug Squashing Session

The purpose of the bug squashing session is to reduce the number of KDE bugreports at the openSUSE bugzilla. There are currently several hundred bugreports assigned to KDE maintainers, which is a number that's beyond the capabilities of the current KDE team to fix (or even handle without wasting a large portion of time on it). A considerable number of the bugreports belong to the upstream bugzilla according to the upstream vs downstream reporting guidelines, additionally many bugreports may no longer be valid for various reasons (fixed meanwhile by upstream, no response from the reported when asked for additional data, etc.).

How to take a part

Please read guidelines for KDE bugreports screening before starting.

If you want to help, openSUSE:Bug_Squashing_KDE_bugreports has a list of assigned bugreport number ranges. Select one that is free (has ? next to it) and edit the page to assign it to yourself (add your name). When you are done with the range, mark it as DONE. If there are any bugreports that you cannot handle for any reason (you don't have the necessary hardware, you don't understand the problem, etc.), add the bugreport number to the appropriate list in openSUSE:Bug_Squashing_KDE_bugreports.

If you have any questions, feel free to ask in #opensuse-kde.


There are several criteria which may be used for checking validity of a bugreport:

Checking old NEEDINFO bugreports

Check the query for bugreports which are in NEEDINFO state for longer than a month. See section 'Incomplete bugreports' in openSUSE:Bug Screening KDE#Reviewing_bugreports. Note that if the NEEDINFO is for another developer (somebody with Novell email), they should be pinged instead.

Checking whether old bugreports are still valid

Here are queries for openSUSE 11.3, openSUSE 11.4 and openSUSE 12.1. They should be checked with a recent KDE version (from openSUSE 12.2 or the KDE:Release:49, KDE:Distro:Factory or KDE:Unstable:SC repositories) whether they are still valid. If they are not valid, they should be closed as RESOLVED FIXED with a comment stating that in the new KDE version the bug is not present, unless the bug is very serious, enough to justify an online update (add such bugreports to the 'Online update' section in openSUSE:Bug_Squashing_KDE_bugreports). If the bugreport is still valid, add a comment stating in which KDE version the bug still exists and make sure the bug status is ASSIGNED.

Upstreaming bugreports

Note: This task requires already a little experience with handling of bugreports and is not recommended for new community members. Please try with other tasks first.

Here is a query for all P4 bugreports and P3 bugreports. According to the guidelines, all bugreport with priority less than P2 that are not openSUSE-specific should be forwarded to upstream bugzilla and closed as RESOLVED UPSTREAM.

If the bugreport itself already references an upstream bugreport, just close it. If not, you can try to find a possible upstream bugreport yourself. You can use the advanced search there (if there is a backtrace, search for the topmost entry in it, if there is an error message, try searching for the fixed part of it, etc.). This link will give you a table with all bugreports for components of a specific bugzilla product (edit the 'kwin' in the URL to whichever part of KDE is responsible). If you find such bugreport, add it to the URL field in bugzilla and close the bugreport with a comment like:

'Please next time report non-major problems that are not openSUSE-specific directly upstream at ('

If you cannot find an upstream bugreport for the issue, you can either report it yourself (in which case then close the original one as said above), or you can ask the reporter to do that themselves (e.g. if they may be asked for further information by upstream developers, or even just if forwarding them upstream is too time consuming). Close then the bugreport with a comment like:

Please report your problem directly upstream at ('.

See also section 'Decide whether the bugreport should be kept in Novell bugzilla or upstreamed' in openSUSE:Bug Screening KDE.

Handling P5 bugreports

Note: This task requires already a little experience with handling of bugreports and is not recommended for new community members. Please try with other tasks first.

This query lists all P5 bugreports that haven't been processed yet. They should be handled according to the guidelines at openSUSE:Bug Screening KDE.