Introduction

This bug day will take place on Sunday, August 1st 2010, but feel free to start early. The aim of this bug day is to get as many Dolphin-related bugs done as possible. Our target for triage is bugs listed in bugs.kde.org under the product Dolphin.

Goals of this Bug Day

Check if bugs reported for Dolphin which are previously UNCONFIRMED are reproducible.

If a bug's description is somewhat unclear, try to provide a better step-by-step procedure on how to reproduce it. This will make it easier for developers to find and fix the bug.

Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eye principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.

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 be working with KDE SC 4 (either 4.4 or newer, preferably 4.5 RC3 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).

Is it a big bug?

Prioritizing is good. If a major application doesn't work, this should be taken care of.

Version field

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 4.0 to 4.2)

As requested by the Dolphin maintainter, just leave it to the version where the user has reported it, not to the version where it could be reproduced.

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>

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 Bug Day, 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 batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which batches bugs you are working on to avoid duplication of effort.

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.

Bugs needing Version Field changed

If you don't have bugzilla permissions yet, you can't change version fields. Put what needs changing here and someone else will go through and do it for you. Don't worry, you'll have permissions soon enough...

Valid bugs with step-by-step instructions

If it is a deterministic bug, put it here. Make sure it has instructions. You should be able to verify it. (Write that you did on bugzilla and include your version information.)

INVALID bugs

A bug is INVALID if it describes desired behavior, or something that isn't a bug.

bug #234217The automount feature of a external HDD is managed by HAL (with rigths configurable at /etc/hald/....) or Solid. Also, there is a simple workaround. Create the contents inside a folder of the folder where it is mounted. It is invalid (or a solid bug) Jtamate

I would consider this bug as invalid too. The behaviour is what I expect. FiNeX

Valid bugs that should be marked as NEW

If a bug was previously UNCONFIRMED and you can reproduce it, put it here.

bug #182914 It keeps a light blue selected when you right click and do not uses the menu (rigth clicking in the main view, or just pressing ESC). Jtamate

Dolphin bugs that need attention from developers

If anything is in doubt, put it here, and give a description of why you think a developer should look at it.

bug #240972The status line info policy seems to be: if the mouse is over an item, show this information, with priority over the keyboard actions. Is this rigth? Jtamate

bug #223680 - Related to using FTP in Dolphin. Can't reproduce but it might be specific to the server software used by the reporter. Lemma

bug #227412 - I only get one thumbnailer so it seems like the actual bug got fixed, however when closing Dolphin the thumbnailer keeps creating thumbnails and the jobs don't seem to get cancelled. Lemma

Bugs needing Feedback

If a bug sounds valid but can't really be reproduced and needs more information from the reporter, put it here.

bug #220517Can not reproduce (I've tried folders with spaces, copying them, their children,...). I think it deserves to ask the reporter if he is still able to reproduce it with a more recent KDE SCJtamate

bug #241212Can not reproduce with a slow usb stick, but asking the reporter would be better. Jtamate

bug #246030 - Can't reproduce, works as expected here. However, asked the user how his KDE was built (sources/packages) for further investigation. anselmolsm

bug #232536 - I didn't figure out how to reproduce this bug (ie. what conditions the file being copied has to match in order to get the dialog). Tried on 4.4.5 using a loop-mounted ntfs image. Lemma