KDE TechBase - User contributions [en]

User:DarioAndres/TriageTaskCrashLogout

2011-09-30T00:57:14Z

DarioAndres: Blanked the page

User:DarioAndres/TriageTaskCrashLogout

2011-09-29T23:20:28Z

DarioAndres:

Note: for this test we will be using a new user account because it will contain a default KDE setup with no customizations which could interfere.
Also note that some distributions have different default configurations. This could affect the behavior too.

After each "test run", check if Plasma crashes when quitting it.

- Create a new user account

<pre>
Test 1:
- Login into your new user account
- Exit Plasma / Logout
(if it crashes, were there any applicacion window shown ?)

Test 2:
- Login into your new user account / Restart Plasma
- Start an application, so a window is created
- Close this window
- Exit Plasma / Logout

Test 2a:
- Login into your new user account / Restart Plasma
- Start an application, so a window is created. Start more windows of that application.
- Close one window
- Exit Plasma / Logout

Test 2b:
- Login into your new user account / Restart Plasma
- Start an application, so a window is created. Start more windows of that application.
- Close more than one window.
- Exit Plasma / Logout

Test 3:
- Login into your new user account / Restart Plasma
- Start several applications with one or more windows
- Close some applications of all of them
- Exit Plasma / Logout

Test 4:
- Login into your new user account / Restart Plasma
- Customize the taskbar layout to your like
- Start several applications with one or more windows (try different combinations)
- Close some applications of all of them (try different combinations)
- Exit Plasma / Logout

Test 5:
- Login into your new user account / Restart Plasma
- Start several applications with one or more windows (try different combinations)
- Try grouping/ungrouping the taskbar entries of those windows
- Close some applications of all of them (try different combinations)
- Exit Plasma / Logout

Test 6:
- Login into your new user account / Restart Plasma
- Start several applications with one or more windows (try different combinations)
- Try grouping/ungrouping the taskbar entries of those windows
- Change taskbar entries grouping settings
- Close some applications of all of them (try different combinations)
- Exit Plasma / Logout
</pre>

User:DarioAndres/TriageTaskCrashLogout

2011-09-29T23:15:21Z

DarioAndres:

Note: for this test we will be using a new user account because it will contain a default KDE setup with no customizations which could interfere.
Also note that some distributions have different default configurations. This could affect the behavior too.

After each "test run", check if Plasma crashes when quitting it.

- Create a new user account

<pre>
Test 1:
- Login into your new user account
- Exit Plasma / Logout
(if it crashes, were there any applicacion window shown ?)

Test 2:
- Login into your new user account / Restart Plasma
- Start an application, so a window is created
- Close this window
- Exit Plasma / Logout

Test 2a:
- Login into your new user account / Restart Plasma
- Start an application, so a window is created. Start more windows of that application.
- Close one window
- Exit Plasma / Logout

Test 2b:
- Login into your new user account / Restart Plasma
- Start an application, so a window is created. Start more windows of that application.
- Close more than one window.
- Exit Plasma / Logout

Test 3:
- Login into your new user account / Restart Plasma
- Start several applications with one or more windows
- Close some applications of all of them
- Exit Plasma / Logout

Test 4:
- Login into your new user account / Restart Plasma
- Customize the taskbar layout to your like
- Start several applications with one or more windows (try different combinations)
- Close some applications of all of them (try different combinations)
- Exit Plasma / Logout

Test 5:
- Login into your new user account / Restart Plasma
- Start several applications with one or more windows (try different combinations)
- Change grouping options of those windows/applications
- Close some applications of all of them (try different combinations)
- Exit Plasma / Logout
</pre>

User:DarioAndres/TriageTaskCrashLogout

2011-09-29T23:14:18Z

DarioAndres: Created page with "Note: for this test we will be using a new user account because it will contain a default KDE setup with no customizations which could interfere. Also note that some distribution..."

Contribute/Bugsquad

2010-12-19T14:18:59Z

DarioAndres:

[[File:Bugweeks_ladybug.png]]

==What is BugSquad?==

The '''KDE BugSquad''' keeps track of incoming bugs in KDE software, and goes through old bugs. We verify that a bug exists, and is reproducible, and that the reporter has given enough information. When applicable, we write testcases. ''Our end goal is to help developers notice valid bugs quicker, and to save their time.''

You do not need any programming knowledge to be in the Bugsquad, and it is a great way to give practical support to the KDE community. If you are just starting to learn programming, it is a great way to gain familiarity with the components.

==Bug Days==

We have regular days where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla cleaning day.

{{:Contribute/Bugsquad/NextBugDay}}

[[:Contribute/Bugsquad/OrganizingABugDay|How to organize a BugDay]]

The results of all past bug days can be found [[/BugDays|here]].

===Bug Weeks===

