< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 14:07, 26 November 2010 by Lemma (Talk | contribs)

Jump to: navigation, search

The 4.6-beta1 BugWeek will be from 27.11 till 4.12 :)

Additions to this wikipage welcome :)



Goals of this Week

This bugday tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.


You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.


Some packagers provide LiveCD/DVDs to faciliate testing:


For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:

  • add distribution and link to instructions here


If there are no packages for your distribution, you can always build KDE. kdesrc-build is a nice way to get the newest code and have it compiled for you. Be sure to get the sample rc from trunk

Is it a big bug?

Prioritizing is good. If a major application doesn't work, this should be taken care of.

Keep this page updated!

After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>


Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.

IRC Nickname KDE version used for testing Distribution
Brot 4.6 beta 1 Kubuntu 10.10


Please select a period of bugs from the Division of Labour section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.


  • If a bug's description is somewhat unclear, try to provide a better step-by-step procedure on how to reproduce it. This will make it easier for developers to find and fix the bug.
  • Some bugs will only be reprocudible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
  • Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eye principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
  • Some more information on how to mark bugs can be found on This page.

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal