Jump to: navigation, search



This is the page for the triage part of the KDE PIM Bug Weeks 1 which takes place from Sunday, November 23rd 2008 to Saturday, December 6th, but feel free to start early. The aim of these bug weeks is to organize as many of the KDE PIM applications' bugs as possible. Our targets for triage are bugs listed in under the products kmail and korganizer.

The goal of this bug-day is to check if bugs filed against older version of KDE PIM still apply to the latest version. If a bug is still reproducible our aim will be to find simple step-by-step solutions and/or testcases so it gets easier for the KDE PIM developers to find and fix those bugs.


You don't need any programming experience to help out with Triaging, but you will need a recent version of KDE, either svn trunk or the latest release from KDE 4.1. Information on setting up KDE from trunk can be found here. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

General information

  • This page has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get approval from a developer before you mark something a duplicate. We don't want to create more work for the developers!
  • Be sure to join #kde-bugs on, as this is where the bug-weeks will be coordinated. (You can even join now!)


First of all, put your name and the version of KDE PIM you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.


  1. Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
  2. Execute the query to get the list of bugs and go through the bugs one by one.
    1. Read the bug description and the comments carefully and try to reproduce the bug.
    2. Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KDE PIM you are testing with in the comment.
    3. Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. crash. Please mark every bug with your IRC nickname. You can easily do that by appending ~~~.
    4. Check if the bug's Version field is set properly. If not do one of the following:
      1. If the bug is reproducible, set the version field to the version of KDE PIM you are triaging with.
      2. If the bug is not reproducible, set the version field to the version the bug was reported with.
    5. Check if the bug's product and component are appropriate. Don't forget to look at the application specific hints. If the bug's product/component needs to be changed but you lack permissions, put it in the "Needs product/component change" section.
    6. If you lack bugzilla permissions to change the version field, additionally file the bug in the "needs version field change" section. Never change a version if it has already been set to a number!
    7. Mark the bug as triaged by adding the triaged keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
  3. If you're done with your batch, pick another one and start from the top :-)


Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create documents that show the buggy behaviour. In both cases we have to add the testcase keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.


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!

Upstream and Downstream

  • Some bugs are not really bugs in KDE, but might be in underlying software (eg. in Qt or in some other library used). Those bugs should be closed as UPSTREAM (or rather moved to this wiki page section called UPSTREAM).
  • Some of the bugs are introduced by the distributions packaging them. Those bugs should be closed as DOWNSTREAM.

Is it a big bug?

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

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 use the tag <s>...</s> to mark a bug as done like this.


  • You can edit single sections of this page if you you check Enable section editing via edit links in your TechBase Preferences.
  • Sometimes you might encounter edit conflicts if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).
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).


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 beta2 if you're using that):

IRC Nickname KDE PIM version used for testing
Lemma svn trunk r887937
jtamate opensuse 4.1.73
gkiagia svn trunk r884939
FiNeX svn trunk >= r888281
dtritscher Kubuntu KDE Beta2 4.1.85

Division of Labour

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

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

The bugs presented on this page are only a selection of the bugs that need triaging. If you run out of bugs to do, please tell on IRC and we'll provide new batches.

With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.


Information mostly for people organizing:

  • The template query for kmail is this one.

Additional information:

  • KMail just added the new folder- and messagelist developed in one of this year's SoC project. If you find any bugs related to those lists, please let someone with a recent build of trunk who has the new views triage the bug.
A list of known bugs of the SoC project can be found here. However, new bugs should not be reported there, they should go to bugzilla.
Bug reports about the new message list or the new folder tree should be changed to the "new message list" or "new folder tree" component. When changing the component, please also reassign to the owner of the component, which is not kdepim-bugs but the SoC student.
You need the newest version of qt-copy, otherwise you'll get random crashes, see bug 174065.
Batch No of bugs IRC Nickname Status Query
1 10 Lemma working Query
2 10 gkiagia starting Query
3 10 dtritscher working Query
4 10 Query
5 10 Query
6 10 Query
7 10 Query
8 10 Query
9 10 Query
10 10 Query
11 10 Query
12 10 Query
13 10 Query
14 10 Query
15 10 Query
16 10 Query
17 10 Query
18 10 Query
19 10 Query
20 10 Query
21 10 Query
22 10 Query
23 10 Query
24 10 Query
25 10 Query
26 10 Query
27 10 Query
28 10 Query
29 10 Query
30 10 Query


Information mostly for people organizing:

  • The template query for korganizer is this one.
Batch No of bugs IRC Nickname Status Query
1 10 jtamate done Query
2 10 FiNeX done Query
3 10 Jtamate working Query
4 10 Query
5 10 Query
6 10 Query
7 10 Query
8 10 Query
9 10 Query
10 10 Query
11 10 Query
12 10 Query
13 10 Query
14 10 Query
15 10 Query

Bugs that need changes that require permissions

If you put a bug into this section, please be sure you additionally put it into the appropriate Completed Bugs section.

Bugs to be marked as TRIAGED

Bugs that need the triaged keyword adding to them should be listed here.

Bugs to be marked as TESTCASE

Bugs needing the testcase keyword added to them should be listed here.

Bugs needing version field changed

Bugs should be listed here if their version field is invalid. For rules about which bugs need their version field changed, please check above.

Bugs needing product/component changed