Our team has recently launched a new iniciative named "Bug Weeks", as an evolution of the traditional BugDays. All the workflow is based on the [http://forum.kde.org/ KDE Community Forums].

You can find more information about it at [http://forum.kde.org/viewtopic.php?f=4&t=84473 its official announcement]

The first bugweek was about triaging Plasma Desktop bug reports. You can find more information in the [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek Session 0 article]. (A summary article is yet to come)

{{note|We don't just do bugs on BugDays! Don't hesitate to join us at '''#kde-bugs''' on irc.freenode.net, we have plenty for you to do. ;) Check the topic to see what we are currently working on. And if you are new, please read the "how to triage bugs" page.}}

==How to help==

Read the [[/Guide_To_BugTriaging|ultimate guide to BugTriaging for KDE Projects]] (Recommended)

or ...

Read this [[/Guide|guide]] and join us for one of our [[#Bug_Days|bug days]] or [[#Bug_Weeks|bug weeks]]. We meet on IRC in the #kde-bugs channel on irc.freenode.org. You can easily get started by having your questions answered there, and having someone guide you as to general bug triaging philosophy. Someone in IRC will usually be able to help you. Although we do sleep sometimes!

A summary of the BugSquad guide is provided below to give you a quick idea of how you can help:

* Confirming bugs. Bugs with the UNCONFIRMED status should get the NEW status once someone else is able to reproduce the bug reliably.
* Finding bug duplicates. Many bugs entered into Bugzilla are duplicates of other bugs. Sometimes it's hard to recognize these as duplicates but multiple people checking can make the duplicates bubble to the top of the pile. The following remarks may help you identifying them:
** Using the Similar Bugs link to look if there are duplicates.
** In the case of crashes, use the link below the comment field to look for crash reports with the same backtrace. The backtrace must be in the body of the report in order to look for similar reports. This tool does not look in attachments with backtraces.
* Close bugs which have insufficient information and which have been open for a long time (e.g. reporter does not respond to a need-more-info request). Usually a timeout of one month or more is considered to be an "information timeout".
* Categorize bugs into the right components. Many bug reports can be further categorized into components. For example, Konqueror reports can be assigned to KHTML and kfm components.
* Labeling bugs which contain testcases as such in the title. Ideally, testcases contain the minimal amount of code (HTML, scripts, C++ etc.) necessary to reproduce a bug.
* Writing testcases. Very useful and saves developers' time.

==Getting started==
The sheer number of open bugs can be overwhelming at the start. Here are some hints on getting started more smoothly:
* Look at a single product at a time. For large applications (like Konqueror), you may want to further limit your search to a particular component.
* Don't try to find duplicates early on. Finding duplicates is hard until you have become familiar with the bugs in a component. Start out with verifying UNCONFIRMED bugs as described above. That's valuable work, and a great way to familiarize yourself with the bug database.
* Avoid very old bugs with many comments, and also bugs with many votes. This may seem counter-intuitive, but in most cases these bugs are hard, have gotten a lot of attention, and are probably on a developer's TODO list already. If it is from an older version of KDE, and there are no recent comments, verify them, make a notation, and move on.
* Don't be afraid to ask the reporter for more info. It's something you can even do without Bugzilla permissions. And reporters will generally prefer being asked one question too many, instead of their report never being dealt with. Just remember to be polite. Ask yourself how you would feel if you got the message you are thinking about sending to a user.
* Look at the incoming Bugzilla bugs. Or find the oldest bugs for your favorite software application.
* Look through the rest of our documentation for more information!

==Articles==

* [[/Guide_To_BugTriaging|Dario's Guide to Bug Triaging]] - Extensive guide on how to perform bug triagers tasks

* [[/Quick_Introduction_to_Bugzilla|Quick introduction to Bugzilla]] - This article explains the basics about the bugtracking software that KDE uses: "Bugzilla". It includes the description of a bug reports fields and the workflow of most common tasks like searching into the databse.

* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle] - This article describes the possible status of a bug report and when each should be used.

* [[/How to triage bugs|How to triage bugs]] - This article gives step-by-step what you do during a BugDay, or how to start triaging on your own in our "ongoing triage" (usually for old Konqueror bugs; see #kde-bugs for the current link).

* [[Projects/SystemSettings#Bug_Triaging|How to triage System Settings bugs]] - Explains how System Settings works from a bug squasher's perspective.

* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment] - This article from the BugWeeks initiative describes how to properly configure and setup a KDE SC environment in order to test the bugs.

* [[/How to create useful crash reports|How to create useful crash reports]] - This article helps users to prepare their KDE packages such they can create detailed backtraces.

* [[User:DarioAndres/Basic_Guide_about_Crash_Reporting|Basic guide about crash reports]] - This article is a basic/simplified version of the previous one.

==External links==
*[http://bugs.kde.org/ Bug Tracker]
*[http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&bugidtype=include&bug_id=&votes=100&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&newqueryname=&order=bugs.votes,bugs.priority%2C%20bugs.bug_severity%2C%20bugs.bug_status%2C%20bugs.bug_id%20desc Feature Requests, sorted by popularity]
*[https://mail.kde.org/mailman/listinfo/bugsquad Subscribe to our mailinglist]
*[http://forum.kde.org/viewforum.php?f=148 BugWeeks subforum]
*[http://gitweb.kde.org/scratch/darioandres/bugsquad.git DarioAndres BugSquad GIT repo with useful scripts (including the batch generation for events)]

Contribute/ImportantWorkToBeDone

2010-12-15T20:13:17Z

DarioAndres:

===General===

* FIXME comments: http://lxr.kde.org/search?filestring=cpp&string=%2F%2FFIXME
* TODO comments: http://lxr.kde.org/search?filestring=cpp&string=%2F%2FTODO
* Warning compiler comments: http://lxr.kde.org/search?filestring=cpp&string=%23warning

===KDE technologies===

* KDELIBS
** <s>Update KBugReport to use the new enterbug form (which replaces the wizard)</s> Wizard was adapted to forward the data to enter_bug
** Improve the KBugReport UI dialog, improve the app/component selection

* Phonon
** <s>(In progress) Get someone to review phonon bug reports on BKO; or submit them upstream</s> [sandsmark]
** <s>More collaboration/connection between KDE and Qt teams about this technology</s> Qt "dropped" Phonon, KDE team takes responsibility
** <s>Pulseaudio mess</s> Fixed in latest Phonon

* Solid
** <s>(In progress) Solid-bluetooth needs a maintainer</s> [afiestas got the maintainership of kbluetooth]

* Other
** libkcddb needs a maintainer

===KDE applications===

====Unmaintained====

* KThemeManager could be removed from the code (kdebase/workspace/kcontrol)

* Find a maintainer for KFind
** It needs a rewrite/check of some parts (to not use Process events)
** Improve UI / Extract to UI file
** Strigi/Nepomuk integration
** <s>KFindPart should be removed (unused according to lxr.kde.org)</s> Done for KDESC4.5

* Find a maintainer for KWikdisk/KDiskFree [sandmark has suggest to replace those apps with filelight]
** Integrate Solid devices
** More portable / system-independant code
** Fixes on the treewidget and model implementation

* Find a maintainer for KSystraycmd
** Port to the new systray icon library

* Find a maintainer for DragonPlayer [eean is the official maintainer, sandsmark is willing to accept bug reports]

* Find a maintainer for KolourPaint

* Find a maintainer for KRFB (or remove/replace it) [grundleborg?]
* <s>Find a maintainer for KInfoCenter?
** Some modules need porting to Qt4 classes</s> David Hubner is the new maintainer and he introduced a new solid-based device listing kcm

* Find maintainers for KCMs
** (System Settings is maintained as of 4.3. Complete rewrite)

* Find a maintainer for KPPP

* Find a maintainer for KsCD

* Find a maintainer for [http://cervisia.kde.org Cervisia]

* Find a maintainer for SuperKaramba? (or deprecate it?)

* Maintainer for KFloppy [replace it using DeviceKit by WindowsUninstall]

* Maintainer for KDETv

* Maintainer for [http://games.kde.org/game.php?game=kiriki Kiriki]

* <s>General maintainer for kde-bluetooth</s> [afiestas]

* KWeather (kdetoys) could be removed

====Maintained====

* KScreenSaver + PowerDevil conflicts (dafre?)

* kdelibs and kdebase
** Remove the use of Qt3/KDE3 classes
*** <s>Screensaver KCM</s> Implemented by DarioAndres
** Do not use own deprecated API
** Krazy2 fixes

* KDE apps
** <s>Don't use old icons (kappfinder)</s> App moved to extragear...

* Plasma fixes
** <s>Kickoff should not delete all the setting when switching from/to Classical/Kickoff mode (patch proposed at http://reviewboard.kde.org/r/2923/)</s> patch is committed.

* Kopete
** IRC Support
** More developers needed!

* Konqueror
** Search bar plugin assignee

* System Settings
** Reorganize the KCM categories to follow some logic: (http://forum.kde.org/brainstorm.php#idea54187 , http://forum.kde.org/brainstorm.php#idea40210 , {{bug|157587}}
*** -> http://techbase.kde.org/User:DarioAndres/SystemSettingWork

* Plasmoid resizing issues:
http://techbase.kde.org/Projects/Plasma/Plasmoid-Issues
--[[User:Finex|FiNeX]] 22:34, 11 September 2009 (UTC)

* KEditBookmarks is very buggy. (it got some fixes lately so it should be more stable, however I still think a person was doing a rewrite...)

* KMenuEditor should be ported to not use Q3/K3 classes

* KHelpCenter needs to be ported to not use Q3/K3 classes

===Bugtracker: bugs.kde.org===

* Clean assignees (ping Nightrose) [Dario_Andres is working on it]
** -> and... http://techbase.kde.org/User:DarioAndres/BugzillaCleanup
* Close KDE3 unmaintained crash reports of apps which have a KDE4 version:
** Kaffeine?
* Find assigne person/ML for "kde" product
* Test bug reports and write steps/testcases
* Check old kde3 bug reports against their Kde4 versions and close/(or move to the proper category if needed)
** kde, kdelibs, kio
** kcontrol/systemsettings-kde3 -> systemsettings
** <s>kicker-> plasma</s>
*** [[user:finex|FiNeX]] : http://techbase.kde.org/Contribute/Kicker-bugs
** kpdf -> okular
** konqueror/filebrowsing -> dolphin
*** [[user:finex|FiNeX]] : I'm working on this.
* <s>Create a product for kinfocenter with its kcm_modules as components</s> Product created and reassigned to its new maintainer
* <s>(In progress) Reassign "k3b" to mandriva people too? [there is a new CC for k3b besides trueg]</s> New maintainer

===Other===
* [http://techbase.kde.org/User:DarioAndres/KDESCCodeCleanup KDESCCodeCleanup]

Contribute/Bugsquad/BugDays/Beta46Week2

2010-12-10T17:55:07Z

DarioAndres: /* Division of Labour */

The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)

{{note|Additions to this wikipage welcome :)}}

==Introduction==

===Goals of this Week===
This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.

===Prerequisites===
You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.

====LiveCD====
Some packagers provide LiveCD/DVDs to faciliate testing:
* KDE Four Live (openSUSE) - http://home.kde.org/~kdelive
* openSUSE's KDE repository - http://download.opensuse.org/repositories/KDE:/Medias/images/iso/
* Fedora [http://fedoraproject.org/wiki/Rawhide Rawhide], [http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ nightly live image]

====Packages====
For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:
* '''Gentoo''' (KDE overlay) - [http://kde.gentoo.org/kde4-guide.xml#snapshots Gentoo KDE Guide]
* '''OpenSUSE''' packages [http://en.opensuse.org/Portal:KDE are available] for openSUSE 11.3 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.3/KDE4-BASIS.ymp one-click install]), for openSUSE 11.2 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.2/KDE4-BASIS.ymp one-click install]), and openSUSE Factory ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_Factory/KDE4-BASIS.ymp one-click install]).
* '''Archlinux''' [https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Using_the_kde-unstable_repository 4.6 beta]
* '''Fedora''' [http://fedoraproject.org/wiki/Rawhide Rawhide] already includes 4.6beta, Fedora 14 packages are available in the kde-unstable repository hosted by the [http://kde-redhat.sourceforge.net kde-redhat project].

====Sources====
If there are no packages for your distribution, you can always build KDE. [http://techbase.kde.org/Getting_Started/Build/kdesrc-build#Download_and_install_kdesrc-build kdesrc-build] is a nice way to get the newest code and have it compiled for you. Be sure to get the [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kdesrc-buildrc-sample sample rc from trunk].

===Is it a big bug?===
Prioritizing is good. If a major application doesn't work, this should be taken care of.

===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>

==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 give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.
{|
|-
!IRC Nickname !! KDE version used for testing !! Distribution
|-
|}

==Details==

Please select a batch of bugs from the [[#Division_of_Labour|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.'''

===Hints===
* Take note of bugs with '''high priority''' and put them in the section titled [[#High_priority_bugs|High priority bugs]].
* 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 will only be reproducible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eyes principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].

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

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=252927&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253032 Query]
|-
| 2 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253104&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253172 Query]
|-
| 3 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253207&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253551 Query]
|-
| 4 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253680&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253881 Query]
|-
| 5 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253923&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254119 Query]
|-
| 6 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254132&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254255 Query]
|-
| 7 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254394&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254539 Query]
|-
| 8 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254539&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254638 Query]
|-
| 9 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254749&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254908 Query]
|-
| 10 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254927&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254992 Query]
|-
| 11 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255075&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=255184 Query]
|-
| 12 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255236&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=255396 Query]
|-
| 13 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255463&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=255886 Query]
|-
| 14 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256198 Query]
|-
| 15 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256285&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256365 Query]
|-
| 16 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256388&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256628 Query]
|-
| 17 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256654&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256932 Query]
|-
| 18 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256982&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257137 Query]
|-
| 19 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257331&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257461 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257527&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257724 Query]
|-
| 21 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257723&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257890 Query]
|-
| 22 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257894&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257968 Query]
|-
| 23 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257976&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258070 Query]
|-
| 24 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258074&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258159 Query]
|-
| 25 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258160&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258216 Query]
|-
| 26 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258253&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258341 Query]
|-
| 27 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258341&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258408 Query]
|-
| 28 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258429&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258473 Query]
|-
| 29 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258475&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258532 Query]
|-
| 30 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258536&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258599 Query]
|-
| 31 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258598&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258636 Query]
|-
| 32 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258635&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258700 Query]
|-
| 33 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258738&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258827 Query]
|-
| 34 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258920&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258958 Query]
|-
| 35 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258958&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259048 Query]
|-
| 36 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259050&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259169 Query]
|-
| 37 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259177&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259202 Query]
|-
| 38 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259288&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259358 Query]
|-
| 39 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259357&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259423 Query]
|-
| 40 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259422&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259455 Query]
|}

''(total bugs: 199)''

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

{{:Contribute/Bugsquad/BugDays/Beta46Week1/High priority bugs}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing Version Field changed}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs with step-by-step Instructions}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as NEW}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing attention from developers}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing the reporter's feedback}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bug reports against performance issues}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Wishes}}

Contribute/Bugsquad/BugDays/Beta46Week2

2010-12-10T17:53:06Z

DarioAndres: /* Division of Labour */

The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)

{{note|Additions to this wikipage welcome :)}}

==Introduction==

===Goals of this Week===
This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.

===Prerequisites===
You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.

