< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 01:23, 5 April 2008 by JLP (Talk | contribs)

Jump to: navigation, search



This triage day will run from 0:00 UTC - 23:59 UTC on April 6th 2008. Our target for triage is bugs listed in under the product Konqueror.

The goal of this bug-day is to check for: simple step-by-step instructions, reproducibility, and most of all, come up with test-cases for reproducing the bugs. This will enable the Konqueror developers to deal with bugs more easily, and so have more time left to actually fix them. When you have added either a test-case or step-by-step instructions for the reproduction of a bug, please list it in the appropriate section below, so that a second triager can see if they can get your instructions/test-case to work correctly. This page provides an excellent explanation of how to create a test-case. This page also has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Konqueror doesn't have as many duplicates as some applications, and we don't want to claim things are duplicates when they aren't. So do not look too hard for them, and make sure to double check them with someone else, preferably one of the developers before marking/closing.We especially don't want to create more work for developers!

Be sure to join #kde-bugs on, as this is where the bug-day will be coordinated. (You can even join now!)

You should either be working with Konqueror from KDE 4 (either 4.0.2 or newer is best or SVN trunk) for testing these bugs. In this case, it probably won't matter which one, because KHTML/KJS are aggressively forward-ported and back-ported, and you might find 4.0.x easier to compile.

You may need another browser to test things in.


If you come across a bug with a testcase in the text, put it under the testcase section. If it isn't marked "testcase" in the title, make a note of that. Check that the testcase works! (And doesn't work!)

Most importantly, we need to create testcases. These are time-consuming, but extremely useful and really help out developers. These are especially important if it is a site that is either a non-Western language or a site you need some sort of account for.


If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the bugs awaiting feedback section. Be polite, we want to be nice to our bug reporters!

Is it a big bug?

Prioritizing is good. If a major website doesn't work, that is important. Let's keep track of them.

Version field

Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", it won't show up in developer's searches for 4.0 bugs! Change the version field to match what the other one says, i.e. to match version the bug was first reported in, or mark it below if you don't have bugzilla permissions. Do not update or change the version number (ex. from 3.5.2 to 4.0.2) if it is currently set as a number! Just make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build or which distro the packages come from).

Double Check!

Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.


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.


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:

IRC Nickname KDE version used for testing
Grundleborg svn trunk r790203
Blauzahl dunno
Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup ~~~ to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).

Division of Labour

Please choose a month that is not already taken and then query for all bugs in that month. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.

The bugzilla query to use for this triage day can be found here. Be sure to correct the dates to the month which you will triage before running the query.

Month No of bugs IRC Nickname Status
pre 2003 20 Grundleborg up to bug #40116
2003-01 4
2003-02 6
2003-03 6
2003-04 3
2003-05 3
2003-06 5
2003-07 6
2003-08 5
2003-09 3
2003-10 8
2003-11 12
2003-12 13
2004-01 13 Finex Skipped bug #79369 need more testing
2004-02 10
2004-03 14
2004-04 11
2004-05 14
2004-06 8
2004-07 8
2004-08 11
2004-09 16
2004-10 9
2004-11 12
2004-12 13
2005-01 11
2005-02 16
2005-03 20
2005-04 16
2005-05 24
2005-06 22
2005-07 10
2005-08 10
2005-09 16
2005-10 20
2005-11 16
2005-12 21
2006-01 13
2006-02 13
2006-03 17
2006-04 19
2006-05 20
2006-06 21
2006-07 16
2006-08 18
2006-09 23
2006-10 27
2006-11 25
2006-12 17
2007-01 26
2007-02 26
2007-03 25
2007-04 11
2007-05 20
2007-06 21
2007-07 16
2007-08 12
2007-09 9
2007-10 16
2007-11 21
2007-12 23
2008-01 32
2008-02 28
2008-03 22
2008-04 2

(Total bugs 974)

Bugs needing version field changed

Bugs should be listed here if their version field is invalid and they are still present in KDE 4, so that the version field can be corrected.

Bugs with test-cases Added

Bugs that have had a test case (an example of how to reproduce the bug) added should be entered below.

  • bug #19921 - test case was already there but wasn't marked. Grundleborg
  • bug #32563 - testcase added. Grundleborg
  • bug #79492 - testcase already present. Bug still reproducible Finex
  • bug #79813 - testcase already present. Added on the subject. Bug still reproducible: Saving the file of the testcase will start Kget which save an empty file Finex
  • bug #79813 - testcase already present. Added on the subject. Bug (?) still reproducible. Is it really a bug? It should be checked if a valid email address could contain a "#" char Finex
  • bug #80432 - testcase already present (even on subject). Bug still reproducible. Finex

Bugs with step-by-step instructions

If you have provided step by step instructions on how to reproduce a bug, please list the bug here.

  • bug #80067 - For reproduce the bug go to, type some text on the search field, press "TAB" and "SPACE" quickly. The search will not be started. Finex

Bugs no longer present in 4.x

If a bug is reported against a version of KDE before 4.0, but the bug can no longer be reproduced in KDE 4.x, then it should be listed here. Please do not close the bug. The Konqueror developers would like to check each one before they are closed.

Bugs to be marked as RESOLVED

Bugs filed against KDE 4 (ie, only very recent ones) that can no longer be reproduced should be listed here. Bugs filed against earlier versions of KDE that can no longer be reproduced should be listed in the section above.

  • bug #159325 - Seems to be OK with kdelibs: r793701, kdebase: r793720 - JLP

Bugs to be marked as INVALID

Bugs which are no longer valid go here. A link to the bug and why it qualifies as invalid should be provided.

Some examples of when a bug should be closed as INVALID:

  • The reported behavior is not a bug
  • The bug is completely unrelated to KDE

This list is not exhaustive. If you feel a bug is invalid for any other reason, be sure to list it here, mentioning why you think it is invalid.

Bugs to be marked as DUPLICATE

Duplicates found should be placed here with a link to the bug which you think it is a duplicate of.

Bugs needing users with particular setups

Bugs that require particular software or hardware that you don't have available should be listed here with a description of the non-standard requirement.

  • bug #40116 - needs someone with IE available so they can see what the test-case should look like when rendered correctly. Grundleborg

Non english locales

Bugs requiring non-English locales should be listed here, along with the locale they require.

Bugs needing attention from Konqueror developers

Add bugs here if you need to find out whether the observed behavior is intended, or if there's some other reason that it would be useful for a Konqueror developer to take a look. Make sure you indicate why the bug needs attention from them.

  • bug #79897 - Bug with complete testcases. Firefox 3b5 behavior is like konqueror (on KDE3 and KDE4). Actually konqueror is respecting standard. Emulate IE breaking them is not a good idea. Finex
  • bug #80285 - On this report is proposed to split on certain condition long lines without spaces. Finex

Bugs awaiting feedback

NB. Feedback should only be requested for bugs if you have tried and failed to reproduce them or if the report contains insufficient information to try and reproduce the bug. Requesting feedback for a bug should be seen as a last resort only.

Bugs for which feedback has been requested, which should be revisited in 30 days to see if there's any response. Please list all bugs here for which feedback has been requested.

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