< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 11:41, 9 November 2008 by Dtritscher (Talk | contribs)

Jump to: navigation, search



This is the page for the triage part of the KDE PIM Bug Day 2 which takes place on Sunday, November 9th 2008, but feel free to start early. The aim of this bug day is to organize as many of the KDE PIM applications' bugs as possible. Our targets for triage are bugs listed in under the products akregator, kaddressbook, kmail, knode, kontact and korganizer.

The goal of this bug-day is to check if bugs filed against older version of KDE PIM still apply to the new 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.3. 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-day 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!

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 r881868
jtamate opensuse 4.1.72
JLP svn trunk r881890
opensourcecat svn trunk r881888
dtritscher Kubuntu 4.1.3
Blauzahl svn trunk kdepim 881804
Krop svn trunk kdepim 881888
gkiagia svn trunk r881933

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 done Query
2 10 Lemma starting Query
3 10 Query
4 10 Query
5 10 Query
6 10 Query
7 10 opensourcecat starting Query
8 10 Query
9 10 Query
10 10 krop starting Query
11 10 Query
12 10 Query
13 10 Query
14 10 Query


Information mostly for people organizing:

  • The template query for korganizer is [ this one].
  • Check for [ untriaged bugs].
Batch No of bugs IRC Nickname Status Query
1 10 Query
2 10 Query
3 10 Query
4 10 Query
5 10 Query
6 10 Query
7 10 Query
8 10 Query
9 10 Query
10 10 Query


Information mostly for people organizing:

  • The template query for akregator is this one.
Batch No of bugs IRC Nickname Status Query
1 10 jtamate working Query
2 10 dtritscher done Query
3 10 Query
4 10 Query
5 10 Query


Information mostly for people organizing:

  • The template query for kaddressbook is this one.
Batch No of bugs IRC Nickname Status Query
1 10 Query
2 10 Query
3 10 Query
4 10 Query
5 10 Query


Information mostly for people organizing:

  • The template query for knode is [ this one].
  • Check for [ untriaged bugs].
Batch No of bugs IRC Nickname Status Query
1 10 Query
2 10 Query
3 10 Query
4 10 Query
5 10 Query


Information mostly for people organizing:

  • The template query for kontact is [ this one].
  • Check for [ untriaged bugs].
Batch No of bugs IRC Nickname Status Query
1 10 Query
2 10 Query
3 10 Query
4 10 Query
5 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 #127097 crash in progress labels - Hum
  • bug #126853 Font sizes in internal browser differ from konqueror Hum
  • bug #92051 - Cursor resetting/view scrolling after spell-checking (and correction). works for me. Lemma
    • kdelibs/ktextedit bug now
  • bug #92210 - Message preview empty after receiving a new mail in the same folder. Can't reproduce, never saw this. Lemma
  • bug #116482 - Can't reproduce that crash. dtritscher 11:23, 9 November 2008 (UTC)
    • not fixed yet
  • bug #114997 - Couldn't reproduce with Akregator 1.3.3 dtritscher 11:32, 9 November 2008 (UTC)
  • bug #81561 - Bug gone. Opensourcecat
  • bug #120791 - Couldn't reproduce with Akregator 1.3.3 dtritscher 13:57, 9 November 2008 (UTC)
  • bug #123584 - Couldn't reproduce with Akregator 1.3.3 dtritscher 14:27, 9 November 2008 (UTC)
  • bug #68976 - Can't reproduce with KMail 1.10.1 fvilas 14:52, 9 November 2008 (UTC)
  • bug #72310 - Seems resolved in KMail 1.10.1. See bug comments for steps taken fvilas 15:54, 9 November 2008 (UTC)
  • bug #73215 - fixed in KDE 4.1.2 and SVN JLP
  • bug #74852 - fixed in SVN JLP
  • bug #69379 - Seems resolved in KMail 1.10.1. fvilas 18:22, 9 November 2008 (UTC)
  • bug #56079 - attachment icons for encrypted message parts. no longer reproducible. Lemma
  • bug #92269 - forwarding adds a default date if the forwarded message doesn't have one. no longer reproducible. Lemma closed by togge. Lemma
  • bug #44378 - mbox bug on opensolaris. presumably fixed by winterz - ask him about it. Lemma closed after asking winterz. Lemma
  • bug #92307 - Sometimes the message gets lost if moving from online imap to local folder, related to attachment-on-demand. Can't reproduce. Lemma Closed as it was already confirmed working in 2006.
  • bug #80309 - Bug gone. Does not apply to newer version at all. opensourcecat Can't reproduce either. Lemma
  • bug #92012 - Selecting messages in the messagelist using shift+end/shift+home works fine with the new views. (so obvious I closed right away) Lemma

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 #124486 - Arrow keys do not scroll the html widget when focus on article list - Hum
  • bug #127671 - Expired articles deleted from list but are not from files - Hum
  • bug #127322 akregator --addfeed <url> doesn't work when aKregator runs inside kontact - Hum
  • bug #91820 - crash Copying mails from one KMail window to another one doesn't work or even crashes. Lemma
  • bug #117878 - still different icon sizes shown in akregator 1.3.3. dtritscher 10:48, 9 November 2008 (UTC)
  • bug #114090 - Akregator still shows Kontact icon and name in systray icon when embedded in Kontact- dtritscher 10:55, 9 November 2008 (UTC)
  • bug #114397 - When Akregator is embedded within kontact, it starts fetching feeds only after selecting Akregator in Kontact. dtritscher 10:59, 9 November 2008 (UTC)
  • bug #117478 - Akregator still shows wrong relative links. dtritscher 11:06, 9 November 2008 (UTC)
  • bug #118484 - Akregator 1.3.3 doesn't displays tooltips at all. dtritscher 11:09, 9 November 2008 (UTC)
  • bug #111908 - Akregator 1.3.3 still shows this behaviour. dtritscher 11:38, 9 November 2008 (UTC)
  • bug #117314 - Akregator 1.3.3 still shows this behaviour. dtritscher 11:40, 9 November 2008 (UTC)
  • bug #81078 - Kmail, inserting addresses containig characters to decode does'n work. Opensourcecat 12:00, 9 November 2008 (UTC)
  • bug #121312 - Akregator 1.3.3 still shows this behaviour. dtritscher 14:12, 9 November 2008 (UTC)
  • bug #119724 - Akregator 1.3.3 still shows this behaviour.
  • bug #74938 - Bug still present in KMail from SVN. JLP
  • bug #37307 - No means to print attachments. Still reproducible. Lemma
  • bug #41514 - KMail's UI still freezes while long-running external filters are at work. Lemma
  • bug #56079 - Maildir mails are stored using a ':', problem still reproducible. Shouldn't it be possible to completely replace that? Lemma
  • bug #75673 - KMail from SVN still starts maximized instead of minimized to system tray. JLP
  • bug #75699 - Even with the new messages list the wish is still valid. JLP

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. Some examples of when a bug should be closed as INVALID:

  • The reported behaviour is not a bug.
  • The bug is completely unrelated to KDE PIM.

This list is not exhaustive. If you feel a bug is invalid for any other reason, be fure to list it here, mentioning why you think it is invalid. Before closing a bug as INVALID, be sure to get a developer's opinion.

  • bug #127111 - Back button does not work correctly with frames <-- This is also existent in konqueror which leads me to believe this isn't a akgregator bug
    • This bug is still there. Konqueror behaves differently. Lemma
  • bug #92198 - problems with an IMAP server we can't get any access to. Reporter solved the problem himself. I suggest closing this as there's nothing left to do. Lemma
  • bug #92299 - Completely incomprehensible bugreport about fonts (?), reporter was asked to clarify in 2006, no activity. Lemma INVALID right away. Lemma
  • bug #121879 - Upgrade issue for Akregator, upgrading from KDE3.4.2 to 3.5.x, not valid anymore. Additionally upgrade issues should be addressed by distributors. dtritscher 14:19, 9 November 2008 (UTC)
  • bug #122405 - one time occurence, not reproduceble, affected archive file deleted. dtritscher 14:21, 9 November 2008 (UTC)
  • bug #121711 - feature doesn't exist any more in akregator 1.3.3 dtritscher 14:46, 9 November 2008 (UTC)

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 #110190 Clearly a wish. probably already implemented.
  • bug #91777 - DBus sendMessage() reply doesn't indicate if the mail was sent. This is by design. Lemma
  • bug #127117 Should indicate what the alternative to 'interval fetching' is - Hum
  • bug #118908 - Reporter requests new featuer. dtritscher 14:29, 9 November 2008 (UTC)
    • I think it's a bug :) Lemma
  • bug #120602 - Typical "It's not a bug, it's a feature!". If people want it to be changed, it's a wish. dtritscher 14:37, 9 November 2008 (UTC)

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.

  • bug #75780 - Needs someone with German locale. Maybe not even KDE PIM problem. JLP

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 #91819 - easy Don't set minimum kmmainwidget.cpp window size to make it smaller. Lemma fixed Lemma
  • bug #80995 - It is not clear if this can be implemented or not. Can't call it "wish" because it is the normal behaviour with downloaded mail (pop3). Opensourcecat
  • bug #83038 Devs have to check thath. Opensourcecat 13:10, 9 November 2008 (UTC)
  • bug #37898 - index files, corruption and compacting folders. plenty of discussion, seems to be fixed. maybe this could be closed. Lemma
  • bug #49310 - bug about indices and manually moving mails in maildirs. probably resolved but a little unsure. Lemma
  • bug #51410 - behaviour of the sign button when switching identities. maybe a policy issue. Lemma
  • bug #57192 - Sticky identity overwrites identity if editing draft messages. Policy. Please clarify if this is a bug or a wish. Lemma
  • bug #75045 - I don't have many mails with large photos, only large amounts of text mail which couldn't trigger this. JLP
  • bug #77058 - I don't have any faulty server to test with, all work fine for me. And by comment #5 I'd say this is not a bug, but developers should decide. JLP

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 #121042 No info how to reproduce, never stumbeled over this problem by myself. dtritscher 14:01, 9 November 2008 (UTC) WAITINGFORINFO

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.

  • bug #124678 - Change the system tray icon colour <-- I don't have a functioning system tray to test this - Hum
  • bug #70283 - I'm not sure how to setup the test for this. fvilas 18:10, 9 November 2008 (UTC)
  • bug #76710 - Don't have any encrypted mail in my inbox to test this. JLP

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.

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