====LiveCD====
Some packagers provide LiveCD/DVDs to faciliate testing:
* KDE Four Live (openSUSE) - http://home.kde.org/~kdelive
* openSUSE's KDE repository - http://download.opensuse.org/repositories/KDE:/Medias/images/iso/
* Fedora [http://fedoraproject.org/wiki/Rawhide Rawhide], [http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ nightly live image]

====Packages====
For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:
* '''Gentoo''' (KDE overlay) - [http://kde.gentoo.org/kde4-guide.xml#snapshots Gentoo KDE Guide]
* '''OpenSUSE''' packages [http://en.opensuse.org/Portal:KDE are available] for openSUSE 11.3 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.3/KDE4-BASIS.ymp one-click install]), for openSUSE 11.2 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.2/KDE4-BASIS.ymp one-click install]), and openSUSE Factory ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_Factory/KDE4-BASIS.ymp one-click install]).
* '''Archlinux''' [https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Using_the_kde-unstable_repository 4.6 beta]
* '''Fedora''' [http://fedoraproject.org/wiki/Rawhide Rawhide] already includes 4.6beta, Fedora 14 packages are available in the kde-unstable repository hosted by the [http://kde-redhat.sourceforge.net kde-redhat project].

====Sources====
If there are no packages for your distribution, you can always build KDE. [http://techbase.kde.org/Getting_Started/Build/kdesrc-build#Download_and_install_kdesrc-build kdesrc-build] is a nice way to get the newest code and have it compiled for you. Be sure to get the [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kdesrc-buildrc-sample sample rc from trunk].

===Is it a big bug?===
Prioritizing is good. If a major application doesn't work, this should be taken care of.

===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>

==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 give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.
{|
|-
!IRC Nickname !! KDE version used for testing !! Distribution
|-
|}

==Details==

Please select a batch of bugs from the [[#Division_of_Labour|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.'''

===Hints===
* Take note of bugs with '''high priority''' and put them in the section titled [[#High_priority_bugs|High priority bugs]].
* 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 will only be reproducible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eyes principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].

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

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=252927&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253032 Query]
|-
| 2 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253104&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253172 Query]
|-
| 3 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253207&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253551 Query]
|-
| 4 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253680&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=253881 Query]
|-
| 5 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=253923&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254119 Query]
|-
| 6 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254132&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254255 Query]
|-
| 7 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254394&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254539 Query]
|-
| 8 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254539&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254638 Query]
|-
| 9 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254749&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254908 Query]
|-
| 10 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=254927&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=254992 Query]
|-
| 11 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255075&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=255184 Query]
|-
| 12 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255236&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=255396 Query]
|-
| 13 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255463&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=255886 Query]
|-
| 14 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256198 Query]
|-
| 15 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256285&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256365 Query]
|-
| 16 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256388&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256628 Query]
|-
| 17 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256654&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256932 Query]
|-
| 18 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256982&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257137 Query]
|-
| 19 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257331&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257461 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257527&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257724 Query]
|-
| 21 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257723&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257890 Query]
|-
| 22 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257894&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257968 Query]
|-
| 23 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257976&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258070 Query]
|-
| 24 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258074&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258159 Query]
|-
| 25 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258160&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258216 Query]
|-
| 26 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258253&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258341 Query]
|-
| 27 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258341&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258408 Query]
|-
| 28 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258429&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258473 Query]
|-
| 29 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258475&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258532 Query]
|-
| 30 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258536&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258599 Query]
|-
| 31 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258598&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258636 Query]
|-
| 32 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258635&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258700 Query]
|-
| 33 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258738&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258827 Query]
|-
| 34 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258920&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258958 Query]
|-
| 35 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258958&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259048 Query]
|-
| 36 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259050&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259169 Query]
|-
| 37 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259177&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259202 Query]
|-
| 38 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259288&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259358 Query]
|-
| 39 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259357&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259423 Query]
|-
| 40 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259422&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259455 Query]
|}

''(total bugs: 199)''

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

{{:Contribute/Bugsquad/BugDays/Beta46Week1/High priority bugs}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing Version Field changed}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs with step-by-step Instructions}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as NEW}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing attention from developers}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing the reporter's feedback}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bug reports against performance issues}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Wishes}}

Contribute/Bugsquad/BugDays/Beta46Week2

2010-12-10T17:27:05Z

DarioAndres: /* Division of Labour */

The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)

{{note|Additions to this wikipage welcome :)}}

==Introduction==

===Goals of this Week===
This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.

===Prerequisites===
You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.

====LiveCD====
Some packagers provide LiveCD/DVDs to faciliate testing:
* KDE Four Live (openSUSE) - http://home.kde.org/~kdelive
* openSUSE's KDE repository - http://download.opensuse.org/repositories/KDE:/Medias/images/iso/
* Fedora [http://fedoraproject.org/wiki/Rawhide Rawhide], [http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ nightly live image]

====Packages====
For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:
* '''Gentoo''' (KDE overlay) - [http://kde.gentoo.org/kde4-guide.xml#snapshots Gentoo KDE Guide]
* '''OpenSUSE''' packages [http://en.opensuse.org/Portal:KDE are available] for openSUSE 11.3 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.3/KDE4-BASIS.ymp one-click install]), for openSUSE 11.2 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.2/KDE4-BASIS.ymp one-click install]), and openSUSE Factory ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_Factory/KDE4-BASIS.ymp one-click install]).
* '''Archlinux''' [https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Using_the_kde-unstable_repository 4.6 beta]
* '''Fedora''' [http://fedoraproject.org/wiki/Rawhide Rawhide] already includes 4.6beta, Fedora 14 packages are available in the kde-unstable repository hosted by the [http://kde-redhat.sourceforge.net kde-redhat project].

====Sources====
If there are no packages for your distribution, you can always build KDE. [http://techbase.kde.org/Getting_Started/Build/kdesrc-build#Download_and_install_kdesrc-build kdesrc-build] is a nice way to get the newest code and have it compiled for you. Be sure to get the [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kdesrc-buildrc-sample sample rc from trunk].

===Is it a big bug?===
Prioritizing is good. If a major application doesn't work, this should be taken care of.

===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>

==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 give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.
{|
|-
!IRC Nickname !! KDE version used for testing !! Distribution
|-
|}

==Details==

Please select a batch of bugs from the [[#Division_of_Labour|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.'''

===Hints===
* Take note of bugs with '''high priority''' and put them in the section titled [[#High_priority_bugs|High priority bugs]].
* 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 will only be reproducible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eyes principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].

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

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255884&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=255990 Query]
|-
| 2 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255994&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256334 Query]
|-
| 3 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256339&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256560 Query]
|-
| 4 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256565&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256810 Query]
|-
| 5 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256819&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256932 Query]
|-
| 6 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256945&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257124 Query]
|-
| 7 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257135&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257353 Query]
|-
| 8 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257361&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257652 Query]
|-
| 9 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257653&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257724 Query]
|-
| 10 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257723&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257890 Query]
|-
| 11 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257894&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257955 Query]
|-
| 12 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257962&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257973 Query]
|-
| 13 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257975&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257986 Query]
|-
| 14 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258000&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258048 Query]
|-
| 15 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258053&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258118 Query]
|-
| 16 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258136&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258164 Query]
|-
| 17 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258165&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258259 Query]
|-
| 18 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258283&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258343 Query]
|-
| 19 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258350&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258390 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258389&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258439 Query]
|-
| 21 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258448&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258480 Query]
|-
| 22 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258510&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258545 Query]
|-
| 23 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258546&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258600 Query]
|-
| 24 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258602&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258637 Query]
|-
| 25 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258639&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258700 Query]
|-
| 26 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258738&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258778 Query]
|-
| 27 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258788&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258924 Query]
|-
| 28 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258925&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258958 Query]
|-
| 29 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258958&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259048 Query]
|-
| 30 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259050&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259057 Query]
|-
| 31 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259057&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259084 Query]
|-
| 32 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259086&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259106 Query]
|-
| 33 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259150&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259175 Query]
|-
| 34 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259177&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259202 Query]
|-
| 35 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259209&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259294 Query]
|-
| 36 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259296&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259359 Query]
|-
| 37 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259390&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259424 Query]
|-
| 38 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259429&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259455 Query]
|}

''(total bugs: 189)''

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

{{:Contribute/Bugsquad/BugDays/Beta46Week1/High priority bugs}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing Version Field changed}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs with step-by-step Instructions}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as NEW}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing attention from developers}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing the reporter's feedback}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bug reports against performance issues}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Wishes}}

Contribute/Bugsquad/BugDays/Beta46Week2

2010-12-10T16:34:42Z

DarioAndres: /* Division of Labour */

The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)

{{note|Additions to this wikipage welcome :)}}

==Introduction==

===Goals of this Week===
This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.

===Prerequisites===
You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.

====LiveCD====
Some packagers provide LiveCD/DVDs to faciliate testing:
* KDE Four Live (openSUSE) - http://home.kde.org/~kdelive
* openSUSE's KDE repository - http://download.opensuse.org/repositories/KDE:/Medias/images/iso/
* Fedora [http://fedoraproject.org/wiki/Rawhide Rawhide], [http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ nightly live image]

====Packages====
For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:
* '''Gentoo''' (KDE overlay) - [http://kde.gentoo.org/kde4-guide.xml#snapshots Gentoo KDE Guide]
* '''OpenSUSE''' packages [http://en.opensuse.org/Portal:KDE are available] for openSUSE 11.3 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.3/KDE4-BASIS.ymp one-click install]), for openSUSE 11.2 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.2/KDE4-BASIS.ymp one-click install]), and openSUSE Factory ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_Factory/KDE4-BASIS.ymp one-click install]).
* '''Archlinux''' [https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Using_the_kde-unstable_repository 4.6 beta]
* '''Fedora''' [http://fedoraproject.org/wiki/Rawhide Rawhide] already includes 4.6beta, Fedora 14 packages are available in the kde-unstable repository hosted by the [http://kde-redhat.sourceforge.net kde-redhat project].

====Sources====
If there are no packages for your distribution, you can always build KDE. [http://techbase.kde.org/Getting_Started/Build/kdesrc-build#Download_and_install_kdesrc-build kdesrc-build] is a nice way to get the newest code and have it compiled for you. Be sure to get the [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kdesrc-buildrc-sample sample rc from trunk].

===Is it a big bug?===
Prioritizing is good. If a major application doesn't work, this should be taken care of.

===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>

==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 give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.
{|
|-
!IRC Nickname !! KDE version used for testing !! Distribution
|-
|}

==Details==

Please select a batch of bugs from the [[#Division_of_Labour|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.'''

===Hints===
* Take note of bugs with '''high priority''' and put them in the section titled [[#High_priority_bugs|High priority bugs]].
* 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 will only be reproducible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eyes principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].

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

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255885&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256152 Query]
|-
| 2 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256197&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256389 Query]
|-
| 3 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256559&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256820 Query]
|-
| 4 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256837&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257017 Query]
|-
| 5 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257021&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257352 Query]
|-
| 6 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257362&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257655 Query]
|-
| 7 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257711&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257869 Query]
|-
| 8 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257889&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257963 Query]
|-
| 9 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257979 Query]
|-
| 10 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257984&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258047 Query]
|-
| 11 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258054&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258157 Query]
|-
| 12 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258158&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258254 Query]
|-
| 13 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258258&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258351 Query]
|-
| 14 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258354&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258430 Query]
|-
| 15 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258432&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258479 Query]
|-
| 16 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258511&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258551 Query]
|-
| 17 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258556&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258635 Query]
|-
| 18 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258636&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258739 Query]
|-
| 19 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258750&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258826 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258921&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258957 Query]
|-
| 21 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258959&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259052 Query]
|-
| 22 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259054&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259081 Query]
|-
| 23 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259083&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259151 Query]
|-
| 24 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259152&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259198 Query]
|-
| 25 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259199&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259293 Query]
|-
| 26 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259297&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259392 Query]
|-
| 27 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259421&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259454 Query]
|}

''(total bugs: 189)''

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

{{:Contribute/Bugsquad/BugDays/Beta46Week1/High priority bugs}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing Version Field changed}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs with step-by-step Instructions}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as NEW}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing attention from developers}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing the reporter's feedback}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bug reports against performance issues}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Wishes}}

Contribute/Bugsquad/BugDays/Beta46Week2

2010-12-10T16:33:45Z

DarioAndres: /* Division of Labour */

The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)

{{note|Additions to this wikipage welcome :)}}

==Introduction==

===Goals of this Week===
This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.

===Prerequisites===
You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.

====LiveCD====
Some packagers provide LiveCD/DVDs to faciliate testing:
* KDE Four Live (openSUSE) - http://home.kde.org/~kdelive
* openSUSE's KDE repository - http://download.opensuse.org/repositories/KDE:/Medias/images/iso/
* Fedora [http://fedoraproject.org/wiki/Rawhide Rawhide], [http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ nightly live image]

====Packages====
For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:
* '''Gentoo''' (KDE overlay) - [http://kde.gentoo.org/kde4-guide.xml#snapshots Gentoo KDE Guide]
* '''OpenSUSE''' packages [http://en.opensuse.org/Portal:KDE are available] for openSUSE 11.3 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.3/KDE4-BASIS.ymp one-click install]), for openSUSE 11.2 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.2/KDE4-BASIS.ymp one-click install]), and openSUSE Factory ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_Factory/KDE4-BASIS.ymp one-click install]).
* '''Archlinux''' [https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Using_the_kde-unstable_repository 4.6 beta]
* '''Fedora''' [http://fedoraproject.org/wiki/Rawhide Rawhide] already includes 4.6beta, Fedora 14 packages are available in the kde-unstable repository hosted by the [http://kde-redhat.sourceforge.net kde-redhat project].

====Sources====
If there are no packages for your distribution, you can always build KDE. [http://techbase.kde.org/Getting_Started/Build/kdesrc-build#Download_and_install_kdesrc-build kdesrc-build] is a nice way to get the newest code and have it compiled for you. Be sure to get the [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kdesrc-buildrc-sample sample rc from trunk].

===Is it a big bug?===
Prioritizing is good. If a major application doesn't work, this should be taken care of.

===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>

==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 give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.
{|
|-
!IRC Nickname !! KDE version used for testing !! Distribution
|-
|}

==Details==

Please select a batch of bugs from the [[#Division_of_Labour|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.'''

===Hints===
* Take note of bugs with '''high priority''' and put them in the section titled [[#High_priority_bugs|High priority bugs]].
* 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 will only be reproducible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eyes principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].

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

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=255885&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256152 Query]
|-
| 2 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256197&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256389 Query]
|-
| 3 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256559&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=256820 Query]
|-
| 4 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=256837&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257017 Query]
|-
| 5 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257021&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257352 Query]
|-
| 6 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257362&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257655 Query]
|-
| 7 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257711&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257869 Query]
|-
| 8 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257889&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257963 Query]
|-
| 9 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=257979 Query]
|-
| 10 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=257984&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258047 Query]
|-
| 11 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258054&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258157 Query]
|-
| 12 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258158&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258254 Query]
|-
| 13 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258258&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258351 Query]
|-
| 14 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258354&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258430 Query]
|-
| 15 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258432&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258479 Query]
|-
| 16 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258511&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258551 Query]
|-
| 17 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258556&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258635 Query]
|-
| 18 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258636&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258739 Query]
|-
| 19 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258750&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258826 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258921&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=258957 Query]
|-
| 21 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=258959&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259052 Query]
|-
| 22 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259054&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259081 Query]
|-
| 23 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259083&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259151 Query]
|-
| 24 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259152&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259198 Query]
|-
| 25 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259199&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259293 Query]
|-
| 26 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259297&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259392 Query]
|-
| 27 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdepim&product=kdepimlibs&product=akonadi&product=kmail&product=kmail2&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&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&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=259421&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=259454 Query]
|}

''(total bugs: 0)''

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

{{:Contribute/Bugsquad/BugDays/Beta46Week1/High priority bugs}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing Version Field changed}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs with step-by-step Instructions}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs to be marked as NEW}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing attention from developers}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing the reporter's feedback}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bug reports against performance issues}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/Beta46Week1/Wishes}}

User:DarioAndres/BKoResurrection

2010-11-15T14:52:23Z

DarioAndres: Created page with 'ToDo: * Marking a bug as duplicate (and the added message on the parent report) shouldn't send emails to all the people in the CC. This usually causes a lot of spam to the repor...'

ToDo:

* Marking a bug as duplicate (and the added message on the parent report) shouldn't send emails to all the people in the CC. This usually causes a lot of spam to the reporter of the original issue (who cannot unsuscribe); and the other CCed people wanting to leave the report. This frustrate bug reporters and make them leave, so if we need really important information we are not going to be able to reach them.

* Bug triagers comments in the bug reports could start as:
[Bug triager comment]
This way the people can easily check that this is an administrative message to tidy up things. (but it could have useful information)

Contribute/Bugsquad

2010-05-22T13:42:50Z

DarioAndres: /* How to help */

[[File:Bugweeks_ladybug.png]]

==What is BugSquad?==

The '''KDE BugSquad''' keeps track of incoming bugs in KDE software, and goes through old bugs. We verify that a bug exists, and is reproducible, and that the reporter has given enough information. When applicable, we write testcases. ''Our end goal is to help developers notice valid bugs quicker, and to save their time.''

You do not need any programming knowledge to be in the Bugsquad, and it is a great way to give practical support to the KDE community. If you are just starting to learn programming, it is a great way to gain familiarity with the components.

==Bug Days==

We have regular days where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla cleaning day.

{{:Contribute/Bugsquad/NextBugDay}}

The results of all past bug days can be found [[/BugDays|here]].

===Bug Weeks===

