Introduction

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 bugs.kde.org 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 irc.freenode.net, 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.

Testcases

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.

Unclear

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.

Details

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.

Sign-in

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 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 bugs.kde.org 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.

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.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. 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.

For those interested, this was implemented after a short discussion on IRC between grundleborg, blauzahl, _lemma, and myself (nixeagle).

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.

bug #124312 - Resolved in 4.0.3 - Please note the bug is unconfirmed, but was confirmad at one time (A dev unconfirmed it again noting similar behavior to firefox). However the report is resolved so that it works as the filer wanted. Nixeagle

bug #134442 - Test case (has to be marked!) works fine in trunk (no flickering access keys), but not in 3.5.9. Also true for the mentioned website (flickering is less obvious than in test case), but someone with working flash on trunk might want to verify this.Frank78ac closed with worksforme and testcase marked by DanielW

bug #151500 - I think the size part is fixed in 4.0.3, as for rendering, I'm not sure the small differences really matters. Not fixed in 3.5.9. Talavis

Bugs needing version field changed

Bugs should be listed here if their version field is invalid (i.e. it is listed as "unspecified") and they are still present in KDE 4, so that the version field can be corrected. In general, we are not changing the version numbers.

If a bug fits another category, put it there and add the notation that the version field needs changing.

bug #133979 - Confirmed in trunk (was confirmed already in 4.0.3, comment #7). Instructions already there. In addition to the "old" bug, the page is rendered incorrectly in KDE 4. Maybe one should change the bug summary or file a new bug to reflect this. Frank78ac

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 #151453 - since Konqueror 4 seems usable, I guess this bug about Konq crashing at quit can be considered resolved.

bug #141733 - original reporter claimed the site changed several days after reporting the bug (openmoko.org). However retrieving an old version from archive.org doesn't show any difference. Unreproducible. lemma

bug #141067 - Site seems to have changed (not reproducible/retrievable using archive.org) or the original reporter was just plain wrong. I asked if he could provide some more information. If he can't i vote INVALID lemma

bug #133994 - Reasons to mark as invalid: 1. The bug was due to the website using too old udm4 menus, see first comment to the bug. 2. Website has changed, does not have the drop down menus anymore. Frank78ac

bug #133426 - Confirmed the original report in trunk ("Go to next component" does not work). I get Javascript errors when error reporting is turned on. Did not check what was reported in comment #5 because I don't have a Dell account. Maybe someone with an account can check this? Frank78ac

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 #124193 - Report has a problem with XLST, the only response to this bug is that XLST is not supported.Nixeagle

Maksim has had a look, stated it was low priority but not a WONTFIX. Nixeagle

bug #124843 - Report appears as if it may have a fix on the page. However I can't confirm as there is no way to get a working demo up. If you guys happen to know if this is resolved, please close it. Otherwise we have to wait until we can get a working demo going again. Nixeagle

bug #144361 - Bug is reproducible in 3.5.9 and trunk. Maksim wondered about which specification the keygen field belongs to. Should be researched and ither implemented or marked as invalid. mutlu_inek

bug #134232 - Cannot reproduce crash on 3.5.8 and trunk. Not sure if this is fixed or if the website changed (the mentioned page seems to be unavailable on archive.org). Reporter had attached a patch to fix the bug, so the developers might be able to say if this is fixed or not. Frank78ac

bug #134165 - Test case not available any more (404 not found; archive.org doesn't have it). Not sure if the bug is still there or if Maksim got enough information to fix it (see comment #4). Frank78ac

bug #139603 - Still reproducible in 3.5.9, can't confirm for trunk as user-defined stylesheets are currently not working. lemma

bug #135457 - carewolf's comment is that konq's behaviour is probably correct. The reporter disagrees. Konq behaves the same as ff. Philrod

bug #145224 - bug (if it is a bug) still reproducible. A patch has been done. It should be tested. FiNeX

bug #146562 - jamendo.com flash music audio backend error, wants XUL and FF or IE according to greeneg, maybe we should send them a polite email, since it sounds like a site-issue that could easily be fixed on their end, i don't remember if i tried cloaking, it loads really slowly, so i probably forgot to check if it worked, doh! Blauzahl

bug #146384 - Bank site issue, seems fixed now, can probably close, but maybe not; some XHR thing that maybe still exists elsewhere and the patch was never applied SadEagle didn't like it Blauzahl

bug #134258 - Germain seemed to think in 2006 it was not really a bug. Rendering of the test cases in trunk seems to be very close to Firefox now (text padding doesn't overlap with surrounding text any more in 2nd test case, FF just has a larger gap). Frank78ac

bug #147256 testcase, this is one where SadEagle & germain both seem to have patches, but it's still open probably for a reasonBlauzahl

Needs more information

bug #134002 - Bug still present in "original page" in 3.5.8 and trunk. Test case unavailable at the moment (Timeout on server; archive.org doesn't have the page). We should check later if the server works again or ask for a new test case if it doesn't. Frank78ac

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.

bug #122883 - No way to reproduce this as the links for the testcase give 403 forbidden. I've asked for updated links if there are still some available. Nixeagle