This bug day will take place on Sunday, May 18th 2008, but feel free to start early. The aim of this bug day is to clear as many Konqueror-general bugs as possible. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Konqueror, component General.

−

'''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. [http://konqueror.kde.org/investigatebug/ This page] provides an excellent explanation of how to create a test-case. [http://techbase.kde.org/index.php?title=Contribute/Bugsquad 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!'''

+

{{Tip|This is a mostly self-contained page for an introduction to triage. At this point, it is ongoing. If you are new, carefully document your work, and do a month or two. Then find grundleborg or blauzahl on irc.}}

+

+

This bug day will take place on Sunday, June 1th 2008, but feel free to start early. The aim of this bug day is to clear as many Konqueror-general bugs as possible. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Konqueror, component General.

+

+

'''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 rendering 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.

+

+

[http://konqueror.kde.org/investigatebug/ This page] provides an excellent explanation of how to create a test-case. [http://techbase.kde.org/index.php?title=Contribute/Bugsquad 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!)

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!)

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> 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).}}

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> 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).}}

Line 74:

Line 94:

The bugzilla query to use for this triage day can be [http://bugs.kde.org/query.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=konqueror&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2003-03-01&chfieldto=2003-03-31&chfieldvalue=&newqueryname=&namedcmd=2003-onwards found here]. Be sure to correct the dates to the month which you will triage before running the query.

The bugzilla query to use for this triage day can be [http://bugs.kde.org/query.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=konqueror&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2003-03-01&chfieldto=2003-03-31&chfieldvalue=&newqueryname=&namedcmd=2003-onwards found here]. Be sure to correct the dates to the month which you will triage before running the query.

−

{{Tip| '''The most recent months (2008+) should be done by people using recent SVN trunk.'''}}

+

{{Tip| '''The most recent months (2008+) should be done by people using recent SVN trunk. In general, the most recent version you can use of 4, the better.'''}}

{{Warning| 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.}}

{{Warning| 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.}}

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.

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.

+

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.

{{:Contribute/Bugsquad/BugDays/KonquerorDay5/Bugs no longer present in 4.x}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay5/Bugs no longer present in 4.x}}

This is a mostly self-contained page for an introduction to triage. At this point, it is ongoing. If you are new, carefully document your work, and do a month or two. Then find grundleborg or blauzahl on irc.

This bug day will take place on Sunday, June 1th 2008, but feel free to start early. The aim of this bug day is to clear as many Konqueror-general bugs as possible. Our target for triage is bugs listed in bugs.kde.org under the product Konqueror, component General.

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 rendering 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.3 or newer is best or SVN trunk) for testing these bugs.

Warning

Always 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 and which distro the packages come from).

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!

Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to match what the report says, i.e. to match version the bug was first reported in. Do not change the version number if it is currently set as a number! (ex. from 3.5.2 to 4.0.2)

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.

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.

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).

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.

Tip

The most recent months (2008+) should be done by people using recent SVN trunk. In general, the most recent version you can use of 4, the better.

Warning

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.

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.

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 #161375 flash seems to be working properly, though i am not using x86_64 and the reporter was. Ramblurr

flash is a pain. we should get someone with 64 to test that to make double sure (until recently it didn't work, hey everyone help me figure out how recently and fill in the flash chart above in the labor section), and then i'll write some nice anti-3.5.9 comment if need be. In general, a lot of the flash bugs are dups.Blauzahl

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.

Normally we'd never change version numbers (that's an amarok-specific thing). Since there were no comments, and it was a test suite, I must have told you to change it to version: svn :D And then tossed the url to devs, and as you'll see, harri commented on it, and they're doing stuff with it. Somewhere you'll find a bug open for the acid3 testsuite as well. It has a long list of updates as things get added, although at this point if you're curious there's a techbase page that has a list of tests that don't pass and more information. Blauzahl

bug #143770 now it crashes, gah; is it related to that other bug with file download stuff? Blauzahl

bug #143830 flash game doesn't load; actually maybe this is a dup too, dunno and we'll probalby never know given that its flash; doubt there's much they can do with this, though so i'm putting it in this section Blauzahl

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 #138325 - The first issue mentioned in the report (finding) is a duplicate of bug #31340. The second issue (scrolling) is a separate problem, Konqueror behaves unintuitively and different from Firefox. One could either file this as a new bug or keep the report open and change the summary to reflect only the scrolling issue. Added a small testcase demonstrating both issues. Frank78ac

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 #138328 Thumbnails in PNG format sometimes have a similar or even larger file size than the original image in JPG. Reporter suggests to use JPG thumbnails in these cases. Devs should decide if it's worth the effort or if it's WONTFX. Frank78ac

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 #141269 I don't know if this is invalid or not, but since Gmail defaults to Basic HTML, konqueror needs to set browser id to firefox2, which in kde 3.5.9 I don't have the option for and I believe trunk needs to have extragear or playground aditional packages, so I asked if it still happens. sahaqiel

Bram is one of us, and he asked for more information a while back. No reponse for over a month; so you can close it with REMIND and a note asking to reopen if they can provide more information. Blauzahl

Sounds specific to the port. I changed OS field to be MS Windows and set this to "new", we should find out what the email address of the windows port mailing list is and send it to there, since they don't tend to look at bz.Blauzahl

bug #138578 - Confirmed that menus are covered in 3.5.9, but menus are covered by flash stuff in Firefox 3 Beta 5 too, so I guess it's an error in the page. However, Konqueror has only two menus (Teams, Shop), Firefox has more. Can't test on trunk (flash). Frank78ac