Bugs that seem to be labelled incorrectly and need a product/component change should go here.

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.

Bugs to be marked as RESOLVED

Bugs that are no longer reproducible and have been fixed already go into this section. After they are double-checked they can be closed.

  • bug #86095 remote calendar over fish protocol loads correctly FiNeX
  • bug #90589 todos and sub-todos are all printed. Jtamate
  • bug #78417 - old bug/wish left open. make ldap/kresource fields configurable. Lemma
  • bug #78427 - wrong window focus if editing an attachment's properties. no longer rperoducible. Lemma
  • bug #78560 - state of the folder tree (expanded/collapsed) not saved on session end. no longer reproducible. Lemma
  • bug #68976 - broken headers in mails forwarded as attachments. can't reproduce any longer. Lemma
  • bug #69379 - mouse cursor trouble. no longer reproducible. Lemma already double-confirmed Lemma
  • bug #70227 - Folder->Properties enabled if starting KMail without any folders. can't reproduce. Lemma
  • bug #72310 - strange display if organization name is in From: header. no longer reproducible. Lemma</s> already double-confirmed Lemma
  • bug #80176 - works fine for me, also confirmed by another user. WORKSFORME

Bugs with test-cases

If the bug is still reproducible and has a test-case attached, put it here.

Bugs with step-by-step instructions

If the bug has proper step-by-step instructions to reproduce the bug it should go here. Actually most reproducible bugs should end up in this section.

  • bug #42899 a recurring event between days dissapears in weekly view. Jtamate
  • bug #64603 bad events draw. Jtamate
  • bug #77862 I have confirmed this several times in the past with kmail 1.10.1. There are step-by-step instructions on bug #173407, which is a duplicate of this one. gkiagia
  • bug #76710 grahl said it's reproducable. I don't know how to reproduce myself. gkiagia
  • bug #77904 - drafts folder should either not be renameable or renaming it should change the identities that use it. still reproducible. Lemma
  • bug #78415 - marking threads of messages as important doesn't make new messages in the thread important. still reproducible. Lemma
  • bug #78749 - small display errors when navigating the mime tree in message digests. still reproducible. Lemma
  • bug #78712 - faulty quoted-printable encoding for forward-attached mails. still reproducible. Lemma
  • bug #64815 - no encoding detection for text-attachments. still reproducible. Lemma
  • bug #65571 - kmail deletes mails on an imap account if the imap server's spool is full. Lemma
  • bug #80988 - problem with read-only mails still exists, added step-by-step instructions. dtritscher

Bugs to be marked as INVALID

Bugs which are no longer valid go here. Please provide the reason why you think this bug is invalid.

Bugs to be marked as DUPLICATE

Duplicates (or possible duplicates) found should be placed here along with a link to the bug you think it is a duplicate of.

Bugs that should be WISHES

Sometimes there are bugs that are actually wishlist items. If you think a bug is not really a bug please put it here.

  • bug #49797 It looks like a wish to me (and the reporter). Jtamate
  • bug #85897 Caching events to local cache if remote resource is not available. FiNeX
  • bug #78198 - kmail should support different encodings in the message source window. imo this is by design and should be a wish if not invalid. Lemma

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.

Non english locales

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

Bugs needing attention from KDE PIM developers

Add bugs here if you need to find out whether the observed behaviour is inteded, or if there's some other reason that it would be useful for a KDE PIM developer to take a look at. Make sure you indicate why the bug needs attention. A second common reason to put a bug here is if it has already been heavily commented on by the application's developer. In the latter case please only add bugs you can reproduce.

Always defer policy decisions to developers.

  • bug #78803 Does the perl script still exists? Jtamate
  • bug #79168 This is not possible to do with Qt4 anymore. Is that ok, or we should file a bug to trolltech? gkiagia
  • bug #80511 The actual behaviour seems right to me. Devs agree??? FiNeX
    • Winterz agree :-)
  • bug #57341 - Hard one, message status and the "Status:" header. Retry when kmail is using akonadi. Lemma
  • bug #60138 - hanging on using gpg with certain schedulers (sync gpg). Asked Ingo about it. Lemma
  • bug #80995 - maybe a WONTFIX or a wish dtritscher
  • bug #81416 - i'm not sure whether this is a bug or a feature. reporter complains about sender identity of mail replys followingthe receivers address not the indentity setting for a folder. dtritscher 16:06, 8 January 2009 (UTC)

Bugs awaiting feedback

Some bugs are hard to reproduce because the reporter left out some explanation you'd need. In that case we have no other means but to request some more information. Bugs for which feedback from the reporter has been requested should be put here. They should be revisited in 30 days to see if there's any response. If there's feedback

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.

  • bug #77088 - needs hotmail webdav access which is no longer free (and outdated). I assume this has been fixed but I'm asking the reporter if it can be closed. Lemma

Bugs that you can't do

If you have bugs in your month that you can't do, and no-one has been able to help you with on IRC, please list them here for someone else to have a look at.

High profile

Some bugs seem to be more important than the others. If you feel a bug is really really (really) important and you can still reproduce it, please put it here.

Bugs not related to KDE PIM

Put a bug in this section if it is not related to KDE PIM and needs reassignment.

This page was last modified on 8 January 2009, at 16:14. This page has been accessed 6,539 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal