< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 08:38, 26 April 2008 by Grundleborg (Talk | contribs)

Jump to: navigation, search



This day will happen in the future at some point, but feel free to start now. The aim is to carry on from where we left off on 6th April Bug Day. 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.

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>

Update bugzilla

Add your comments even on bugzilla for a more complete feedback by users and developers. When you comment on bugzilla, be sure to include the version of KDE you tested on (revision number and trunk/branch if it's SVN).


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 r795406

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

This bug day, we will be targeting two sets of bugs. If you have access to an IMAP email account, please take a group of bugs from the IMAP BUGS section. Otherwise, please take a group of general KMail bugs.

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


Period of time / month No of bugs Query IRC Nickname Status
pre-2004 6 Query
2004-01 - 2004-08 11 Query
2004-09 - 2004-10 12 Query
2004-11 - 2004-12 11 Query
2005-01 - 2005-02 5 Query
2005-03 - 2005-04 12 Query
2005-05 - 2005-06 9 Query
2005-07 - 2005-08 12 Query
2005-09 - 2005-10 8 Query
2005-11 - 2005-12 19 Query
2006-01 - 2006-02 18 Query
2006-03 - 2006-04 9 Query
2006-05 - 2006-06 14 Query
2006-07 - 2006-08 15 Query
2006-09 7 Query
2006-10 14 Query
2006-11 6 Query
2006-12 9 Query
2007-01 - 2007-02 18 Query
2007-03 - 2007-04 11 Query
2007-05 - 2007-06 8 Query
2007-07 - 2007-08 9 Query
2007-09 - 2007-10 6 Query
2007-11 - 2007-12 19 Query
2008-01 - 2008-02 10 Query
2008-03 - now 8 Query

(Total bugs 286)

General Bugs

Period of time / Month No of bugs Query IRC Nickname Status
pre-2003 5 Query
2003-01 - 2003-06 16 Query
2003-07 - 2003-12 16 Query
2004-01 - 2004-02 15 Query
2004-03 - 2004-04 11 Query
2004-05 - 2004-06 7 Query
2004-07 - 2004-08 9 Query
2004-09 - 2004-10 19 Query
2004-11 - 2004-12 19 Query
2005-01 6 Query
2005-02 6 Query
2005-03 14 Query
2005-04 10 Query
2005-05 8 Query
2005-06 14 Query
2005-07 15 Query
2005-08 8 Query
2005-09 8 Query
2005-10 8 Query
2005-11 7 Query
2005-12 12 Query
2006-01 10 Query
2006-02 13 Query
2006-03 14 Query
2006-04 7 Query
2006-05 12 Query
2006-06 11 Query
2006-07 11 Query
2006-08 9 Query
2006-09 2 Query
2006-10 10 Query
2006-11 7 Query
2006-12 12 Query
2007-01 15 Query
2007-02 11 Query
2007-03 10 Query
2007-04 6 Query
2007-05 8 Query
2007-06 12 Query
2007-07 13 Query
2007-08 14 Query
2007-09 3 Query
2007-10 12 Query
2007-11 9 Query
2007-12 11 Query
2008-01 9 Query
2008-02 6 Query
2008-03 15 Query
2008-04 - now 6 Query

(Total bugs 520)

Completed Bugs

Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up. The remainder of the page is separated into sub-pages to reduce edit conflicts. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

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 KMail developers would like to check each one before they are closed.

  • bug #63409 Cannot reproduce. Folders are synced and removed successfully after removing them from another mail client. gkiagia
  • bug #61009 the bcc entries aren'T lost anymore. --dtritscher 16:21, 12 September 2008 (CEST)
  • bug #65835 Seems to be fixed, header looks correct. --dtritscher 16:52, 12 September 2008 (CEST)
  • bug #66001 Couldn't reproduce. --dtritscher 17:10, 12 September 2008 (CEST)
  • bug #74889 the child windows are placed in the save virtual desktop as the parent window. --Jtamate 18:34, 9 September 2008 (CEST)
  • bug #90623 The pop filters stay there. --Jtamate 19:09, 10 September 2008 (CEST)
  • bug #69854 I can't reproduce that by following the steps in the description (I am afraid though I might be missing something here, as I have never used DIMAP before. Somebody please check that). gkiagia
    • worksforme --Jtamate 16:14, 12 September 2008 (CEST)
  • bug #97917 Sending big files seems to not be a problem (except the long time it takes). --Jtamate 22:25, 30 August 2008 (CEST) Lemma
  • bug #97665 The headers look the same no matter what the html mail size was. --Jtamate 01:27, 31 August 2008 (CEST) Lemma
  • bug #98589 The thread is marked right (tested with all the thread tags). --Jtamate 12:18, 31 August 2008 (CEST) Lemma
  • bug #53185 Didn't manage to crash kmail following the given instructions. --dtritscher 13:18, 31 August 2008 (CEST)
    • I have not been able to crash it, but I can open the search dialog but not being able to use it until the keys dialog is done.
      • worksforme --Jtamate 16:14, 12 September 2008 (CEST)
  • bug #83480 Instructions to reproduce no longer apply in r855160, not reproducible Lemma
    • worksforme --Jtamate 16:14, 12 September 2008 (CEST)
  • bug #82600 Related to incorrect display of the progress bar on retrieving IMAP mail. Can't reproduce Lemma
    • worksforme --Jtamate 16:14, 12 September 2008 (CEST)
  • bug #85987 Can't reproduce Lemma Lemma
  • bug #53015 Works fine with 4.1 --dtritscher 14:50, 31 August 2008 (CEST)
  • bug #60440 Seems to be fixed in 4.1 --dtritscher 15:32, 31 August 2008 (CEST)
    • worksforme --Jtamate 16:14, 12 September 2008 (CEST)
  • bug #60597 Can't reproduce in 4.1 --dtritscher 23:01, 31 August 2008 (CEST) Lemma
  • bug #92272 System tray icon is correctly updated now. gkiagia
    • worksforme --Jtamate 16:14, 12 September 2008 (CEST)
  • bug #72389 the smtp protocol max length is respected (¿test again with the [bla@bla.bla] greater than 80 characters?). --Jtamate 17:53, 9 September 2008 (CEST) Lemma
  • bug #73074 the change language in the spell checker dialog is immediate and I have not seen the crash. --Jtamate 17:58, 9 September 2008 (CEST) Lemma
  • bug #73957 the pgp signed email looks identical after traveling a lot. --Jtamate 18:17, 9 September 2008 (CEST) Lemma
  • bug #74440 the window order is the good one. --Jtamate 18:22, 9 September 2008 (CEST) Lemma
  • bug #74902 the folder option is used to compose a new mail. --Jtamate 18:37, 9 September 2008 (CEST) Lemma
  • bug #75724 the view source shortkey works as expected. --Jtamate 18:56, 9 September 2008 (CEST) Lemma
  • bug #89402 The names with "xxx,xxx" are shown good. --Jtamate 18:48, 10 September 2008 (CEST) Lemma
  • bug #90599 does not change the mail id. --Jtamate 19:09, 10 September 2008 (CEST) Lemma
  • bug #91909 the vcard background is good. --Jtamate 19:16, 10 September 2008 (CEST) Lemma
  • bug #92121 this shortcut works as expected. --Jtamate 19:16, 10 September 2008 (CEST) Lemma
  • bug #65916 Couldn't find any problem. --dtritscher 17:03, 12 September 2008 (CEST) Lemma
  • bug #126714 Can't reproduce in kde 4.1.1. sahaqiel Lemma
  • bug #124679 Reporter claims there is a menu item called Troubleshoot IMAP in the Folder menu, but since I can't find it in kde 4.1.1, I suppose it's "fixed" ( although the bug is about shortcuts ). Also, there's a patch that goes around the bug, don't know if it was applied to kde3.5 or not. sahaqiel Lemma

/Bugs needing version field changed

/Bugs with test-cases Added

/Bugs with step-by-step instructions

/Bugs to be marked as RESOLVED

/Bugs to be marked as INVALID

/Bugs to be marked as DUPLICATE

/Bugs needing users with particular setups

/Non english locales

/Bugs needing attention from KMail developers

/High Profile

/Needs more information

/Bugs awaiting feedback

/Bugs not related to today

/Bugs that you cant do

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