Our team has recently launched a new iniciative named "Bug Weeks", as an evolution of the traditional BugDays. All the workflow is based on the [http://forum.kde.org/ KDE Community Forums].

You can find more information about it at [http://forum.kde.org/viewtopic.php?f=4&t=84473 its official announcement]

The first bugweek was about triaging Plasma Desktop bug reports. You can find more information in the [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek Session 0 article]. (A summary article is yet to come)

{{note|We don't just do bugs on BugDays! Don't hesitate to join us at '''#kde-bugs''' on irc.freenode.net, we have plenty for you to do. ;) Check the topic to see what we are currently working on. And if you are new, please read the "how to triage bugs" page.}}

==How to help==

Read the [[/Guide_To_BugTriaging|ultimate guide to BugTriaging for KDE Projects]] (Recommended)

or ...

Read this [[/Guide|guide]] and join us for one of our [[#Bug_Days|bug days]] or [[#Bug_Weeks|bug weeks]]. We meet on IRC in the #kde-bugs channel on irc.freenode.org. You can easily get started by having your questions answered there, and having someone guide you as to general bug triaging philosophy. Someone in IRC will usually be able to help you. Although we do sleep sometimes!

A summary of the BugSquad guide is provided below to give you a quick idea of how you can help:

* Confirming bugs. Bugs with the UNCONFIRMED status should get the NEW status once someone else is able to reproduce the bug reliably.
* Finding bug duplicates. Many bugs entered into Bugzilla are duplicates of other bugs. Sometimes it's hard to recognize these as duplicates but multiple people checking can make the duplicates bubble to the top of the pile. The following remarks may help you identifying them:
** Using the Similar Bugs link to look if there are duplicates.
** In the case of crashes, use the link below the comment field to look for crash reports with the same backtrace. The backtrace must be in the body of the report in order to look for similar reports. This tool does not look in attachments with backtraces.
* Close bugs which have insufficient information and which have been open for a long time (e.g. reporter does not respond to a need-more-info request). Usually a timeout of one month or more is considered to be an "information timeout".
* Categorize bugs into the right components. Many bug reports can be further categorized into components. For example, Konqueror reports can be assigned to KHTML and kfm components.
* Labeling bugs which contain testcases as such in the title. Ideally, testcases contain the minimal amount of code (HTML, scripts, C++ etc.) necessary to reproduce a bug.
* Writing testcases. Very useful and saves developers' time.

==Getting started==
The sheer number of open bugs can be overwhelming at the start. Here are some hints on getting started more smoothly:
* Look at a single product at a time. For large applications (like Konqueror), you may want to further limit your search to a particular component.
* Don't try to find duplicates early on. Finding duplicates is hard until you have become familiar with the bugs in a component. Start out with verifying UNCONFIRMED bugs as described above. That's valuable work, and a great way to familiarize yourself with the bug database.
* Avoid very old bugs with many comments, and also bugs with many votes. This may seem counter-intuitive, but in most cases these bugs are hard, have gotten a lot of attention, and are probably on a developer's TODO list already. If it is from an older version of KDE, and there are no recent comments, verify them, make a notation, and move on.
* Don't be afraid to ask the reporter for more info. It's something you can even do without Bugzilla permissions. And reporters will generally prefer being asked one question too many, instead of their report never being dealt with. Just remember to be polite. Ask yourself how you would feel if you got the message you are thinking about sending to a user.
* Look at the incoming Bugzilla bugs. Or find the oldest bugs for your favorite software application.
* Look through the rest of our documentation for more information!

==Articles==

* [[/Guide_To_BugTriaging|Dario's Guide to Bug Triaging]] - Extensive guide on how to perform bug triagers tasks

* [[/Quick_Introduction_to_Bugzilla|Quick introduction to Bugzilla]] - This article explains the basics about the bugtracking software that KDE uses: "Bugzilla". It includes the description of a bug reports fields and the workflow of most common tasks like searching into the databse.

* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle] - This article describes the possible status of a bug report and when each should be used.

* [[/How to triage bugs|How to triage bugs]] - This article gives step-by-step what you do during a BugDay, or how to start triaging on your own in our "ongoing triage" (usually for old Konqueror bugs; see #kde-bugs for the current link).

* [[Projects/SystemSettings#Bug_Triaging|How to triage System Settings bugs]] - Explains how System Settings works from a bug squasher's perspective.

* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment] - This article from the BugWeeks initiative describes how to properly configure and setup a KDE SC environment in order to test the bugs.

* [[/How to create useful crash reports|How to create useful crash reports]] - This article helps users to prepare their KDE packages such they can create detailed backtraces.

* [[User:DarioAndres/Basic_Guide_about_Crash_Reporting|Basic guide about crash reports]] - This article is a basic/simplified version of the previous one.

==External links==
*[http://bugs.kde.org/ Bug Tracker]
*[http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&bugidtype=include&bug_id=&votes=100&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&newqueryname=&order=bugs.votes,bugs.priority%2C%20bugs.bug_severity%2C%20bugs.bug_status%2C%20bugs.bug_id%20desc Feature Requests, sorted by popularity]
*[https://mail.kde.org/mailman/listinfo/bugsquad Subscribe to our mailinglist]
*[http://forum.kde.org/viewforum.php?f=148 BugWeeks subforum]

Contribute/ImportantWorkToBeDone

2010-04-11T13:34:05Z

DarioAndres: /* Bugtracker: bugs.kde.org */

===General===

* FIXME comments: http://lxr.kde.org/search?filestring=cpp&string=%2F%2FFIXME
* TODO comments: http://lxr.kde.org/search?filestring=cpp&string=%2F%2FTODO
* Warning compiler comments: http://lxr.kde.org/search?filestring=cpp&string=%23warning

===KDE technologies===

* KDELIBS
** Update KBugReport to use the new enterbug form (which replaces the wizard)
** Improve the KBugReport UI dialog, improve the app/component selection

* Phonon
** <s>(In progress) Get someone to review phonon bug reports on BKO; or submit them upstream</s> [sandsmark]
** More collaboration/connection between KDE and Qt teams about this technology
** <s>Pulseaudio mess</s> Fixed in latest Phonon

* Solid
** <s>(In progress) Solid-bluetooth needs a maintainer</s> [afiestas got the maintainership of kbluetooth]

* Other
** libkcddb needs a maintainer

===KDE applications===

====Unmaintained====

* KThemeManager could be removed from the code (kdebase/workspace/kcontrol)

* Find a maintainer for KFind
** It needs a rewrite/check of some parts (to not use Process events)
** Improve UI / Extract to UI file
** Strigi/Nepomuk integration
** <s>KFindPart should be removed (unused according to lxr.kde.org)</s> Done for KDESC4.5

* Find a maintainer for KWikdisk/KDiskFree [sandmark has suggest to replace those apps with filelight]
** Integrate Solid devices
** More portable / system-independant code
** Fixes on the treewidget and model implementation

* Find a maintainer for KSystraycmd
** Port to the new systray icon library

* Find a maintainer for DragonPlayer [eean is the official maintainer, sandsmark is willing to accept bug reports]

* Find a maintainer for KolourPaint

* Find a maintainer for KRFB (or remove/replace it) [grundleborg?]
* <s>Find a maintainer for KInfoCenter?
** Some modules need porting to Qt4 classes</s> David Hubner is the new maintainer and he introduced a new solid-based device listing kcm

* Find maintainers for KCMs
** (System Settings is maintained as of 4.3. Complete rewrite)

* Find a maintainer for KPPP

* Find a maintainer for KsCD

* Find a maintainer for [http://cervisia.kde.org Cervisia]

* Find a maintainer for SuperKaramba? (or deprecate it?)

* Maintainer for KFloppy [replace it using DeviceKit by WindowsUninstall]

* Maintainer for KDETv

* Maintainer for [http://games.kde.org/game.php?game=kiriki Kiriki]

* <s>General maintainer for kde-bluetooth</s> [afiestas]

* KWeather (kdetoys) could be removed

====Maintained====

* KScreenSaver + PowerDevil conflicts (dafre?)

* kdelibs and kdebase
** Remove the use of Qt3/KDE3 classes
*** <s>Screensaver KCM</s> Implemented by DarioAndres
** Do not use own deprecated API
** Krazy2 fixes

* KDE apps
** <s>Don't use old icons (kappfinder)</s> App moved to extragear...

* Plasma fixes
** Kickoff should not delete all the setting when switching from/to Classical/Kickoff mode (patch proposed at http://reviewboard.kde.org/r/2923/)

* Kopete
** IRC Support
** More developers needed!

* Konqueror
** Search bar plugin assignee

* System Settings
** Reorganize the KCM categories to follow some logic: (http://forum.kde.org/brainstorm.php#idea54187 , http://forum.kde.org/brainstorm.php#idea40210 , {{bug|157587}}
*** -> http://techbase.kde.org/User:DarioAndres/SystemSettingWork

* Plasmoid resizing issues:
http://techbase.kde.org/Projects/Plasma/Plasmoid-Issues
--[[User:Finex|FiNeX]] 22:34, 11 September 2009 (UTC)

* KEditBookmarks is very buggy. (it got some fixes lately so it should be more stable, however I still think a person was doing a rewrite...)

* KMenuEditor should be ported to not use Q3/K3 classes

* KHelpCenter needs to be ported to not use Q3/K3 classes

===Bugtracker: bugs.kde.org===

* Clean assignees (ping Nightrose) [Dario_Andres is working on it]
** -> and... http://techbase.kde.org/User:DarioAndres/BugzillaCleanup
* Close KDE3 unmaintained crash reports of apps which have a KDE4 version:
** Kaffeine?
* Find assigne person/ML for "kde" product
* Test bug reports and write steps/testcases
* Check old kde3 bug reports against their Kde4 versions and close/(or move to the proper category if needed)
** kde, kdelibs, kio
** kcontrol/systemsettings-kde3 -> systemsettings
** <s>kicker-> plasma</s>
*** [[user:finex|FiNeX]] : http://techbase.kde.org/Contribute/Kicker-bugs
** kpdf -> okular
** konqueror/filebrowsing -> dolphin
*** [[user:finex|FiNeX]] : I'm working on this.
* <s>Create a product for kinfocenter with its kcm_modules as components</s> Product created and reassigned to its new maintainer
* <s>(In progress) Reassign "k3b" to mandriva people too? [there is a new CC for k3b besides trueg]</s> New maintainer

===Other===
* [http://techbase.kde.org/User:DarioAndres/KDESCCodeCleanup KDESCCodeCleanup]

Contribute/Bugsquad

2010-04-10T12:19:47Z

DarioAndres: /* Articles */

[[File:Bugweeks_ladybug.png]]

==What is BugSquad?==

The '''KDE BugSquad''' keeps track of incoming bugs in KDE software, and goes through old bugs. We verify that a bug exists, and is reproducible, and that the reporter has given enough information. When applicable, we write testcases. ''Our end goal is to help developers notice valid bugs quicker, and to save their time.''

You do not need any programming knowledge to be in the Bugsquad, and it is a great way to give practical support to the KDE community. If you are just starting to learn programming, it is a great way to gain familiarity with the components.

==Bug Days==

We have regular days where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla cleaning day.

{{:Contribute/Bugsquad/NextBugDay}}

The results of all past bug days can be found [[/BugDays|here]].

===Bug Weeks===

Our team has recently launched a new iniciative named "Bug Weeks", as an evolution of the traditional BugDays. All the workflow is based on the [http://forum.kde.org/ KDE Community Forums].

You can find more information about it at [http://forum.kde.org/viewtopic.php?f=4&t=84473 its official announcement]

The first bugweek was about triaging Plasma Desktop bug reports. You can find more information in the [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek Session 0 article]. (A summary article is yet to come)

{{note|We don't just do bugs on BugDays! Don't hesitate to join us at '''#kde-bugs''' on irc.freenode.net, we have plenty for you to do. ;) Check the topic to see what we are currently working on. And if you are new, please read the "how to triage bugs" page.}}

==How to help==
Read the [[/Guide|guide]] and join us for one of our [[#Bug_Days|bug days]] or [[#Bug_Weeks|bug weeks]]. We meet on IRC in the #kde-bugs channel on irc.freenode.org. You can easily get started by having your questions answered there, and having someone guide you as to general bug triaging philosophy. Someone in IRC will usually be able to help you. Although we do sleep sometimes!

A summary of the BugSquad guide is provided below to give you a quick idea of how you can help:

* Confirming bugs. Bugs with the UNCONFIRMED status should get the NEW status once someone else is able to reproduce the bug reliably.
* Finding bug duplicates. Many bugs entered into Bugzilla are duplicates of other bugs. Sometimes it's hard to recognize these as duplicates but multiple people checking can make the duplicates bubble to the top of the pile. The following remarks may help you identifying them:
** Using the Similar Bugs link to look if there are duplicates.
** In the case of crashes, use the link below the comment field to look for crash reports with the same backtrace. The backtrace must be in the body of the report in order to look for similar reports. This tool does not look in attachments with backtraces.
* Close bugs which have insufficient information and which have been open for a long time (e.g. reporter does not respond to a need-more-info request). Usually a timeout of one month or more is considered to be an "information timeout".
* Categorize bugs into the right components. Many bug reports can be further categorized into components. For example, Konqueror reports can be assigned to KHTML and kfm components.
* Labeling bugs which contain testcases as such in the title. Ideally, testcases contain the minimal amount of code (HTML, scripts, C++ etc.) necessary to reproduce a bug.
* Writing testcases. Very useful and saves developers' time.

==Getting started==
The sheer number of open bugs can be overwhelming at the start. Here are some hints on getting started more smoothly:
* Look at a single product at a time. For large applications (like Konqueror), you may want to further limit your search to a particular component.
* Don't try to find duplicates early on. Finding duplicates is hard until you have become familiar with the bugs in a component. Start out with verifying UNCONFIRMED bugs as described above. That's valuable work, and a great way to familiarize yourself with the bug database.
* Avoid very old bugs with many comments, and also bugs with many votes. This may seem counter-intuitive, but in most cases these bugs are hard, have gotten a lot of attention, and are probably on a developer's TODO list already. If it is from an older version of KDE, and there are no recent comments, verify them, make a notation, and move on.
* Don't be afraid to ask the reporter for more info. It's something you can even do without Bugzilla permissions. And reporters will generally prefer being asked one question too many, instead of their report never being dealt with. Just remember to be polite. Ask yourself how you would feel if you got the message you are thinking about sending to a user.
* Look at the incoming Bugzilla bugs. Or find the oldest bugs for your favorite software application.
* Look through the rest of our documentation for more information!

==Articles==

* [[/Guide_To_BugTriaging|Dario's Guide to Bug Triaging]] - Extensive guide on how to perform bug triagers tasks

* [[/Quick_Introduction_to_Bugzilla|Quick introduction to Bugzilla]] - This article explains the basics about the bugtracking software that KDE uses: "Bugzilla". It includes the description of a bug reports fields and the workflow of most common tasks like searching into the databse.

* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle] - This article describes the possible status of a bug report and when each should be used.

* [[/How to triage bugs|How to triage bugs]] - This article gives step-by-step what you do during a BugDay, or how to start triaging on your own in our "ongoing triage" (usually for old Konqueror bugs; see #kde-bugs for the current link).

* [[Projects/SystemSettings#Bug_Triaging|How to triage System Settings bugs]] - Explains how System Settings works from a bug squasher's perspective.

* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment] - This article from the BugWeeks initiative describes how to properly configure and setup a KDE SC environment in order to test the bugs.

* [[/How to create useful crash reports|How to create useful crash reports]] - This article helps users to prepare their KDE packages such they can create detailed backtraces.

* [[User:DarioAndres/Basic_Guide_about_Crash_Reporting|Basic guide about crash reports]] - This article is a basic/simplified version of the previous one.

==External links==
*[http://bugs.kde.org/ Bug Tracker]
*[http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&bugidtype=include&bug_id=&votes=100&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&newqueryname=&order=bugs.votes,bugs.priority%2C%20bugs.bug_severity%2C%20bugs.bug_status%2C%20bugs.bug_id%20desc Feature Requests, sorted by popularity]
*[https://mail.kde.org/mailman/listinfo/bugsquad Subscribe to our mailinglist]
*[http://forum.kde.org/viewforum.php?f=148 BugWeeks subforum]

Contribute/Bugsquad/Guide To BugTriaging

2010-04-08T12:59:17Z

DarioAndres: /* Bugs caused by external issues (UPSTREAM/DOWNSTREAM) */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year", or even from the very beggining (like 2000)). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 
{{Tip|You can search on different products at the same time}}

{{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

{{Note|The '''UPSTREAM''' resolution refers to bugs caused by libraries/dependencies, upstream in the software stack (like Qt, glibc, X11).
The '''DOWNSTREAM''' resolution refers to bug caused by the Distributions (broken packaging, ...) or by external plugins (unofficial Plasma widgets, other extensions, ...)}}

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

{{Note|If you don't get feedback after a period of time, you can mark the report as "NEEDSINFO" with resolution "WAITINGFORINFO" (or resolution "BACKTRACE" if you are waiting for a complete backtrace)}}

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

==Other Situations and Cases==

===One report per issue===

There is a policy in KDE bugtracker which establishes that different issues/bugs should not be mixed up in the same bug report, in order to keep the database clean and easy to read.

If any user adds information which is unrelated to the current bug report, gently tell him/her to write it down on a *different/new report. (The new issue described may be already reported somewhere else. In that case, you need to write a reference to the that bug report ID)

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]
* [http://aseigo.blogspot.com/2009/01/bugskdeorg.html aseigo's suggestions for bugs.kde.org]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-03T12:38:20Z

DarioAndres: /* Other Situations and Cases */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year", or even from the very beggining (like 2000)). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 
{{Tip|You can search on different products at the same time}}

{{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

{{Note|If you don't get feedback after a period of time, you can mark the report as "NEEDSINFO" with resolution "WAITINGFORINFO" (or resolution "BACKTRACE" if you are waiting for a complete backtrace)}}

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

==Other Situations and Cases==

===One report per issue===

There is a policy in KDE bugtracker which establishes that different issues/bugs should not be mixed up in the same bug report, in order to keep the database clean and easy to read.

If any user adds information which is unrelated to the current bug report, gently tell him/her to write it down on a *different/new report. (The new issue described may be already reported somewhere else. In that case, you need to write a reference to the that bug report ID)

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]
* [http://aseigo.blogspot.com/2009/01/bugskdeorg.html aseigo's suggestions for bugs.kde.org]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-03T12:33:21Z

DarioAndres: /* Handling reports: What to do with a bug report */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year", or even from the very beggining (like 2000)). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 
{{Tip|You can search on different products at the same time}}

{{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

{{Note|If you don't get feedback after a period of time, you can mark the report as "NEEDSINFO" with resolution "WAITINGFORINFO" (or resolution "BACKTRACE" if you are waiting for a complete backtrace)}}

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

==Other Situations and Cases==

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]
* [http://aseigo.blogspot.com/2009/01/bugskdeorg.html aseigo's suggestions for bugs.kde.org]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T17:53:47Z

DarioAndres: /* Useful Links */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year", or even from the very beggining (like 2000)). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 
{{Tip|You can search on different products at the same time}}

{{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

{{Note|If you don't get feedback after a period of time, you can mark the report as "NEEDSINFO" with resolution "WAITINGFORINFO" (or resolution "BACKTRACE" if you are waiting for a complete backtrace)}}

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]
* [http://aseigo.blogspot.com/2009/01/bugskdeorg.html aseigo's suggestions for bugs.kde.org]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T17:48:23Z

DarioAndres: /* Check the report quality (and ask for missing information) */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year", or even from the very beggining (like 2000)). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 
{{Tip|You can search on different products at the same time}}

{{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

{{Note|If you don't get feedback after a period of time, you can mark the report as "NEEDSINFO" with resolution "WAITINGFORINFO" (or resolution "BACKTRACE" if you are waiting for a complete backtrace)}}

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T17:31:44Z

DarioAndres: /* General */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year", or even from the very beggining (like 2000)). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 
{{Tip|You can search on different products at the same time}}

{{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T16:01:57Z

DarioAndres: /* Check bug reports of a single product over a period of time */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year", or even from the very beggining (like 2000)). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 {{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T15:33:29Z

DarioAndres: /* Special products and cases */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year"). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 {{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

* "systemsettings" contain bug reports of the Shell application SystemSettings and kcmshell4, and reports of the configuration modules "kcm_*"
** Try to identificate if the report is about the shell applications (and set the component to "general", "treeview" or "kcmshell") or about some of the configuration modules (and set the component to "kcm_*name*")

* Konqueror can use different engines, like KHTML or WebKit
** If the report is about a webkit-only issue, reassign to product "kdelibs", component "kdewebkit"

{{Tip|When updating the bugzilla product or component, do not forget to reset to the default assignee}}

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T15:25:37Z

DarioAndres: /* More Information */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year"). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 {{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Special products and cases==

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T15:23:35Z

DarioAndres: /* Avoiding useless function calls */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year"). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 {{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in a backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T15:22:25Z

DarioAndres: /* Processing search results */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year"). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 {{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one (resolve the duplicates chain). However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which one refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| qt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.

Contribute/Bugsquad/Guide To BugTriaging

2010-04-02T15:16:58Z

DarioAndres: /* Adding related people to the CC list */

Initial version by [[User:DarioAndres|Dario Andres]] (2010-03/2010-04).

Initial corrections by Lydia Pintscher (Nightrose)

===Disclaimer===

This "ultimate" guide is based on my own experience (approximately 2 years) on the KDE bug tracker.

I hope it works for you too :)

=General Considerations=

* '''Be polite''': when you need to request information or feedback be clear and polite, and you will get more information in less time.  Often Bugzilla is a place which involves discussions (about implementations, or even about contributors). Try to be concise and polite, respecting the others position while describing your own.

* Don't try to do too many things at the same time; otherwise you will end up with a headache.

If you are not familiar with the Bugzilla (KDE bug tracker system) interface, you may find this guide useful: [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick Introduction to Bugzilla]

You may want to properly setup your bugzilla account as mentioned at [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla#Configure_your_account_.28Important.29 Configure your account]

=About getting permissions to work in the bug tracker=

Manpower is always needed in a bug tracker, but as any action taken on it may be potentially destructive to other people's work; or it may end up messing things up (and consuming the developers' or other triager's time) the tracker requires special permissions to perform changes in bug reports.

If you want to work in the bug tracker you need to prove that you know what you are doing.

Initially you will ask for support on '''#kde-bugs''' (on IRC) and add comments in the bug report (so other people will see and check them, perform the needed actions, and evaluate your work)

{{Note|Adding comments in a bug report is allowed for every user}}

=Getting Started: Find what to work on (Different Approaches)=

You could use different techniques or approaches to triage the reports according to your current mood or the amount of work you want to do for example.

{{Tip|The two following techniques are complementary.}}

==Check all the bug reports of the day==

In this technique you check all the bug reports (of all the products) which were filed today (or some days ago).

You can focus on crash, normal or wish reports individually (recommended) or all of them together.

'''Good:'''
* You get a complete view of all the reports
* You can easily recognize possible duplicates if the report titles are appropriate
* You can choose any report
* You can quickly clean the bugs that were filed recently (keeping them from rotting)
* You can get quick feedback from the reporter

'''Not so Good:'''
* You don't focus on one product
* You may not pay too much attention to every report, as you are triaging different kinds of reports
* You need a lot of attention to handle the different reports (at the ~same~ time)

This technique could be used ''every week'' (or every day)

===Bugzilla Links===
* All the bugs ('''any type''') reported [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=1d&chfieldto=Now&bug_file_loc=&cmdtype=doit today] or the [https://bugs.kde.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bugidtype=include&chfield=%5BBug+creation%5D&chfieldfrom=7d&chfieldto=Now&bug_file_loc=&cmdtype=doit last week]
* All the '''crashes''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''normal bugs''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]
* All the '''feature requests''' reported [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=1d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= today] or the [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=7d&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= last week]

==Check bug reports of a single product over a period of time==

Choose a product (application or library). Then choose a period of time like 1 month or 1 or 2 years (or "from the beginning of the current year"). You can also choose which kind of reports you want to handle.

This technique is useful to audit old bugs or perform a deep clean (in case that the bugs weren't triaged on a daily basis previously).

'''Good:'''
* You focus only on one product / topic, so you don't need to pay too much attention (pay attention anyways!)

'''Not so Good:'''
* The reports of the other application may rot if they aren't checked
* You may not get feedback if the report is too old or the reporter is not accessible anymore

You can also filter out results (and be even more focused) if you select a custom component inside the product (a subsection of the application).

This technique could be used ''two times a month''.

===Bugzilla Links===

* Template search for all the reports of any status, since 2008: [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= any kind of report], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=crash&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/query.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bugidtype=include&chfield=%5BBug%20creation%5D&chfieldfrom=2008-01-01&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=bug_severity&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=plasma&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=plasma&value-1-1-0=crash&value0-0-0=&votes= feature requests]
* Template search for all the open reports, since 2008: [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= any kind of report], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crashes], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= normal bugs], [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=wishlist&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= feature requests]

=Workflow of the bug triaging activity=

Now that you have a list of bug reports, pick one and start working.

[[File:DarioAndres_GuideToBugTriaging_Workflow.png]]

=Handling reports: What to do with a bug report=

There are several things that must be checked and "fixed" to make an initial bug report an interesting and useful peace of information for the developers to check.

{{Note|if at any point you don't really know how to continue, because you don't understand the issue properly, always ask to the developers or related contributors}}

As KDE has too much users, we get a lot of reports about bugs which are already reported (the so named "duplicates"). Before putting any effort in the current report we should check for the main report.

==Identifying duplicates==

There are a lot of ways of identifying duplicate reports depending of the kind of bug.

===General===

* Search for duplicates should be done initially against the same product of the bug report you are triaging:  If you don't find any related issue, you may need to search in a different product.
 {{Note|Due to the heavy usage of libraries in the KDE software, a bug reported for an application may be being tracked at a library product (example, a bug in Plasma Desktop may be a bug in kdelibs, and therefore being tracked in the "kdelibs" product)}}

[http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies List of related KDE technologies]

* You may want to filter out the results by date: you can select a date range since some years (or months ago) to "Now" (today)

===For "normal" (non-crash) reports===

# Pick some "keywords" from the current report. This keywords need to explain the inner concept of the bug that was reported (they must represent it).
# Perform a full search over the same product (read general note), initially on the "general" component.  Initially, put the keywords in the title, and perform the search (this will only look for the keywords in the title)
# If your search has results on it, check them all, reading the whole description and trying to identify the situation.
# If you don't get any results, you need to go back and: 
#* Change your keywords (tip: select thesaurus, or similar/related concepts); or
#* Use the keywords in the "Comments" field (so the search will look up in the bug description and comments too)

{{Note|When using more than one word in the "Comments" field you need to select the option "contains all of the words/strings"}}

{{Note|It is sometimes difficult to choose the proper ones, as the way of describing a scene varies from person to person (but we have time)}}

===For "crash" reports===

# Perform the same operation as with normal bug reports
# Check for reports with duplicate backtraces:   (Read the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#C.2B.2B_Backtraces_.28identifying_crashes_duplicates.29 Backtraces section] below)

Perform a full search over the same product (read general note), initially on the "general" component, putting the "ClassName::FunctionName" pairs that identify the crash in the Comments field of the form (if you put more than one pair, you need to select the option "contains all of the words/strings")

===Processing search results===

* If you don't find any similar report then we should assume the new bug reports is "unique" (and valid). See next section 

* If you find a similar bug report we have too choices:
** If you are completely sure it is the same issue, you have to mark the report as duplicate.   The bug report you initially picked (name it "copy") is going to be marked as duplicate of the original report (name it "main"). If "copy" has additional information that "main" doesn't have, you may want to add it. (Note: some details may look unimportant to you, but they may be important for developers who know about the application workflow and code. Also, adding a big amount of minimal/incomplete information you may end up generating a big and complete testcase) 
** If you aren't completely sure: you need someone else to double check your work. You may want to add a comment in the current report. Then, you should ask in #kde-bugs IRC channel for someone to look at your comment.
Comment template:
This bug looks related to bug XXXXXX
(XXXXXX being the bug ID of "master")

{{Note|You may found related reports that are already marked as duplicate of a third report. Always try to use this third report as the "main" one. However, in some cases, the "main" reports refers to a root issue, and some of its duplicates may refer to sub-issues. In those cases try to check which refers to the issue you are looking at.}}

==Identifying duplicates (crashes) : C++ Backtraces==

===Definition===

A backtrace is a piece of information that describes what was the application doing when it encountered the error and had to close itself. It is a "function stack" leading to the "crashing point".

In KDE applications, the backtraces are generated by the Crash Handler Dialog ("DrKonqi"). They can also be generated by the general debugger "GDB", but that involves more steps.

The backtrace is read from top to bottom

The first line shows *where* the crash occurred (because of an illegal instruction, invalid pointer, memory problem or other issues)

The other lines show the "way to the first function"

===Example===

Application: Plasma Workspace (kdeinit4), signal: Bus error
[KCrash Handler]
#5 0x00007fb563bb8f02 in KPixmapCache::Private::mmapFile (this=0x92df60,
filename=..., info=0x92dfb0, newsize=33656832) at /usr/src/debug/kdelibs-
4.4.1/kdeui/util/kpixmapcache.cpp:491
#6 0x00007fb563be3c34 in KPixmapCache::Private::mmapFiles (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7 0x00007fb563be38e3 in KPixmapCache::Private::init (this=0x92df60) at
/usr/src/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8 0x00007fb563be576d in KPixmapCache::discard (this=0x1203ca0) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9 0x00007fb563be5e48 in KPixmapCache::deleteCache (name=...) at /usr/src
/debug/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007fb55afdc97d in Plasma::ThemePrivate::discardCache (this=0x7a7d30)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:224
#11 0x00007fb55afe009b in Plasma::ThemePrivate::setThemeName (this=0x7a7d30,
tempThemeName=<value optimized out>, writeSettings=<value optimized out>)
at /usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:380
#12 0x00007fb55afe19fb in Plasma::Theme::settingsChanged (this=0x70af20) at
/usr/src/debug/kdelibs-4.4.1/plasma/theme.cpp:341
#13 0x00007fb55afe2918 in Plasma::ThemePrivate::settingsFileChanged
(this=0x7a7d30, file=<value optimized out>) at /usr/src/debug/kdelibs-
4.4.1/plasma/theme.cpp:335
...

===Description of a backtrace line===

#NumberInTheStack MemoryAddress in Namespace::Class:FunctionMember
(argumentThis=pointerValue, argument1=value, argument2=value, ...) at path/to
/source/code/file.cpp:linenumber

* #NumberInTheStack: is the order number in the function stack. The lesser, the nearer to the crash point. The smaller number may not be zero
* MemoryAddress: we don't put attention to this one.. Ignore
* Namespace: C++ namespace of the function. It may not be available if there are no namespaces. This could be also a class name if "Class" is an embedded one.
* Class: C++ class name of the function
* FunctionMember: C++ function name
* argumentThis=pointerValue : this first argument is often the memory address/pointer of the C++ object (example "this=0x91ec5f8"  other argument use the same form "parameterName=parameterValue"
* (..): arguments supplied to the function. This information may not be available if *debug information* is not present  
* path/to/source/code/file.cpp:linenumber the path to the source code file that describes that function, and the line number. The path is the one found at '''build time'''. This information may not be useful if '''debug information''' is not available (in that case, the name of the library or application binary may be included. Example: ''/home/kde-devel/kde/lib/libsopranoclient.so.1'')

'''Example''':

#13 0xb759d5d7 in Nepomuk::ResourceData::determineUri (this=0x91ec5f8) at
/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp:671

* The function is the number 13 in the stack
* Function's namespace: "Nepomuk"
* Function's class: "ResourceData"
* Function's function: "determineUri"
* The object "Nepomuk::ResourceData" which called to "determineUri" has the pointer "0x91ec5f8"
* The function is described (where it was build) at "/home/kde-devel/kde/src/KDE/kdelibs/nepomuk/core/resourcedata.cpp". It leads to the next function in the stack at the line number 671

===Identifying the first (useful) backtrace functions===

The first thing you need to do is to locate where it crashed, identifying the "[KCrash Handler]" mark (only in backtraces fetched using DrKonqi)

If the application only had one thread, then it is at the top of the unique thread; otherwise you may need to look at all the thread (the KCrash mark may not be always in the Thread number 1)

Once that you located the "crashing thread start", pickup the first two or three "ClassName::Functions" pairs from top to bottom (some functions should be ignored, read below)

This pairs will be used as "keywords" for the duplicate search

{{Note|This is only a general rule. There are some special cases when the first three function at the top may be the same but the crash may be different (specially on complex application/libraries as Konqueror)}}

If the first backtrace functions aren't available (they are not there, or there are "??" )then we can't proceed without requiring more information (a more complete backtrace) [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#Check_the_report_quality_.28and_ask_for_missing_information.29 Ask for more information]

===Avoiding useless function calls===

Some functions or calls are common to a lot of applications using the same core libraries (like the Qt library, glib, glibc, or many others). This kind of functions should not be used for search as they are not representative of the crash itself and it may return lots of results.

'''Classes and functions to ignore in backtrace''':
* Kernel/GLibC functions (__kernel_vsyscall, raise, abort)
* Functions from core/base libraries (libraries with filenames like libpthread.so.0, libc.so, libstdc++.so, libglib-2.0.so; or functions starting with "*__GI_"). You may also need to ignore calls to graphics drivers (like nvidia or libGL)
* Qt containers classes (QMap, QList, QLinkedList, QVector, QStack, QQueue, QSet, QMap, QMultiMap, QHash, QMultiHash)
* Qt deep core classes (QApplication, QCoreApplication, QBasicAtomicInt, QBasicAtomicPointer, QAtomicInt, QAtomicPointer, QMetaObject, QPointer, QWeakPointer, QSharedPointer, QScopedPointer, QMetaCallEvent)
* Qt misc functions (qt_message_output, qt_message, qGetPtrHelper, (starting with) qt_meta_)

===Special cases (Advanced)===

There are special crashes related to the X11 graphics server. To identify this crashes you can search for the "XIOError" function name (often on Thread 1). The "[KCrash handler]" mark appears in a secondary thread.

The important things to identify those crashes is recognizing the functions *below* the XIOError call (this is, which functions caused the X11 error).

In most of this crashes the functions below "[KCrash handler]" are not important (but they could still be useful to search for duplicates).

==Bugs caused by external issues (UPSTREAM/DOWNSTREAM)==

Check if the bug is caused by an external plugin/add-on or distribution issue

There are several bugs which may be caused by external add-ons. If you are sure this is the case, you should dismiss the report, telling the reporter to file a new bug in a different place.

* Applications which use plugins may be easier to affect (like Plasma when using custom Plasmoids/widgets)

Distributions can also bring some trouble, specially with packaging.

Some problems that may cause bugs are:
* different versions among KDE packages (kdelibs at one version, kdebase at a different one)
* missing plugins (broken packaging) causing crashes or missing features.

Also, distribution can include their own add-ons (to bring their own branding or any other special function). If you know KDE software enough you may be able to recognize this unofficial add-ons.

If the reporter mentions an application or dialog you cannot identify, you could try requesting a screenshot; other people may identify if it is a KDE application or an external addition.

==Check the report quality (and ask for missing information)==

Now that you know that the bug report is unique, and that is not an external issue, you need to check all the needed information is there.

* Check that report is English and that is easily understandable.  
** If it is not in English you may want to look for someone on the KDE group (IRC channels) that may translate it for you. Alternatively you can ask the reporter to use some online translation system (you won't get a clear explanation, but it is something).
**   If the explanation is not clear enough, and you think that the bug could be described in a image, you may want to ask for a screenshot [explanation of Bugzilla attachments]

* If the bug is a graphical glitch or issue, you may want to request a screenshot [explanation of Bugzilla attachments]
* If the issue involves any other component (like the graphics card or drivers) you may need to ask for the versions and component's names
* If the bug report is about a crash and the backtrace information is not really complete (and you couldn't perform a duplicate search) you need to ask the user to install the missing debug package symbols, reproduce the bug and generate a new backtrace. Template for this request:

If you can reproduce the crash at will (or you experience this regularly),
can you install the "PACKAGENAME" package and post a complete backtrace here?
(you can get more information at http://techbase.kde.org/User:DarioAndres
/Basic_Guide_about_Crash_Reporting ) Thanks

The names of the missing packages depends of the application and the distribution (as package naming scheme changes..). Look at List of debug package names on several Distributions

'''Useful information which could be also missing''':
* Application version
* KDE Platform (and/or Software Compilation) version
* If the bug is about a crash, request the version of the Qt library
* If the reporter is using an development version, request the SVN revision of the KDE platform and application

==Setting Bugzilla fields (and re-assignation)==

Often the bug reports aren't properly categorized, or they miss some information in the Bugzilla fields (which are useful for sorting and filtering):

* '''Version''': if the report has a application version, you probably want to set the version in the Bugzilla field
* '''Priority''': we don't use this field in the KDE bug tracker
* '''Severity''': if the bug is important, critical or it causes data loss if should be set to "major" or "critical". If it is about a crash or a freeze it should be set to "crash". If it is any other kind of bug, it should be set to "normal". If it is a feature request (not a regression) it should be set to "wish".
** If you are not really sure if a report describes a real bug or a feature; or if you cannot diagnose the issue, you need to ask in the support channels or wait for other triagers or developers to check the report.
* '''Platform''': this field is only important if the bug is related to one distribution or specific system. (most of the bug reports are common to most of the platforms). Same with the OS field

===Renaming a report: Updating the summary===

Most of the times, the reporter user initially sets the bug report's title, and therefore, the summary doesn't really represent the bug itself. You may want to update the title to contain enough information to identify the issue properly.

A good title may contain:

* A brief explanation of the root cause (if it was found)
* Some of the symptoms people are experiencing
* Additional comments between round brackets/parentheses

{{Tip|Try to use complete and easily readable english sentences as summary}}

* If the bug is about a crash, you may add the first useful ClassName::FunctionName pairs that identify it. You can put them inside square brackets at the end of the title

* If the report has additional information (like a testcase file, or an attached proposed patch) you may add those references as tags at the start of the summary (inside square brackets)

'''Examples''':

[patch] Plasma clock draws garbage when hovering it if the Ctrl key is pressed

Dolphin hangs when trying to view the properties of a big file

[testcase file] Plasma crashes when adding a special file to the panel
[Class1::Function1, Class1::Function2, Class2::Function3]

Applications that use Plasma themes crash when compositing is switched on/off
due an error in KPixmapCache [KPixmapCache::Private::mmapFile,
KPixmapCache::Private::init, KPixmapCache::discard]

[testcase url] Konqueror shows a graphical artifact in webpage's form when
scrolling

===Reassigning bug reports===

Some of the reports are assigned to the wrong product. This may happen because the original reporter didn't know to which application/library did the bug belong to. It may happen if the Crash Handler dialog reports a crash about an unsupported application (or one that is not mapped properly)

{{Warning|Only perform re-assignations if you are sure the bug is in the wrong product.}}

{{Note|Remember to check the [http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging#List_of_related_KDE_technologies KDE related technologies list]}}

# Select the correct Bugzilla product.
# If you are sure the current assignee is the default of the current product, you need to click the checkbox to reset the assignee (so the assignee of the new(and correct) Bugzilla product will get notified)
# Commit the changes
# In the next page, select the correct Component and Version, and save the changes

==Adding related people to the CC list==

Sometimes, the reports describe general issues or are filed against common bugzilla products (like "kde" or "kdelibs"); or, on the other round, are filed against specific products (but the underling bug root cause is at some specific library, not directly related to the current bugzilla product assignee)

In both cases, if we don't need/want to reassign the report (because we aren't really sure about it), we can add the assignee of the other related products, or other developers mail address, to the CC list of the bug report.
That means, this person (or people following a mailing list) will get notified about this bug report, and they might look at it.

To know whom to add to the CC list you can:
* Look at the [https://bugs.kde.org/editproducts.cgi list of bugzilla products and components] and find the current default assignee (this requires special "editcomponents" permissions)
* Look at copyright of the source code related to the bug. (You can always access the code using [http://websvn.kde.org/trunk/KDE/ WebSVN])
* Ask in the IRC support channels which person is related to an specific KDE area (#kde-devel)

Common situation '''examples''':

* A report against "Dolphin" describes a Nepomuk-related error.
** Add the Nepomuk default assignee to the CC list

* A report against "Plasma" describes an error which seems to be more general (at kdelibs level), but you are not really sure if you should reassign it.
** Do not reassign and add "kdelibs-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Konqueror-related issue (and you aren't sure it is a Konqueror-only issue)
** Do not reassign and add "konq-bugs___at___kde___dot___org" to the CC list

* A report against the "kde" bugzilla product describes a Plasma issue
** Reassign the report to the "plasma" bugzilla product; or
** Add "plasma-bugs___at___kde___dot___org" to the CC list

=Trying to reproduce the bugs=

An important step of bug triaging is trying to reproduce the bugs, this means, using the information the reporters added to the bug report to force(recreate, reproduce, repeat) the bug in the application.

This is needed in order to differentiate random/race condition bugs of reproducible ones (which may be reproduced by developers too; and they can fix them)

{{Warning|Testing bug reports may modify/alter your own desktop configuration; also, to try to reproduce some bugs you may need a clean pristine (or sightly modified) environment. I recommend you to perform tests on a separate KDE installation or a clean user. There is also a way to start KDE applications with a clean configuration, even under your current configuration (setting the KDEDIR environment variable at run-time to an empty directory).}}

You may want to use this reference text to setup your testing environment: [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]

{{Note|It is also important to have an updated KDE SC installation to test bugs.}}

==How to test bug reproducibility==

# Read the *complete* bug report (including all the attached information). Note that some bits of information may look unrelated; but they could be useful (or not)
# Use the information in the first comment (the original bug description) to try to reproduce the bug in the application.
# If you can reproduce the bug, then go to the next step
#* If you can't reproduce the bug, use the next comment in the report (which may add new information) to try to reproduce.
#* If you can't reproduce with all the comments in a separate way, you may want to try combined situations (a bit of the description of the original bug, plus a bit of the second one) and similar combinations. You often have to use your imagination a bit (hopefully we still have time). Hopefully, you may find a combination that may reproduce the bug all (or most of) the times. Write down the "recipe" (steps to reproduce it), you need to include that data into the report later.
# Now that we have a result, we need to add our information/conclusions to the bug report

{{Tip|When trying to reproduce a bug, and if there are more than one piece of information, at first glance, try to identify a *common situation*. (some data or context that is present in all (or most of) the cases). This kind of data may be the key to find out how to reproduce.}}

==Adding new information (and requesting feedback)==

* In any case, add your KDE SC version and system information. (other kind of configuration data may be useful to: "did you tested it on a clean environment or in your existing configuration ?" "do you have library X installed and updated ?" "is your system 32 or 64 bits ?")

'''If you could reproduce the bug''':

* If you had to combine several steps to make your own "recipe" to reproduce, write it down. This kind of information should be useful for the developers.

* If you had to use custom input data (text, or a file); you may want to attach it to the bug report (of course, if it is not attached already)

A template of a comment for this situation could be:

I can reproduce the bug here using KDE SC x.y.z, Qt a.b.c on Distribution,
Kernel d.e.f on XX bits.
In order to reproduce I have to perform the following actions:
1- Action 1
2- Action 2
3- Action 3
4- Bug Appears
Note that you need to have the X configuration set to Y, and use the Z library
- Can anyone else confirm this ?
Thanks

'''If you could not reproduce the bug''':

* Write down which kind of steps you performed to try to get the bug.

* You may want to ask to all the reporters if your step had missing something, or if they notice any other strange (or not-default) situation or configuration which may be related.

* Also, if the report is a bit old (more than two major KDE SC releases old), you could try to ask the reporters if you can reproduce the bug in the latest stable KDE SC release or trunk (development version). The bug may be fixed already (but no one wrote it down into the bug report)

A template of comment for this situation could be:

I couldn't reproduce the bug here using KDE SC x.y.z, Qt a.b.c
on Distribution, Kernel d.e.f on XX bits.
I tried performing this actions:
1- Action 1
2- Action 2
or
1a- Action 1a
2a- Action 2a
However the bug didn't appear/the application didn't crash
- Are you all using library X and this kind of configuration ?
- Can you still reproduce this bug with an updated KDE SC version ?
Thanks

Hopefully you will get feedback from the reporters and you could gather more information to try to reproduce the bug or close the report as WORKSFORME (or FIXED)

=Getting bug triaging support=

During your work you may need help on how to proceed, you can use this resources to get help:

* The '''#kde-bugs channel''' on IRC (Freenode.net). You can ask to the whole channel.
* The BugSquad mailing list <bugsquad ##at## kde ##dot## org>

=BugWeeks=

We are planing to host bug triaging events (where new "students" can learn the tricks) named "BugWeeks" on a regular basis to help cleaning up the KDE bug tracker database.

The BugWeeks initiative is based on the Klassroom initiative in the KDE Community Forums

You can find more information about this at:
* [http://forum.kde.org/viewtopic.php?f=4&t=84473 BugWeeks announcement]
* [http://forum.kde.org/viewforum.php?f=148 BugWeeks subsection on KDE Community Forums]
* [http://forum.kde.org/viewtopic.php?f=148&t=84713 BugWeek 0 - Plasma Desktop bugs] ([http://forum.kde.org/viewtopic.php?f=148&t=84888 Summary])

=FAQ=
=More Information=

==List of related KDE technologies==

* Every KDE application use kdelibs [Bugzilla product: '''"kdelibs"''']
* Applications using the standard KDE file operations use KIO [Bugzilla product: '''"kio"'''] and probably KFile (for the UI part) [Bugzilla product: '''"kfile"''']
* Oxygen widget style (default) [Bugzilla product: '''"oxygen"''' component '''"style"'''] (I'm adding the component because "Oxygen" also refers to a Plasma and icon themes)
* Multimedia usage: Phonon library [Bugzilla product: '''"Phonon"''']
* PIM related applications use kdepimlibs, Akonadi and kresources technologies [Bugzilla products: '''"kdepim"''', '''"kdepimlibs"''', '''"Akonadi"''', '''"kresources"''']
* Applications using KHTML [Bugzilla product: '''konqueror"''']
* Applications using OpenDesktop services uses Attica [Bugzilla product: '''"attica"''']
* Screen management related operations use the Kephal subsystem [Bugzilla product: '''"kephal"''']
* Games use libkdegames [Bugzilla product: '''"libkdegames"''']
* Scanning related applications probably use the KSane lib [Bugzilla product: '''"libksane"''']
* Multimedia applications reading audio tags use taglib [Bugzilla product: '''"taglib"''']
* Hardware related functions use Solid classes [Bugzilla product: '''"solid"''']
* Power Management functions use PowerDevil [Bugzilla product: '''"solid"''', component: '''"powerdevil-daemon"''']

==Useful Links==

* [http://techbase.kde.org/Contribute/Bugsquad BugSquad page on Techbase]
* [http://techbase.kde.org/Contribute/Bugsquad/Quick_Introduction_to_Bugzilla Quick introduction to Bugzilla]
* [https://darioandreskde.wordpress.com/ Dario_Andres blog about bug triaging]
* [https://bugs.kde.org/page.cgi?id=fields.html A Bug's Life Cycle]
* [http://forum.kde.org/viewtopic.php?f=9&t=84475 Preparing a testing environment]
* [http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports How to create useful crash reports]
* [http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting Basic guide about crash reports]

==Debug package names for several distributions==

For every KDE application it is recommended to install the debug information for "kdelibs" and "qt4"

{| class="wikitable" style="border:1px solid #AAA; padding:2px"
|-
! Package
! Ubuntu/Debian
! OpenSuse
! Fedora
! Mandriva
|-
| ''kdelibs''
| kdelibs5-dbg
| kdelibs4-debuginfo
| kdelibs-debuginfo
| kdelibs4-debug
|-
| ''qt''
| libqt4-dbg
| libqt4-debuginfo
| qt-debuginfo
| libqt4-debug
|-
| ''kdebase (KDE base applications)''
| kdebase-dbg, kdebase-runtime-dbg, kdebase-workspace-dbg
| kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo
| kdebase-debuginfo, kdebase-runtime-debuginfo, kdebase-workspace-debuginfo
| kdebase4-debug, kdebase4-runtime-debug, kdebase4-workspace-debug
|-
| ''General example for every KDE "MODULE"''
| kdeMODULE-dbg
| kdeMODULE4-debuginfo
| kdeMODULE-debuginfo
| kdeMODULE4-debug
|-
| ''Phonon (multimedia subsystem)''
| phonon-dbg
| phonon4-debuginfo-x86 / libphonon4-debuginfo-32bit
| phonon-debuginfo
| phonon-debug
|}

For a detailed list of distributions naming scheme examples you can look at [http://techbase.kde.org/index.php?title=User:DarioAndres/CreateUsefulReports#How_to_obtain_debug_package_for_several_distributions How to obtain debug packages for every distribution].

==Glossary==

* Testcase: custom file that triggers a bug in the application. A testcase can also be a custom code snippet, or to a set of steps.