KDE TechBase - User contributions [en]

Development/CMake KDE 4 2

2013-06-02T20:49:23Z

Krop: /* How to use KdepimLibs */

=Changes in the buildsystem from KDE 4.0/4.1 to KDE 4.2=

Starting with KDE 4.0.0 source compatibility is guaranteed, this
doesn't apply only to the C++ sources, but also to the
CMake interface.

==Incompatible Changes==

This is the section which we'd like to have empty. Still there were two changes which in some cases make it necessary to modify the CMake files of projects. The change regarding KDEPIMLIBS_INCLUDE_DIR is clearly a bug fix and should affect only few installations. The reduced link interface may be considered a bug fix too, but even if we wouldn't have done it, distributions would have done it (and breaking compatibility by doing this) anyway. So better we do it instead of each distribution maintaining huge patches and distributing something we didn't develop.

# The reduced link interface, details see below. It may be possible that an application which linked against KDE 4.0/4.1 now fails due to unresolved symbols. In this case the libraries which provide these symbols have to be added to the TARGET_LINK_LIBRARIES() calls. This happens only if symbols are used but the library is not linked again. This can be considered a bug in the cmake files of these applications. Applications which explicitely link against all libraries they use will build successfully with KDE 4.2.
# When using a library from kdepimlibs/, KDEPIMLIBS_INCLUDE_DIR has to be added to the include directories, otherwise the headers may not be found. This has only an effect if kdepimlibs is installed in a different directory than kdelibs. In KDE 4.0 and 4.1 FindKdepimLibs.cmake added this include directory to KDE4_INCLUDES, which was wrong and which has been fixed.

==Other Changes==

===Required CMake Version===

At least version 2.6.2 of CMake is required now. With KDE 4.0 and 4.1 version 2.4.5 was required.

===How to use KdepimLibs===

As with KDE 4.0 and 4.1 you do a FIND_PACKAGE(KdepimLibs) to find the installed KdepimLibs.

'''New:''' Then use KDEPIMLIBS_INCLUDE_DIR to add the KdepimLibs include directory using INCLUDE_DIRECTORIES()

'''New:''' The library variables from KdepimLibs now all have the prefix KDEPIMLIBS_ . Use these to link against the KdepimLibs libraries. Simplified example:
<pre>
...
find_package(KdepimLibs REQUIRED)
include_directories(${KDEPIMLIBS_INCLUDE_DIRS})
...
kde4_add_executable(kfoo ${kfooSrcs})
target_link_libraries(kfoo ${KDEPIMLIBS_AKONADI_LIBS} )
</pre>

'''Note:''' In KDE 4.0 and 4.1 these libraries all had the prefix "KDE4_" instead of "KDEPIMLIBS_". This was wrong because the "KDE4_" prefix is reserved exclusively for stuff coming from kdelibs. To keep compatibility, these variables are still available.

For details see the documentation at the top of kdelibs/cmake/modules/FindKdepimLibs.cmake .

===How to use libraries from kdebase/workspace/===

In kdebase/workspace/ there are several libraries which are installed and can be used by other projects. These are libraries for kwin, plasma, the screensaver and some more, see the documentation at the top of kdelibs/cmake/modules/FindKDE4Workspace.cmake for the full list of variables (they are all prefixed with "KDE4WORKSPACE_" ).

===New: Exporting and importing targets===

Starting with version 2.6 CMake can "export" targets. These exported targets can then be imported again by projects using these targets (libraries). These imported targets can then be used in the same way as normal targets and can be used to link against them.
This is necessary to provide better linking support. At least on Windows it is necessary to link against debug versions of libraries in debug mode and against release versions in release mode, otherwise there will be crashes. This was kind-of supported by CMake via the ''debug'' and ''optimized'' keywords for TARGET_LINK_LIBRARIES(), but this was inflexible and and problematic. Exported targets now fully support different configuration types and flexible mapping between them.

Additionally it is now possible to have full control over the so-called link interface of a library. The link interface of library <foo> is the set of libraries against which projects linking against <foo> will be linked additionally. Details see below.

Exporting targets is a two-step process. First the targets have to be added to a set of exported targets, and then this export set has to be installed. You can give this export set arbitrary names. Both executable and library targets can be exported. This is done in the INSTALL(TARGETS ... ) command:
<pre>
add_executable(hello ${helloSrcs})
add_library(bar SHARED ${barSrcs})

install(TARGETS hello EXPORT ExportedTargets DESTINATION bin )
install(TARGETS bar EXPORT ExportedTargets DESTINATION lib )
</pre>

The code shown above puts the two targets ''hello'' and ''bar'' into the (implicitely created) export set named ''ExportedTargets''. This can be done in multiple directories to collect targets into export sets.
Then the export set has to be installed, this means a CMake script file which defines these targets will be written by CMake and installed. This is done using install(EXPORT ):
<pre>
install(EXPORT ExportedTargets DESTINATION ${SOME_INSTALL_DIR}
FILENAME MyPackageConfig.cmake
NAMESPACE MyPackage__ )
</pre>

The command above specifies the install directory of the export file and the filename it will be given. NAMESPACE has the effect that the names of the exported targets will be the names of the original targets in the project prefixed with the given string. This makes name clashes between the imported targets and targets in other projects basically impossible.
So this export files basically looks like this:

<pre>
add_executable(MyPackage__hello IMPORTED)
add_library(MyPackage__bar SHARED IMPORTED)

set_target_properties(MyPackage__hello PROPERTIES
IMPORTED_LOCATION /usr/bin/hello )

set_target_properties(MyPackage__bar PROPERTIES
...configuration specific properties )
...
</pre>

This is automatically generated by CMake and you actually don't have to care about the concrete contents of this file.

Other projects can then include this file and use these targets.

More details at http://www.cmake.org/Wiki/CMake_2.6_Notes#Exporting_and_Importing_Targets .

===New: The reduced link interface===

In KDE 4.0 and 4.1 EXPORT_LIBRARY_DEPENDENCIES() was used in kdelibs/ and kdepimlibs/ for the installed libraries. This creates a file which lists all libraries of that project, and against which libraries they link. This file then had to be include()d by other projects. This way those projects transitively also linked against ''all'' libraries against which these libraries were linked when using these libraries. This is called the "link interface".
Here's an example:
<pre>
add_library(foo ${fooSrcs})
target_link_libraries(foo ${BAR_LIBS} ${BLUB_LIBS} ${ZOT_LIBS})
export_library_dependencies(...)
</pre>

When then another project loads this file and links something against foo, it will be also linked against BAR_LIBS, BLUB_LIBS and ZOT_LIBS. While this is necessary for static libraries, it is not necessary for everything for shared libraries. For shared libraries only those libraries which are exposed in the public interface of the library should be in the link interface. If e.g. foo uses class BlubWidget in a public header, BLUB_LIBS should be in the link interface. This is done using the TARGET_LINK_LIBRARIES() command. The link interface set there is not considered when using EXPORT_LINK_LIBRARIES(), but it is used when exporting the target. So in order to actually benefit from the link interface, the export feature has to be used:
<pre>
add_library(foo ${fooSrcs})
target_link_libraries(foo ${BAR_LIBS} ${BLUB_LIBS} ${ZOT_LIBS})
target_link_libraries(foo LINK_INTERFACE_LIBRARIES ${BLUB_LIBS})

install(foo EXPORT MyExports DESTINATION lib ...)
</pre>

The second TARGET_LINK_LIBRARIES() doesn't cause any additional libraries to be linked against foo, it ''only'' specifies the link interface of the library foo when eported.

===How to install libraries correctly now===

Libraries are still installed using INSTALL(TARGETS ...).

But during installation projects can now also install cmake scripts which export targets, so they can be used by other projects.

So if a project installs a library, and creates an exported target for it, which can be imported by other projects then, two things have to be done additionally:

# Set the link interface
# Export the target

In KDE this is the case for all libraries in '''kdelibs''', '''kdepimlibs''' and the libraries in '''kdebase/workspace''' (and I think also ''kdevplatform'').

====Set the link interface====
This defines against which libraries a package which links to this library will be linked additionally automatically. By default the link interface is empty. This is only the case for libraries created using KDE4_ADD_LIBRARY(), if a library is created using the standard ADD_LIBRARY() the link interface is "full" by default.
Put those libraries in the link interface from which symbols are used in the public interface of your library. If e.g. a QWidget appears in your public headers, but nothing from zlib, put QT_QTGUI_LIBRARY in the link interface:
<pre>
kde4_add_library(kfoo ${kfooSrcs})
target_link_libraries(kfoo ${ZLIB_LIBRARIES} ${QT_QTGUI_LIBRARY})
target_link_libraries(kfoo LINK_INTERFACE_LIBRARIES ${QT_QTGUI_LIBRARY})
</pre>

====Export the library====

This is done in two steps. First add the library to a set of exported targets, and then install this export set as explained above. Here we chose the name ''MyExports'' for the export set:
<pre>
kde4_add_library(kfoo ${kfooSrcs})
...
install(TARGETS kfoo EXPORT MyExports ${INSTALL_TARGETS_DEFAULT_ARGS})
install(EXPORT MyExports args_see_above... )
</pre>

===New option: KDE4_USE_COMMON_CMAKE_PACKAGE_CONFIG_DIR===

With KDE 4.2 and the required CMake 2.6.2 the FIND_PACKAGE() command now supports finding installed configuration files of packages. If the package is named <package>, their configuration file is named <package>Config.cmake. CMake 2.6.2 supports searching these files in lib/<package>/cmake/, a version number may also be included in the directory name: lib/<package>-x.y.z/cmake/.
Starting with version 2.6.3 of CMake (soon to be released as of January 2009), it also supports searching these configuration files in lib/cmake/<package>/ (also with optional version number). This may be preferred by packagers. If a KDE package installs such a configuration file it should check this option, and if enabled install its <package>Config.cmake file to lib/cmake/<package>/ instead of lib/<package>/cmake/.
More at http://www.cmake.org/Wiki/CMake_2.6_Notes#Packages .

This option is only available with CMake >= 2.6.3, in this case it is ON by default. Otherwise it is OFF.

If a package has been installed with this option enabled (which can only be the case with CMake >= 2.6.3), at least CMake 2.6.3 is also required for building packages which use this package. CMake < 2.6.3 will not find their installed <package>Config.cmake files.

Currently only kdepimlibs/ and kdebase/workspace/ install such configuration files.
===Removed option: KDE4_ENABLE_EXPERIMENTAL_LIB_EXPORT===
The option KDE4_ENABLE_EXPERIMENTAL_LIB_EXPORT was new in KDE 4.1 and enabled the reduced link interface. This is now always the case, so the option became unnecessary.

===Removed option: KDE4_USE_ALWAYS_FULL_RPATH===
KDE4_USE_ALWAYS_FULL_RPATH was by default on. In this case executables, libraries and plugins were linked with RPATH. This caused relinking of these binaries during make install, which takes some time. If it was off, only executables were linked with RPATH, and their RPATH had to be sufficient also for the shared libraries and plugins. This can be the case, but doesn't have to. Applications which were not marked as RUN_UNINSTALLED were built directly with their install RPATH. This saved a lot of time during make install but the resulting install might not get the correct libraries. Since version 2.6 CMake can now edit the RPATH inside binaries, which compared to relinking takes no time.

That's why this option is not necessary anymore, and now '''all''' executables, libraries and plugins are always built with their build tree RPATH and then installed with their install tree RPATH, so they always get their correct libraries, both when executed from the build tree as well as when executed from the install tree.

So, if you set this option somewhere, this is no problem with KDE 4.2, it now always does the right thing.

===Guide for writing CMake files===

This is not really a change.

Now using ''all-lowerspace'' for commands is recommended. It is even more recommended to use consistent casing within one file.

There is now a guide available: [[Policies/CMake_Coding_Style | Coding style for CMake files]]

And there is also a guide on how to keep source compatibility for CMake FindXXX.cmake modules: [[Policies/CMake_and_Source_Compatibility | Source compatiblity with CMake]]

===Specifying the minimum required version of some package===

With KDE 4.0/4.1 the minimum required version of some package could by specified using module-specific variables. E.g. for the minimum version of kdelibs you had to do the following:

<pre>
set(KDE_MIN_VERSION "4.1.0")
find_package(KDE4 REQUIRED)
</pre>

Now with CMake 2.6 the FIND_PACKAGE() command supports a minimum version directly as first argument after the package name, but it also has to be supported by the respective FindXXX.cmake module. So now you can do:
<pre>
find_package(KDE4 "4.2" REQUIRED)
</pre>
This works, but there is one problem when doing this for finding KDE4: this way to specify the version is not supported by KDE 4.0/4.1, they just ignore this version information. So to make sure this also works with KDE 4.0/4.1 you have to use the KDE_MIN_VERSION variable.

New modules should support only the new way to do it.

===Misc. new CMake features===

====Finding installed packages====

Starting with CMake 2.6 the FIND_XXX() commands now search by default the respective subdirectories under the current CMAKE_INSTALL_PREFIX and the install prefix of CMake itself.

Additionally now the environment variable CMAKE_PREFIX_PATH is supported. This is a list of directories which are searched by the FIND_XXX() commands with the respective subdirectories appended, i.e. include/ for FIND_PATH() and FIND_FILE(), lib/ for FIND_LIBRARY() and bin/ for FIND_PROGRAM(). These directories are searched before all other directories, so this can be used to make CMake find the versions of packages you want it to find.

E.g. the following can be used to make CMake find required packages in the given directories instead of e.g. a Qt4 installed in /usr/lib :
<pre>
$ export CMAKE_PREFIX_PATH=/opt/qt-copy:/opt/kdesupport:/opt/kdelibs:/opt/kde4
$ cmake args...
</pre>

====Comparing version strings====

CMake now supports comparing version strings consisting of version 1 to 4 version components:
* if(<str> VERSION_GREATER "1.2.3")
* if(<str> VERSION_LESS "1.2.3")

====Functions====

CMake now has a FUNCTION() and an ENDFUNCTION() commands. They can be used similar to MACRO()/ENDMACRO(), but variables created (i.e. SET() ) inside them stay local. To modify a variable outside the function, e.g. as return value, do the following:
<pre>
function(foo)
set(var1 "hello")
set(var2 "world" PARENT_SCOPE)
endfunction(foo)

foo()
message(STATUS "${var1} ${var2}")
</pre>

This will print only "world", since var1 is local to the function.

====Return()====
CMake now has a RETURN(), which can be used to return from function()s and also from processed files. See the man page for details.

====Elseif() ====
CMake now has a ELSEIF().

====Simple calculations====
CMake has a MATH() command, which can be used for simple calculations, it supports the basic mathematical operations.

====cmake-gui====

cmake-gui is a Qt4 based GUI to CMake. It makes running CMake, setting options, checking results and selecting the generator easier.
There are four ways how to invoke cmake-gui:
* in the build directory, the source directory as argument:
<pre>
kdebase/build/$ cmake-gui ..
</pre>
* in any directory, the build directory as argument: if the directory contains already a CMakeCache.txt, cmake-gui will work on this build tree:
<pre>
kdebase/build/ $ cmake-gui .
</pre>
As said before, this works only if the build tree has already been configured before.
* Using "make edit_cache": the edit_cache target invokes the CMake cache editor. By default this is the curses-based ccmake. But if the build tree was generated using cmake-gui, or if you executed cmake-gui previously on the build tree, then "make edit_cache" invokes cmake-gui instead.
* in any directory without arguments: then it starts with the source and build directories from the previous run

http://www.neundorf.net/pics/cmake-gui-kdelibs.png .

====CMake policies====

Starting with version 2.6.0 CMake supports so called policies. These policies are used to provide full compatibility between different CMake versions. In some cases bugfixes in CMake can mean that CMake handles something different now. This may break projects which were set up to expect the buggy behaviour. In order to keep them working for each such change a policy is introduced. Each policy can be set to NEW or OLD behaviour. With OLD behaviour the old (buggy) behaviour is active, with NEW behaviour the new and fixed behaviour is active.

The default for the policies depends on the required minimum version of CMakeas defined with CMAKE_MINIMUM_REQUIRED(). The policies can be manipulated using the new CMAKE_POLICY() command.

The policies are set up for KDE4 in FindKDE4Internal.cmake. They are mostly set to be 2.4.x compatible in order to keep source compatibility with KDE 4.0/4.1.

More details at http://www.cmake.org/Wiki/CMake_Policies .

====Improved documentation====

CMake can generate the documentation additionally to HTML, plain text and man pages now also in docbook format. This can be processed further with docbook utilities to other formats.

Also the documentation has been split into multiple pages:
* cmake: everything all-in-one
* cmakecommands: the recommended commands
* cmakecompat: commands not recommended for use, kept for compatibility
* cmakemodules: the documentation for all modules coming with CMake
* cmakevars: documentation for variables
* cmakeprops: documentation for global, directory, target and source file properties
* cmakepolicies: documentation of the CMake policies

====Support for Cross compiling====

Since version 2.6 CMake supports cross compiling. But KDE4 is not yet ready for cross compiling. Adding support for cross compiling KDE4 is on the TODO for 4.3.

====Support for KDevelop3, Eclipse and CodeBlocks projects====

CMake is not just a Makefile generator but a project generator. This means, it can not only generator Makefiles, but also project files for a variety of IDEs.
CMake 2.4 already supported generating project files for KDevelop3, XCode and MS Visual Studio. Version 2.6 adds support for Eclipse CDT4 and CodeBlocks. This means you can now tell CMake to generate project files for these IDEs and use them to work on your KDE project.

You can do this either via the command line, this is quite a lot of typing:
<pre>
$ cmake -G "CodeBlocks - Unix Makefiles" moreargs...
</pre>
You can also use cmake-gui instead, which makes this much easier.

Policies/CMake Coding Style

2012-12-26T09:18:11Z

Krop: /* Avoid Micro-Optimzations */

This document describes the recommended coding style for CMake files in KDE, i.e. CMakeLists.txt files and *.cmake files.

=General=

To put in in one sentence: be as careful when writing the CMake files as when you are writing C++ code.

==Indentation==

Indent all code correctly, i.e. the body of

* if/else/endif
* foreach/endforeach
* while/endwhile
* macro/endmacro
* function/endfunction

Use spaces for indenting, 2, 3 or 4 spaces preferably. Use the same amount
of spaces for indenting as is used in the rest of the file. Do not use tabs.

==Upper/lower casing==

Most important: use consistent upper- or lowercasing within one file !

In general, in KDE the '''all-lowercase''' style is preferred.

So, this is recommended:
<syntaxhighlight lang="cmake">
add_executable(foo foo.c)
</syntaxhighlight>

This is also acceptable:

<syntaxhighlight lang="cmake">
ADD_EXECUTABLE(bar bar.c)
</syntaxhighlight>

Mixed casing as shown below works too, but should '''not''' be done within KDE:
<pre>
Add_Executable(hello hello.c)
aDd_ExEcUtAbLe(blub blub.c)
</pre>

== End commands ==

To make the code easier to read, use empty commands for endforeach(), endif(), endfunction(), endmacro() and endwhile(). Also, use empty else() commands.

For example, do this:
<syntaxhighlight lang="cmake">
if(FOOVAR)
some_command(...)
else()
another_command(...)
endif()
</syntaxhighlight>

and '''not''' this:
<pre>
if(BARVAR)
some_other_command(...)
endif(BARVAR)
</pre>

=Writing CMake Find-modules=

==(Not) Using pkg-config==

You are free to use pkg-config in FindXXX.cmake modules, as long as the following conditions are met:
* the FindXXX.cmake must also work without pkg-config, as long as the package is either installed to one of the default locations (as /usr or /usr/local) or if CMAKE_PREFIX_PATH is set accordingly
* use only find_package(PkgConfig), don't use include(UsePkgConfig), this one is deprecated
* make sure the variables created by pkg_check_modules() are all prefixed with "PC_", so they don't mix up with other variables, e.g. set via find_path() etc.
* FindLibXml2.cmake as shipped with CMake 2.8.5 is a good example how pkg-config should be handled
* putting something like if(NOT WIN32) around the pkg-config stuff is not necessary (and should be removed if it is somewhere). If pkg-config is not found, e.g. on Windows, the macros simply do nothing.

==Follow CMake's readme.txt==

Follow the style guide from CMake when writing some FindFoo.cmake module:
[http://www.cmake.org/cgi-bin/viewcvs.cgi/Modules/readme.txt?root=CMake&view=markup readme.txt]

==Use FindPackageHandleStandardArgs.cmake==
For checking the results inside the Find-module, the macro find_package_handle_standard_args() (coming with CMake) should be used, using the new extended syntax, which supports also version checking.

==Avoid Micro-Optimizations==
Micro-optimizations like
<pre>
if(FOO_LIBRARY AND FOO_INCLUDE_DIR)
set(FOO_FOUND TRUE)
else()
... execute the whole find-logic
endif()
</pre>
should be removed, the find-logic should be executed always. These shortcuts can cause problems e.g. when the same file is used from multiple directories but e.g. with different required versions or components etc.

Also manually quieting the module should not be done:
<pre>
if ( SQLITE_INCLUDE_DIR AND SQLITE_LIBRARIES )
set(Sqlite_FIND_QUIETLY TRUE)
endif ( SQLITE_INCLUDE_DIR AND SQLITE_LIBRARIES )
</pre>

If find_package_handle_standard_args() is used, this is completely unnecessary, since find_package_handle_standard_args() only prints something if the result has changed compared to the previous run. So if, as in this example, sqlite has already been found, find_package_handle_standard_args() will only print this information during the first CMake run, but not on successive runs.

So, do not add such code. It is unnecessary and makes the modules look more complicated than necessary.

=Writing FooConfig.cmake files=

* See http://quickgit.kde.org/?p=kdeexamples.git&a=tree&hb=HEAD&f=buildsystem/HowToInstallALibrary for a fully commented example

* See also:
** http://www.cmake.org/Wiki/CMake/Tutorials/Exporting_and_Importing_Targets
** http://www.cmake.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file
** http://www.cmake.org/Wiki/CMake/Tutorials/Packaging

Development/Tutorials/Debugging/How to create useful crash reports

2012-10-30T14:58:06Z

Krop: catch both __cxa_throw and __cxa_rethrow

==Introduction==

This document describes how to reproduce a useful backtrace of crashing KDE applications. First, some general information is given. Then, we will describe for several distributions how to prepare your KDE packages and gaining the backtrace. This should be enough for most people.
There are additional sections on how to create backtraces with the GNU Debugger and with Valgrind, which are in some cases useful.

==How to create useful crash reports==

A good crash report at [http://bugs.kde.org Bugzilla] consists of two parts: a '''description''' of how to reproduce the crash and a '''backtrace''' of the crash. With one of those elements missing, it is much harder (if not impossible) for developers to tackle the problem.

A description should consist of more than only "it crashed". Try to describe everything you did prior to the crash. Did you click on a button, opened a particular website or file which caused problems? That little detail which may look useless to you may be useful for the developer, so just write it down.

A more insightful article on how to write good bug descriptions is available [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html at this link], please read that before reporting bugs.

Don't attach the backtrace to the bug report. Instead, simply paste it. This way it is much easier for developers to search for duplicate reports, because attachments will not be searched.

If you paste a backtrace to a report, make sure you strip all but one or two of the
(no debugging symbols found)
lines from the backtrace as they make it harder to read.

Even though pasting backtraces directly is preferred over adding an attachment, please do not paste other things like logs (valgrind, strace or terminal output) or example data (mails, HTML files and so on). Use attachments for these items.

===Backtraces===

Backtraces are essential. They may look meaningless to you, but they might actually contain a wealth of useful information. A backtrace describes which functions were called prior to the crash, so that developers may track down in which function the mess started. Having good backtraces has a downside: [[Development/Tutorials/Debugging/Debugging_symbols|libraries and executables occupy much more disk space than their optimized counter parts]]. That's the reason why many distros choose to install stripped files, '''which results in useless backtraces''':

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233848624 (LWP 12212)]
[New Thread -1255081072 (LWP 12820)]
[New Thread -1240921200 (LWP 12819)]
[New Thread -1266680944 (LWP 12818)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6a1210b in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6a85afe in ?? () from /usr/lib/libX11.so.6
#3 0x00000003 in ?? ()
#4 0x082149c0 in ?? ()
#5 0x00003ffc in ?? ()
#6 0x00000000 in ?? ()

But no worries, with some modifications you can create full blown backtraces for KDE applications.

===Preparing your KDE packages===

If your distribution has debugging-enabled packages, install them.

It is easy to see which debug packages you are missing from looking at the backtrace. For example, take the following line from a backtrace:

#6 0xb7975bdc in ?? () from /usr/lib/libkmailprivate.so.4

The <tt>??</tt> indicates that the library <tt>libkmailprivate.so.4</tt> does not have debug information, which might be available in separate debug packages. In this case, it is pretty easy to guess that you need to install debug packages for KMail to get a better backtrace.

Sometimes, you need to install more than one debug package to get a good backtrace. This depends on how the distribution splits up the packages. For example, for some distributions it is enough to install the debug package for <tt>kdepim</tt> to get enough debugging information for a crash in KMail, for other distributions there is an additional debug package just for KMail.

Here's a list of how to obtain debug packages for some distributions:

*'''Debian''' - Debian offers <tt>-dbg</tt> packages to easy create useful backtraces. Just install the corresponding <tt>-dbg</tt> package. e.g. <tt>kdepim-dbg</tt> for KMail crashes. The dependencies of -dbg makes sure to pull in the other right packages (kdelibs-dbg, gdb, and so on).
*'''FreeBSD ports''' - Please refer to the [http://freebsd.kde.org/faq.php#AKDEapplicationcrashedandIwanttofileabugreportathttpbugskdeorgbutthebacktraceintheKDECrashManagerisuselessWhatcanIdo KDE on FreeBSD FAQ].
*'''Gentoo''' - Gentoo has its [http://www.gentoo.org/proj/en/qa/backtraces.xml own document] describing how to proceed.
*'''Mandriva''' - Mandriva 2007.0 and up has additional debugging packages for all of KDE (in fact, for all of its packages). Just install the corresponding <tt>-debug</tt> package, like <tt>kdebase-debug</tt> and <tt>kdemultimedia-debug</tt>. You probably want to install <tt>kdelibs-debug</tt> anyways.
** Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
*'''Kubuntu/Ubuntu''' - The Ubuntu family makes things quite easy. Every official KDE module has an additional package in the repository, suffixed with <tt>-dbg</tt>. Always install <tt>kdelibs5-dbg</tt>, because all KDE applications use kdelibs (kdelibs-dbg for KDE 3 applications). Then you should install a -dbg package for the application which crashed. For example if KOrganizer crashed you should install <tt>kdepim-dbg</tt> as well. If the program is not from an official KDE module and has no -dbg package, you can install the -dbgsym package from the repository listed on this [https://wiki.kubuntu.org/DebuggingProgramCrash Debugging Program Crashes] page.
**During the Ubuntu development cycle the Apport crash handler is turned on which will report crashes to launchpad.net and do the backtrace for you, if you would rather use the KDE crash handler turn Apport off in /etc/defaults/apport
**Starting with Lucid Lynx (10.04) Kubuntu will be forwarding all non kubuntu specific bugs upstream and had disabled Apport so that DrKonqui will be th edefault crash handler.
*'''openSUSE''' - You should only install the <tt>-debuginfo</tt> packages, for example: <tt>kdepimlibs4-debuginfo</tt>. You can find these packages in [http://en.opensuse.org/KDE/Repositories KDE repositories]. There is also a dedicated [http://en.opensuse.org/openSUSE:Bugreport_application_crashed openSUSE debugging page].
*'''Fedora''' - In Fedora you just need to do:
*# <tt>yum provides "/usr/lib/libkmailprivate.so.4"</tt> to find out which package provides that file;
*# <tt>debuginfo-install kdepim</tt> as root to install debug packages for that package (dependencies included).
*:A complete and detailed guide for Fedora is available in [http://fedoraproject.org/wiki/StackTraces this document] describing how to proceed. Fedora uses a separate debuginfo repository that has to be enabled. Also consider <tt>auto-update-debug-info</tt> yum plugin to keep debuginfo packages up to date.

If your distribution doesn't have debugging-enabled packages for KDE, you'll have to compile KDE from sources:

* If you're using KDE 3, then at the configure stage, you should supply the parameter <tt>--enable-debug=full</tt> in order to build debug symbols in the resulting files.
* If you're using KDE 4, then at the cmake stage, you should supply the parameter <tt>-DCMAKE_BUILD_TYPE=Debug</tt>. If you want to specify your own CXXFLAGS, then use <tt>-DCMAKE_BUILD_TYPE=None -DCMAKE_CXX_FLAGS=$foo</tt> (where $foo is whatever flags you want to set). Note that the Debug build type is highly recommended for most testers.

Then it's just <tt>make</tt> and <tt>make install</tt> as you're used to.

===Crash!===

Now it's time to crash your application. The KDE Crash Dialog should appear right after the crash, which shows the "Developer Information" tab.

[[Image:Kde-crash-handler.png|center|300px|KDE Crash Dialog]]

Click that tab and wait for a minute. This process may take quite some memory, so things may go sluggish all of a sudden. But the result should look much better. For example:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232783168 (LWP 7604)]
[KCrash handler]
#6 0x0806be76 in TreeMapItem::parent (this=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.h:285
#7 0x08065fea in TreeMapItemList::compareItems (this=0xbfec04a8, item1=0x0,
item2=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:720
#8 0xb7281619 in QGList::operator== () from /usr/qt/3/lib/libqt-mt.so.3
#9 0x0806d498 in QPtrList<TreeMapItem>::operator== (this=0xbfec04a8,
list=@0xbfec0468) at /usr/qt/3/include/qptrlist.h:74
#10 0x08062e18 in TreeMapWidget::mousePressEvent (this=0xbfec03ac,
e=0xbfebff1c)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:1840
#11 0xb7004a63 in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb6f6bca7 in QApplication::internalNotify ()
from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb6f6ca88 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb7725a84 in KApplication::notify (this=0xbfec055c, receiver=0xbfec03ac,
event=0xbfebff1c)
at /home/bram/KDE/kde3/kdelibs/kdecore/kapplication.cpp:550
#15 0xb6f0bfd2 in QETWidget::translateMouseEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb6f0b8b0 in QApplication::x11ProcessEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb6f1b761 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb6f82831 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb6f826b6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb6f6b72f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x0805181e in main (argc=134673960, argv=0xffffffff)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/main.cpp:55

This looks better, right? It shows memory addresses, the source files and line numbers and the parameters passed to functions. Which make it more helpful to the developer where to look for the problem.

{{note|You '''need''' GDB installed to get the backtrace of a crash. Please read the next section to know what GDB is, and how to install it.}}

===Retrieving a backtrace with GDB===

In some cases, it is not possible to create a backtrace with the KDE Crash Dialog. This may be caused by an application which entered an infinite loop, or the crash dialog did not appear at all for some reason. You can try to grab a backtrace with <tt>gdb</tt>, the [http://sourceware.org/gdb/ GNU Debugger]. GDB is widely available through distribution packages.

Invoking GDB differs from the situation. You can run an application from inside gdb, or attach gdb to an already running process. The latter may be useful when an application already has entered an infinite loop. But we will first start with running an application inside gdb. From the shell, run:

$ gdb someKDEapp

The GDB prompt will appear. Note that this does not start the application itself, you should run it by invoking the <tt>run</tt> command:

(gdb) run

This will run the application like you are used to, and you can work with it like normal (it only consumes far more memory and may feel sluggish). Now it's time to reproduce your crash. When you succeed, the application just closes and you should return to your GDB prompt. Now it's time to run the 'backtrace' command:

{{note|Some KDE applications (such as JuK and KTorrent) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "run --nofork" at the (gdb) prompt instead of "run" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

(gdb) thread apply all backtrace

This should give a good backtrace which can be posted at the KDE Bugzilla.

In case you want to attach to an existing process, run the following command in the shell:

$ gdb someKDEapp pid

where ''pid'' is the process ID of the process you want to attach to. Once attached, and the process is in an infinite loop, after using the 'backtrace' command again a useful backtrace will appear. You can use 'continue' command to let the application run again and press Ctrl+C in gdb to be able to again enter commands.

=== Retrieving a backtrace when an uncaught exception is causing a crash ===

If your backtrace looks like this:

Thread 1 (Thread 0xb77be730 (LWP 5794)):
[KCrash Handler]
#7 0x00e9b416 in __kernel_vsyscall ()
#8 0x002b1c8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9 0x002b52b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x001c14ed in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0x001bf283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0x001bf2bf in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0x001bf464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
[...]

then only GDB can help getting a useful backtrace. A few more commands are needed. From the shell, run:

$ gdb someKDEapp

Then start loading the application:

(gdb) start

{{note|Some KDE applications (such as KMail or Kontact) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "start --nofork" at the (gdb) prompt instead of "start" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

The GDB prompt will reappear. Turn logging on:

(gdb) set logging file ~/gdblog.txt
(gdb) set logging on

We must now tell gdb to stop just before the exception is thrown. enter:

(gdb) break __cxa_throw
(gdb) break __cxa_rethrow

and finally:

(gdb) cont

This will run the application. Note that the application will consume more memory and be slower.
Now reproduce the crash. When you succeed, the application window will look frozen.

Don't worry and switch back to the shell window.
If you see the gdb prompt, type:

(gdb) thread apply all bt

press enter until the (gdb) prompt reappears.

All done! you can now quit gdb:

(gdb) kill

The kill command will stop the program and now enter:

(gdb) quit

Copy/paste the content saved in the ~/gdblog.txt file to your bug report.

===Retrieving a backtrace with Valgrind===

When it comes to crashes, [http://www.valgrind.org Valgrind] is also a useful tool to create a backtrace. It's not a substitution for GDB, but rather a supplement.

When you run an application in valgrind, every piece of memory read or written by the application is being checked. Valgrind will report erroneous memory operations in the standard output or in a log file. Since most crashes are due to an invalid memory read, valgrind can be useful to track down where the problem occurs.

{{note|Valgrind consists of several tools in order to check or profile an application. For this article, we only use memcheck, the default tool when valgrind is being invoked.}}

Like GDB, Valgrind makes running an application much slower, while consuming a lot more resources.

Start the application within valgrind:

$ valgrind --log-file=someKDEapp someKDEapp

Now reproduce the crash. As soon as this happens, the application and valgrind will terminate. What's left is a file named <tt>someKDEapp.pid</tt> where ''pid'' is replaced by the process ID of the valgrind process. The file may list more errors than the one causing the crash. Here's the bit causing the crash which corresponds to the GDB backtrace above:

==23292== Invalid read of size 4
==23292== at 0x806BD9E: TreeMapItem::parent() const (treemap.h:285)
==23292== by 0x8065FB9: TreeMapItemList::compareItems(void*, void*) (treemap.cpp:720)
==23292== by 0x50AC618: QGList::operator==(QGList const&) const (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x806D3BF: QPtrList<TreeMapItem>::operator==(QPtrList<TreeMapItem> const&) const (qptrlist.h:74)
==23292== by 0x8062DE7: TreeMapWidget::mousePressEvent(QMouseEvent*) (treemap.cpp:1840)
==23292== by 0x4E2FA62: QWidget::event(QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D96CA6: QApplication::internalNotify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D97A87: QApplication::notify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4809AC3: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:550)
==23292== by 0x4D36FD1: QETWidget::translateMouseEvent(_XEvent const*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D368AF: QApplication::x11ProcessEvent(_XEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D46760: QEventLoop::processEvents(unsigned) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== Address 0x2C is not stack'd, malloc'd or (recently) free'd

But to be sure, just attach the whole log file to the crash report.

Projects/PIM

2012-10-20T12:04:41Z

Krop: update

KDE PIM is a package that contains personal information management tools.

The KDEPIM team develops the main application Kontact with all its plugins like KMail, KNode, KOrganizer, KAddressbook, Akregator, KJots and others.

To join the team, simply email the {{KDEML|kdepim}} mailing list, and join the irc://freenode.net/kontact IRC channel.

==Resources==
*[[/PIMsters | Who are we?]]
*[http://kdepim.kde.org Homepage of the KDE PIM]
*[http://kontact.kde.org/ Homepage of Kontact]
*[mailto:kdepim-users@kde.org kdepim-users@kde.org] mailing list (for users): [https://mail.kde.org/mailman/listinfo/kdepim-users subscribe], [http://lists.kde.org/?l=kdepim-users&r=1&w=2 archives]
*[mailto:kde-pim@kde.org kde-pim@kde.org] mailing list (for developers): [https://mail.kde.org/mailman/listinfo/kde-pim subscribe], [http://lists.kde.org/?l=kde-pim&r=1&w=2 archives]

==Development==
Much of the infrastructure of KDE PIM has been moved to kdepimlibs module as a framework for all KDE applications. Therefore we have two main modules within the KDE SVN: '''kdepim''' and '''kdepimlibs'''. The latter contains code that provides public APIs.

Current development focus as of January 2009 is on the Akonadi service and porting existing applications to Akonadi and KMime and other frameworks.

'''If you're looking into starting KMail development, have a look at the [[Projects/PIM/KMail Junior Jobs|list of KMail junior jobs]].'''

===Documentation===
The KMail handbook is currently being rewritten, for more information look at the [[Projects/Documentation/KDE4/kdepim/kmail|documentation wiki page]].
===KDE PIM 4===
*README documents stored in the KDE GIT:
:*kdepim:
::*[https://projects.kde.org/projects/kde/kdepim/repository/revisions/master/entry/README README]
::*[https://projects.kde.org/projects/kde/kdepim/repository/revisions/master/entry/kmail/HACKING KMail's HACKING file]

:*kdepimlibs
::*[https://projects.kde.org/projects/kde/kdepimlibs/repository/revisions/master/entry/README README]
::*[https://projects.kde.org/projects/kde/kdepimlibs/repository/revisions/master/entry/POLICIES POLICIES]
::*[https://projects.kde.org/projects/kde/kdepimlibs/repository/revisions/master/entry/PLAN PLAN]
*[http://api.kde.org/4.x-api/kdepimlibs-apidocs/ KDE PIM LIBS API Reference]
*[http://api.kde.org/4.x-api/kdepim-apidocs/ KDE PIM API Reference]
*[[/KDE 4-related bugs|List of KDE 4-specific bugs, regressions and junior jobs]]
*[[/KMail_SoC_regressions|List of regressions after the merge of the KMail SoC branch]]
*[[/MS Windows|MS Windows topics]]
*[[Development/Tutorials/Writing_kontact_plugins|Tutorial for writing a Kontact plugin]]

====Planning====
*[[Schedules/KDE4/4.2_Feature_Plan#kdepim|Feature Plan]] (see also [[Schedules/KDE4/4.2_Feature_Plan#kdepimlibs|KDEPIMlibs feature plan]])
*Akonadi: [[Projects/PIM/Akonadi|Feature Plan]], [http://lists.kde.org/?l=kde-pim&m=120216697126489&w=2 Osnabrück Meeting Notes]
*[[Projects/PIM/Ideas|Ideas]]:

===Other===
*[[/Development/SingleFileResourceRefactoring|SingleFileResource refactoring plan]]
* [[Projects/PIM/Mobile|KDE PIM for mobile devices]]

===KDE PIM 3===

The KDE PIM 3 branch is frozen and no longer actively maintained. Use the KDE 3 enterprise branch for a version of Kontact that is still being updated.

*[[/Features_3.5.9|New Features included with KDE 3.5.9]]
*[[/Installing the KDE PIM 3.5.5+ feature branch|Installing the KDE PIM 3.5.5+ feature branch]]

===Enterprise branches===
Kontact is the primary [http://kolab.org/ Kolab] client. There are different release cycles for the Kolab clients and for KDE, and therefore there are so-called enterprise branches in SVN where the Kolab versions are maintained. Changes in the enterprise branches are regularly merged back to SVN trunk.
The enterprise branches are maintained by [http://www.klaralvdalens-datakonsult.se/ KDAB].

More information about the enterprise branches can be found at:
*[http://websvn.kde.org/branches/kdepim/ KDEPIM branches in SVN (notably enterprise and enterprise4)]
*[http://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug) Kontact on Windows (enterprise4 branch)]
*[http://kolab.org/roadmap.html Roadmap for the Kolab clients]
*[http://kolab.org/download.html Downloads of the Kolab clients]
*[http://wiki.kolab.org/index.php/Kontact Kontact wiki page]
*[http://kolab.org/documentation.html Various Kolab documents]
*[[Development/Tools/svnmerge.py|Merge Tracking with svnmerge.py]]
*[[Projects/PIM/Enterprise_Translation_Howto|Enterprise Translation Howto]]

===Other Links===
*[http://techbase.kde.org/Category:PIM List of all KDE PIM related articles on TechBase]
*[[Projects/Oxygen/Missing_Icons#KDE_main_modules|Missing Icons in KDE PIM]]
*[http://www.englishbreakfastnetwork.org/krazy/index.php?component=kde-4.x&module=kdepimlibs KDE PIM libraries at the Krazy code checker]
*[http://www.englishbreakfastnetwork.org/krazy/index.php?component=kde-4.x&module=kdepim KDE PIM at the Krazy code checker]
*[http://cia.vc/stats/project/kde/kdepim KDE PIM on CIA]
*[http://cia.vc/account/bots/6503/ CIA commit bot for #kontact (account needed)]
*[http://cia.vc/account/bots/12872/ CIA commit bot for #akonadi (account needed)]
*[http://www.ohloh.net/p/kmail KMail on ohloh.net]
*[http://freshmeat.net/projects/kmail/ Totally outdated KMail freshmeat page]

*[http://forum.kde.org/office-personal-information-management-f-20.html KDE PIM in the KDE forums]
*[http://userbase.kde.org/Applications/Office#Kontact KDE PIM on UserBase]
*[http://userbase.kde.org/Tutorials#In_Kontact KDE PIM tutorials on UserBase]
*[http://en.wikipedia.org/wiki/KDE_Personal_Information_Management KDE PIM on Wikipedia]

===PIM SoC 2008 projects===
*[[/RSS_framework_for_Akonadi|RSS framework for Akonadi]]
[[Category:PIM]]

===Technologies used in KDE PIM===

This list is quite incomplete.

* http://doc.trolltech.com/4.4/richtext.html - Used for the KMail composer. See also [http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRichTextWidget.html KRichTextWidget].
* http://doc.trolltech.com/4.4/model-view-programming.html - Used throughout KDEPIM including KMail tree views etc.
* Akonadi: [[Projects/PIM/Akonadi|Wiki]], [http://www.akonadi-project.org/ Website], [http://download.akonadi-project.org/ Tarballs]

Projects/PIM/Development/IncidenceEditorsRefactoring

2012-10-20T12:04:04Z

Krop: Remove this page as requested by the maintainer

Projects/PIM/Akonadi/Database

2012-03-13T17:21:40Z

Krop: /* PostgreSQL */

= Akonadi Server Database Internals =

This page contains information about how the Akonadi server uses its internal SQL database. This is purely for Akonadi server developers, you are NOT supposed to use the database yourself, by-passing Akonadi!

== Database Schema ==

* [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/akonadi_server_database.html Visualization]
* Code is in server/src/storage
** akonadidb.xml contains the schema in an XML format
** dbinitializer* contains the code to create tables out of that
**updatedb.xml contains schema update instructions
** dbupdater.* executes those

== Backends ==

Akonadi can use different SQL backends. The following documents backend-specific details.

In general, backend specific configuration and setup code can be found in server/src/storage/dbconfig*.

There are three possible operation modes for backends, most only support a subset:
* Embedded: No server process, database is completely integrated into the Akonadi process
* Internal server: Akonadi manages the database server process itself, taking care of starting/stopping and configuring it.
* External server: Akonadi connects to an already running database server.

Selecting and configuring the different backends can be done in ~/.config/akonadi/akonadiserverrc, details on the available options can be found here: [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/classAkonadi_1_1DataStore.html akonadiserverrc options]

=== MySQL ===

Status: working, default backend for desktop systems

Supported modes: Internal, External

MySQL server configuration files for the internal mode can be found here: server/src/storage/mysql-global*.conf.

=== Sqlite ===

Status: working with limitations, default backend for mobile systems

Supported modes: Embedded

Known issues:
* Requires newer version than the default Qt one.
* Requires patched QtSql driver to fix concurrency issues (Akonadi ships a fork of the driver with the necessary changes)
* Slower than MySQL (see e.g. http://bertjan.broeksemaatjes.nl/node/53), based on our measurments about 2-5x on the query level, but still in the milliseconds range, so that's probably not a big issue.
* Mutex-based transaction serialization in Akonadi (required because SQlite's support of concurrency might not be enough) can block clients while background operations such as a IMAP sync are going on. This is the real killer here, the more clients (including background processes like indexing) are accessing the data, the more blocking you experience. Background http://www.sqlite.org/faq.html#q5 , http://www.somacon.com/p369.php , http://www.sqlite.org/lockingv3.html , http://www.mail-archive.com/sqlite-users%40sqlite.org/msg43873.html

=== PostgreSQL ===

Status: Working

Supported modes: Internal, External

Known issues:
* Manual dump and import are required after upgrading the Postgres server installation if the database scheme changes.

=== Virtuoso ===

Status: not working

Supported modes: External

Proof-of-concept work was done during Akademy 2010, up to the point where the database could be created successfully. Known issues:

* Some column names used by Akonadi are Virtuoso keywords
* Some of the first INSERT query fails with a signed vs. unsigned int mismatch/overflow.

Completion of Virtuoso support is considered non-trivial and probably requires a lot of work on the Akonadi side, the SQL dialect is too different from what we support so far.

=== MySQL/Embedded ===

Status: not working

Supported modes: Embedded

Development stopped, MySQL/Embedded does not support transactions.

== Tools ==

=== Generic ===

''akonadiconsole'' has support for browsing the database and run arbitrary SQL queries. See [[Development/Tutorials/Akonadi/Application]].

=== MySQL ===

There are convenience scripts for running mysqld in the configuration used by Akonadi as well as (and probably more useful) running the MySQL command line client connected to the Akonadi database. See server/src/storage/akonadi-mysql-[client|server].sh.

[[Category:Akonadi]]

Development/Tutorials/Debugging/How to create useful crash reports

2012-01-26T20:14:24Z

Krop: /* Retrieving a backtrace when an uncaught exception is causing a crash */

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Debugging/How to create useful crash reports}}
==Introduction==

This document describes how to reproduce a useful backtrace of crashing KDE applications. First, some general information is given. Then, we will describe for several distributions how to prepare your KDE packages and gaining the backtrace. This should be enough for most people.
There are additional sections on how to create backtraces with the GNU Debugger and with Valgrind, which are in some cases useful.

==How to create useful crash reports==

A good crash report at [http://bugs.kde.org Bugzilla] consists of two parts: a '''description''' of how to reproduce the crash and a '''backtrace''' of the crash. With one of those elements missing, it is much harder (if not impossible) for developers to tackle the problem.

A description should consist of more than only "it crashed". Try to describe everything you did prior to the crash. Did you click on a button, opened a particular website or file which caused problems? That little detail which may look useless to you may be useful for the developer, so just write it down.

A more insightful article on how to write good bug descriptions is available [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html at this link], please read that before reporting bugs.

Don't attach the backtrace to the bug report. Instead, simply paste it. This way it is much easier for developers to search for duplicate reports, because attachments will not be searched.

If you paste a backtrace to a report, make sure you strip all but one or two of the
(no debugging symbols found)
lines from the backtrace as they make it harder to read.

Even though pasting backtraces directly is preferred over adding an attachment, please do not paste other things like logs (valgrind, strace or terminal output) or example data (mails, HTML files and so on). Use attachments for these items.

===Backtraces===

Backtraces are essential. They may look meaningless to you, but they might actually contain a wealth of useful information. A backtrace describes which functions were called prior to the crash, so that developers may track down in which function the mess started. Having good backtraces has a downside: [[Development/Tutorials/Debugging/Debugging_symbols|libraries and executables occupy much more disk space than their optimized counter parts]]. That's the reason why many distros choose to install stripped files, '''which results in useless backtraces''':

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233848624 (LWP 12212)]
[New Thread -1255081072 (LWP 12820)]
[New Thread -1240921200 (LWP 12819)]
[New Thread -1266680944 (LWP 12818)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6a1210b in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6a85afe in ?? () from /usr/lib/libX11.so.6
#3 0x00000003 in ?? ()
#4 0x082149c0 in ?? ()
#5 0x00003ffc in ?? ()
#6 0x00000000 in ?? ()

But no worries, with some modifications you can create full blown backtraces for KDE applications.

===Preparing your KDE packages===

If your distribution has debugging-enabled packages, install them.

It is easy to see which debug packages you are missing from looking at the backtrace. For example, take the following line from a backtrace:

#6 0xb7975bdc in ?? () from /usr/lib/libkmailprivate.so.4

The <tt>??</tt> indicates that the library <tt>libkmailprivate.so.4</tt> does not have debug information, which might be available in separate debug packages. In this case, it is pretty easy to guess that you need to install debug packages for KMail to get a better backtrace.

Sometimes, you need to install more than one debug package to get a good backtrace. This depends on how the distribution splits up the packages. For example, for some distributions it is enough to install the debug package for <tt>kdepim</tt> to get enough debugging information for a crash in KMail, for other distributions there is an additional debug package just for KMail.

Here's a list of how to obtain debug packages for some distributions:

*'''Debian''' - Debian offers <tt>-dbg</tt> packages to easy create useful backtraces. Just install the corresponding <tt>-dbg</tt> package. e.g. <tt>kdepim-dbg</tt> for KMail crashes. The dependencies of -dbg makes sure to pull in the other right packages (kdelibs-dbg, gdb, and so on).
*'''FreeBSD ports''' - Please refer to the [http://freebsd.kde.org/faq.php#AKDEapplicationcrashedandIwanttofileabugreportathttpbugskdeorgbutthebacktraceintheKDECrashManagerisuselessWhatcanIdo KDE on FreeBSD FAQ].
*'''Gentoo''' - Gentoo has its [http://www.gentoo.org/proj/en/qa/backtraces.xml own document] describing how to proceed.
*'''Mandriva''' - Mandriva 2007.0 and up has additional debugging packages for all of KDE (in fact, for all of its packages). Just install the corresponding <tt>-debug</tt> package, like <tt>kdebase-debug</tt> and <tt>kdemultimedia-debug</tt>. You probably want to install <tt>kdelibs-debug</tt> anyways.
** Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
*'''Kubuntu/Ubuntu''' - The Ubuntu family makes things quite easy. Every official KDE module has an additional package in the repository, suffixed with <tt>-dbg</tt>. Always install <tt>kdelibs5-dbg</tt>, because all KDE applications use kdelibs (kdelibs-dbg for KDE 3 applications). Then you should install a -dbg package for the application which crashed. For example if KOrganizer crashed you should install <tt>kdepim-dbg</tt> as well. If the program is not from an official KDE module and has no -dbg package, you can install the -dbgsym package from the repository listed on this [https://wiki.kubuntu.org/DebuggingProgramCrash Debugging Program Crashes] page.
**During the Ubuntu development cycle the Apport crash handler is turned on which will report crashes to launchpad.net and do the backtrace for you, if you would rather use the KDE crash handler turn Apport off in /etc/defaults/apport
**Starting with Lucid Lynx (10.04) Kubuntu will be forwarding all non kubuntu specific bugs upstream and had disabled Apport so that DrKonqui will be th edefault crash handler.
*'''openSUSE''' - You should only install the <tt>-debuginfo</tt> packages, for example: <tt>kdepimlibs4-debuginfo</tt>. You can find these packages in [http://en.opensuse.org/KDE/Repositories KDE repositories]. There is also a dedicated [http://en.opensuse.org/openSUSE:Bugreport_application_crashed openSUSE debugging page].
*'''Fedora''' - In Fedora you just need to do:
*# <tt>yum provides "/usr/lib/libkmailprivate.so.4"</tt> to find out which package provides that file;
*# <tt>debuginfo-install kdepim</tt> as root to install debug packages for that package (dependencies included).
*:A complete and detailed guide for Fedora is available in [http://fedoraproject.org/wiki/StackTraces this document] describing how to proceed. Fedora uses a separate debuginfo repository that has to be enabled. Also consider <tt>auto-update-debug-info</tt> yum plugin to keep debuginfo packages up to date.

If your distribution doesn't have debugging-enabled packages for KDE, you'll have to compile KDE from sources:

* If you're using KDE 3, then at the configure stage, you should supply the parameter <tt>--enable-debug=full</tt> in order to build debug symbols in the resulting files.
* If you're using KDE 4, then at the cmake stage, you should supply the parameter <tt>-DCMAKE_BUILD_TYPE=Debug</tt>. If you want to specify your own CXXFLAGS, then use <tt>-DCMAKE_BUILD_TYPE=None -DCMAKE_CXX_FLAGS=$foo</tt> (where $foo is whatever flags you want to set). Note that the Debug build type is highly recommended for most testers.

Then it's just <tt>make</tt> and <tt>make install</tt> as you're used to.

===Crash!===

Now it's time to crash your application. The KDE Crash Dialog should appear right after the crash, which shows the "Developer Information" tab.

[[Image:Kde-crash-handler.png|center|300px|KDE Crash Dialog]]

Click that tab and wait for a minute. This process may take quite some memory, so things may go sluggish all of a sudden. But the result should look much better. For example:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232783168 (LWP 7604)]
[KCrash handler]
#6 0x0806be76 in TreeMapItem::parent (this=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.h:285
#7 0x08065fea in TreeMapItemList::compareItems (this=0xbfec04a8, item1=0x0,
item2=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:720
#8 0xb7281619 in QGList::operator== () from /usr/qt/3/lib/libqt-mt.so.3
#9 0x0806d498 in QPtrList<TreeMapItem>::operator== (this=0xbfec04a8,
list=@0xbfec0468) at /usr/qt/3/include/qptrlist.h:74
#10 0x08062e18 in TreeMapWidget::mousePressEvent (this=0xbfec03ac,
e=0xbfebff1c)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:1840
#11 0xb7004a63 in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb6f6bca7 in QApplication::internalNotify ()
from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb6f6ca88 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb7725a84 in KApplication::notify (this=0xbfec055c, receiver=0xbfec03ac,
event=0xbfebff1c)
at /home/bram/KDE/kde3/kdelibs/kdecore/kapplication.cpp:550
#15 0xb6f0bfd2 in QETWidget::translateMouseEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb6f0b8b0 in QApplication::x11ProcessEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb6f1b761 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb6f82831 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb6f826b6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb6f6b72f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x0805181e in main (argc=134673960, argv=0xffffffff)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/main.cpp:55

This looks better, right? It shows memory addresses, the source files and line numbers and the parameters passed to functions. Which make it more helpful to the developer where to look for the problem.

{{note|You '''need''' GDB installed to get the backtrace of a crash. Please read the next section to know what GDB is, and how to install it.}}

===Retrieving a backtrace with GDB===

In some cases, it is not possible to create a backtrace with the KDE Crash Dialog. This may be caused by an application which entered an infinite loop, or the crash dialog did not appear at all for some reason. You can try to grab a backtrace with <tt>gdb</tt>, the [http://sourceware.org/gdb/ GNU Debugger]. GDB is widely available through distribution packages.

Invoking GDB differs from the situation. You can run an application from inside gdb, or attach gdb to an already running process. The latter may be useful when an application already has entered an infinite loop. But we will first start with running an application inside gdb. From the shell, run:

$ gdb someKDEapp

The GDB prompt will appear. Note that this does not start the application itself, you should run it by invoking the <tt>run</tt> command:

(gdb) run

This will run the application like you are used to, and you can work with it like normal (it only consumes far more memory and may feel sluggish). Now it's time to reproduce your crash. When you succeed, the application just closes and you should return to your GDB prompt. Now it's time to run the 'backtrace' command:

{{note|Some KDE applications (such as JuK and KTorrent) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "run --nofork" at the (gdb) prompt instead of "run" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

(gdb) thread apply all backtrace

This should give a good backtrace which can be posted at the KDE Bugzilla.

In case you want to attach to an existing process, run the following command in the shell:

$ gdb someKDEapp pid

where ''pid'' is the process ID of the process you want to attach to. Once attached, and the process is in an infinite loop, after using the 'backtrace' command again a useful backtrace will appear. You can use 'continue' command to let the application run again and press Ctrl+C in gdb to be able to again enter commands.

=== Retrieving a backtrace when an uncaught exception is causing a crash ===

If your backtrace looks like this:

Thread 1 (Thread 0xb77be730 (LWP 5794)):
[KCrash Handler]
#7 0x00e9b416 in __kernel_vsyscall ()
#8 0x002b1c8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9 0x002b52b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x001c14ed in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0x001bf283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0x001bf2bf in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0x001bf464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
[...]

then only GDB can help getting a useful backtrace. A few more commands are needed. From the shell, run:

$ gdb someKDEapp

Then start loading the application:

(gdb) start

{{note|Some KDE applications (such as KMail or Kontact) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "start --nofork" at the (gdb) prompt instead of "start" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

The GDB prompt will reappear. Turn logging on:

(gdb) set logging file ~/gdblog.txt
(gdb) set logging on

We must now tell gdb to stop just before the exception is thrown. enter:

(gdb) break __cxa_rethrow

and finally:

(gdb) cont

This will run the application. Note that the application will consume more memory and be slower.
Now reproduce the crash. When you succeed, the application window will look frozen.

Don't worry and switch back to the shell window.
If you see the gdb prompt, type:

(gdb) thread apply all bt

press enter until the (gdb) prompt reappears.

All done! you can now quit gdb:

(gdb) kill

The kill command will stop the program and now enter:

(gdb) quit

Copy/paste the content saved in the ~/gdblog.txt file to your bug report.

===Retrieving a backtrace with Valgrind===

When it comes to crashes, [http://www.valgrind.org Valgrind] is also a useful tool to create a backtrace. It's not a substitution for GDB, but rather a supplement.

When you run an application in valgrind, every piece of memory read or written by the application is being checked. Valgrind will report erroneous memory operations in the standard output or in a log file. Since most crashes are due to an invalid memory read, valgrind can be useful to track down where the problem occurs.

{{note|Valgrind consists of several tools in order to check or profile an application. For this article, we only use memcheck, the default tool when valgrind is being invoked.}}

Like GDB, Valgrind makes running an application much slower, while consuming a lot more resources.

Start the application within valgrind:

$ valgrind --log-file=someKDEapp someKDEapp

Now reproduce the crash. As soon as this happens, the application and valgrind will terminate. What's left is a file named <tt>someKDEapp.pid</tt> where ''pid'' is replaced by the process ID of the valgrind process. The file may list more errors than the one causing the crash. Here's the bit causing the crash which corresponds to the GDB backtrace above:

==23292== Invalid read of size 4
==23292== at 0x806BD9E: TreeMapItem::parent() const (treemap.h:285)
==23292== by 0x8065FB9: TreeMapItemList::compareItems(void*, void*) (treemap.cpp:720)
==23292== by 0x50AC618: QGList::operator==(QGList const&) const (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x806D3BF: QPtrList<TreeMapItem>::operator==(QPtrList<TreeMapItem> const&) const (qptrlist.h:74)
==23292== by 0x8062DE7: TreeMapWidget::mousePressEvent(QMouseEvent*) (treemap.cpp:1840)
==23292== by 0x4E2FA62: QWidget::event(QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D96CA6: QApplication::internalNotify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D97A87: QApplication::notify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4809AC3: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:550)
==23292== by 0x4D36FD1: QETWidget::translateMouseEvent(_XEvent const*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D368AF: QApplication::x11ProcessEvent(_XEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D46760: QEventLoop::processEvents(unsigned) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== Address 0x2C is not stack'd, malloc'd or (recently) free'd

But to be sure, just attach the whole log file to the crash report.

Development/Tutorials/Debugging/How to create useful crash reports

2012-01-26T20:09:51Z

Krop: /* Retrieving a backtrace when an uncaught exception is causing a crash */

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Debugging/How to create useful crash reports}}
==Introduction==

This document describes how to reproduce a useful backtrace of crashing KDE applications. First, some general information is given. Then, we will describe for several distributions how to prepare your KDE packages and gaining the backtrace. This should be enough for most people.
There are additional sections on how to create backtraces with the GNU Debugger and with Valgrind, which are in some cases useful.

==How to create useful crash reports==

A good crash report at [http://bugs.kde.org Bugzilla] consists of two parts: a '''description''' of how to reproduce the crash and a '''backtrace''' of the crash. With one of those elements missing, it is much harder (if not impossible) for developers to tackle the problem.

A description should consist of more than only "it crashed". Try to describe everything you did prior to the crash. Did you click on a button, opened a particular website or file which caused problems? That little detail which may look useless to you may be useful for the developer, so just write it down.

A more insightful article on how to write good bug descriptions is available [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html at this link], please read that before reporting bugs.

Don't attach the backtrace to the bug report. Instead, simply paste it. This way it is much easier for developers to search for duplicate reports, because attachments will not be searched.

If you paste a backtrace to a report, make sure you strip all but one or two of the
(no debugging symbols found)
lines from the backtrace as they make it harder to read.

Even though pasting backtraces directly is preferred over adding an attachment, please do not paste other things like logs (valgrind, strace or terminal output) or example data (mails, HTML files and so on). Use attachments for these items.

===Backtraces===

Backtraces are essential. They may look meaningless to you, but they might actually contain a wealth of useful information. A backtrace describes which functions were called prior to the crash, so that developers may track down in which function the mess started. Having good backtraces has a downside: [[Development/Tutorials/Debugging/Debugging_symbols|libraries and executables occupy much more disk space than their optimized counter parts]]. That's the reason why many distros choose to install stripped files, '''which results in useless backtraces''':

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233848624 (LWP 12212)]
[New Thread -1255081072 (LWP 12820)]
[New Thread -1240921200 (LWP 12819)]
[New Thread -1266680944 (LWP 12818)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6a1210b in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6a85afe in ?? () from /usr/lib/libX11.so.6
#3 0x00000003 in ?? ()
#4 0x082149c0 in ?? ()
#5 0x00003ffc in ?? ()
#6 0x00000000 in ?? ()

But no worries, with some modifications you can create full blown backtraces for KDE applications.

===Preparing your KDE packages===

If your distribution has debugging-enabled packages, install them.

It is easy to see which debug packages you are missing from looking at the backtrace. For example, take the following line from a backtrace:

#6 0xb7975bdc in ?? () from /usr/lib/libkmailprivate.so.4

The <tt>??</tt> indicates that the library <tt>libkmailprivate.so.4</tt> does not have debug information, which might be available in separate debug packages. In this case, it is pretty easy to guess that you need to install debug packages for KMail to get a better backtrace.

Sometimes, you need to install more than one debug package to get a good backtrace. This depends on how the distribution splits up the packages. For example, for some distributions it is enough to install the debug package for <tt>kdepim</tt> to get enough debugging information for a crash in KMail, for other distributions there is an additional debug package just for KMail.

Here's a list of how to obtain debug packages for some distributions:

*'''Debian''' - Debian offers <tt>-dbg</tt> packages to easy create useful backtraces. Just install the corresponding <tt>-dbg</tt> package. e.g. <tt>kdepim-dbg</tt> for KMail crashes. The dependencies of -dbg makes sure to pull in the other right packages (kdelibs-dbg, gdb, and so on).
*'''FreeBSD ports''' - Please refer to the [http://freebsd.kde.org/faq.php#AKDEapplicationcrashedandIwanttofileabugreportathttpbugskdeorgbutthebacktraceintheKDECrashManagerisuselessWhatcanIdo KDE on FreeBSD FAQ].
*'''Gentoo''' - Gentoo has its [http://www.gentoo.org/proj/en/qa/backtraces.xml own document] describing how to proceed.
*'''Mandriva''' - Mandriva 2007.0 and up has additional debugging packages for all of KDE (in fact, for all of its packages). Just install the corresponding <tt>-debug</tt> package, like <tt>kdebase-debug</tt> and <tt>kdemultimedia-debug</tt>. You probably want to install <tt>kdelibs-debug</tt> anyways.
** Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
*'''Kubuntu/Ubuntu''' - The Ubuntu family makes things quite easy. Every official KDE module has an additional package in the repository, suffixed with <tt>-dbg</tt>. Always install <tt>kdelibs5-dbg</tt>, because all KDE applications use kdelibs (kdelibs-dbg for KDE 3 applications). Then you should install a -dbg package for the application which crashed. For example if KOrganizer crashed you should install <tt>kdepim-dbg</tt> as well. If the program is not from an official KDE module and has no -dbg package, you can install the -dbgsym package from the repository listed on this [https://wiki.kubuntu.org/DebuggingProgramCrash Debugging Program Crashes] page.
**During the Ubuntu development cycle the Apport crash handler is turned on which will report crashes to launchpad.net and do the backtrace for you, if you would rather use the KDE crash handler turn Apport off in /etc/defaults/apport
**Starting with Lucid Lynx (10.04) Kubuntu will be forwarding all non kubuntu specific bugs upstream and had disabled Apport so that DrKonqui will be th edefault crash handler.
*'''openSUSE''' - You should only install the <tt>-debuginfo</tt> packages, for example: <tt>kdepimlibs4-debuginfo</tt>. You can find these packages in [http://en.opensuse.org/KDE/Repositories KDE repositories]. There is also a dedicated [http://en.opensuse.org/openSUSE:Bugreport_application_crashed openSUSE debugging page].
*'''Fedora''' - In Fedora you just need to do:
*# <tt>yum provides "/usr/lib/libkmailprivate.so.4"</tt> to find out which package provides that file;
*# <tt>debuginfo-install kdepim</tt> as root to install debug packages for that package (dependencies included).
*:A complete and detailed guide for Fedora is available in [http://fedoraproject.org/wiki/StackTraces this document] describing how to proceed. Fedora uses a separate debuginfo repository that has to be enabled. Also consider <tt>auto-update-debug-info</tt> yum plugin to keep debuginfo packages up to date.

If your distribution doesn't have debugging-enabled packages for KDE, you'll have to compile KDE from sources:

* If you're using KDE 3, then at the configure stage, you should supply the parameter <tt>--enable-debug=full</tt> in order to build debug symbols in the resulting files.
* If you're using KDE 4, then at the cmake stage, you should supply the parameter <tt>-DCMAKE_BUILD_TYPE=Debug</tt>. If you want to specify your own CXXFLAGS, then use <tt>-DCMAKE_BUILD_TYPE=None -DCMAKE_CXX_FLAGS=$foo</tt> (where $foo is whatever flags you want to set). Note that the Debug build type is highly recommended for most testers.

Then it's just <tt>make</tt> and <tt>make install</tt> as you're used to.

===Crash!===

Now it's time to crash your application. The KDE Crash Dialog should appear right after the crash, which shows the "Developer Information" tab.

[[Image:Kde-crash-handler.png|center|300px|KDE Crash Dialog]]

Click that tab and wait for a minute. This process may take quite some memory, so things may go sluggish all of a sudden. But the result should look much better. For example:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232783168 (LWP 7604)]
[KCrash handler]
#6 0x0806be76 in TreeMapItem::parent (this=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.h:285
#7 0x08065fea in TreeMapItemList::compareItems (this=0xbfec04a8, item1=0x0,
item2=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:720
#8 0xb7281619 in QGList::operator== () from /usr/qt/3/lib/libqt-mt.so.3
#9 0x0806d498 in QPtrList<TreeMapItem>::operator== (this=0xbfec04a8,
list=@0xbfec0468) at /usr/qt/3/include/qptrlist.h:74
#10 0x08062e18 in TreeMapWidget::mousePressEvent (this=0xbfec03ac,
e=0xbfebff1c)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:1840
#11 0xb7004a63 in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb6f6bca7 in QApplication::internalNotify ()
from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb6f6ca88 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb7725a84 in KApplication::notify (this=0xbfec055c, receiver=0xbfec03ac,
event=0xbfebff1c)
at /home/bram/KDE/kde3/kdelibs/kdecore/kapplication.cpp:550
#15 0xb6f0bfd2 in QETWidget::translateMouseEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb6f0b8b0 in QApplication::x11ProcessEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb6f1b761 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb6f82831 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb6f826b6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb6f6b72f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x0805181e in main (argc=134673960, argv=0xffffffff)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/main.cpp:55

This looks better, right? It shows memory addresses, the source files and line numbers and the parameters passed to functions. Which make it more helpful to the developer where to look for the problem.

{{note|You '''need''' GDB installed to get the backtrace of a crash. Please read the next section to know what GDB is, and how to install it.}}

===Retrieving a backtrace with GDB===

In some cases, it is not possible to create a backtrace with the KDE Crash Dialog. This may be caused by an application which entered an infinite loop, or the crash dialog did not appear at all for some reason. You can try to grab a backtrace with <tt>gdb</tt>, the [http://sourceware.org/gdb/ GNU Debugger]. GDB is widely available through distribution packages.

Invoking GDB differs from the situation. You can run an application from inside gdb, or attach gdb to an already running process. The latter may be useful when an application already has entered an infinite loop. But we will first start with running an application inside gdb. From the shell, run:

$ gdb someKDEapp

The GDB prompt will appear. Note that this does not start the application itself, you should run it by invoking the <tt>run</tt> command:

(gdb) run

This will run the application like you are used to, and you can work with it like normal (it only consumes far more memory and may feel sluggish). Now it's time to reproduce your crash. When you succeed, the application just closes and you should return to your GDB prompt. Now it's time to run the 'backtrace' command:

{{note|Some KDE applications (such as JuK and KTorrent) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "run --nofork" at the (gdb) prompt instead of "run" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

(gdb) thread apply all backtrace

This should give a good backtrace which can be posted at the KDE Bugzilla.

In case you want to attach to an existing process, run the following command in the shell:

$ gdb someKDEapp pid

where ''pid'' is the process ID of the process you want to attach to. Once attached, and the process is in an infinite loop, after using the 'backtrace' command again a useful backtrace will appear. You can use 'continue' command to let the application run again and press Ctrl+C in gdb to be able to again enter commands.

=== Retrieving a backtrace when an uncaught exception is causing a crash ===

If your backtrace looks like this:

Thread 1 (Thread 0xb77be730 (LWP 5794)):
[KCrash Handler]
#7 0x00e9b416 in __kernel_vsyscall ()
#8 0x002b1c8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9 0x002b52b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x001c14ed in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0x001bf283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0x001bf2bf in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0x001bf464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
[...]

then only GDB can help getting a useful backtrace. A few more commands are needed. From the shell, run:

$ gdb someKDEapp

Then start loading the application:

(gdb) start

{{note|Some KDE applications (such as KMail or Kontact) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "start --nofork" at the (gdb) prompt instead of "start" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

The GDB prompt will reappear. Turn logging on:

(gdb) set logging file ~/gdblog.txt
(gdb) set logging on

We must now tell gdb to stop just before the exception is thrown. enter:

(gdb) catch __cxa_rethrow

and finally:

(gdb) cont

This will run the application. Note that the application will consume more memory and be slower.
Now reproduce the crash. When you succeed, the application window will look frozen.

Don't worry and switch back to the shell window.
If you see the gdb prompt, type:

(gdb) thread apply all bt

press enter until the (gdb) prompt reappears.

All done! you can now quit gdb:

(gdb) kill

The kill command will stop the program and now enter:

(gdb) quit

Copy/paste the content saved in the ~/gdblog.txt file to your bug report.

===Retrieving a backtrace with Valgrind===

When it comes to crashes, [http://www.valgrind.org Valgrind] is also a useful tool to create a backtrace. It's not a substitution for GDB, but rather a supplement.

When you run an application in valgrind, every piece of memory read or written by the application is being checked. Valgrind will report erroneous memory operations in the standard output or in a log file. Since most crashes are due to an invalid memory read, valgrind can be useful to track down where the problem occurs.

{{note|Valgrind consists of several tools in order to check or profile an application. For this article, we only use memcheck, the default tool when valgrind is being invoked.}}

Like GDB, Valgrind makes running an application much slower, while consuming a lot more resources.

Start the application within valgrind:

$ valgrind --log-file=someKDEapp someKDEapp

Now reproduce the crash. As soon as this happens, the application and valgrind will terminate. What's left is a file named <tt>someKDEapp.pid</tt> where ''pid'' is replaced by the process ID of the valgrind process. The file may list more errors than the one causing the crash. Here's the bit causing the crash which corresponds to the GDB backtrace above:

==23292== Invalid read of size 4
==23292== at 0x806BD9E: TreeMapItem::parent() const (treemap.h:285)
==23292== by 0x8065FB9: TreeMapItemList::compareItems(void*, void*) (treemap.cpp:720)
==23292== by 0x50AC618: QGList::operator==(QGList const&) const (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x806D3BF: QPtrList<TreeMapItem>::operator==(QPtrList<TreeMapItem> const&) const (qptrlist.h:74)
==23292== by 0x8062DE7: TreeMapWidget::mousePressEvent(QMouseEvent*) (treemap.cpp:1840)
==23292== by 0x4E2FA62: QWidget::event(QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D96CA6: QApplication::internalNotify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D97A87: QApplication::notify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4809AC3: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:550)
==23292== by 0x4D36FD1: QETWidget::translateMouseEvent(_XEvent const*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D368AF: QApplication::x11ProcessEvent(_XEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D46760: QEventLoop::processEvents(unsigned) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== Address 0x2C is not stack'd, malloc'd or (recently) free'd

But to be sure, just attach the whole log file to the crash report.

Development/Tutorials/Debugging/How to create useful crash reports

2012-01-26T20:08:58Z

Krop: add the nofork note

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Debugging/How to create useful crash reports}}
==Introduction==

This document describes how to reproduce a useful backtrace of crashing KDE applications. First, some general information is given. Then, we will describe for several distributions how to prepare your KDE packages and gaining the backtrace. This should be enough for most people.
There are additional sections on how to create backtraces with the GNU Debugger and with Valgrind, which are in some cases useful.

==How to create useful crash reports==

A good crash report at [http://bugs.kde.org Bugzilla] consists of two parts: a '''description''' of how to reproduce the crash and a '''backtrace''' of the crash. With one of those elements missing, it is much harder (if not impossible) for developers to tackle the problem.

A description should consist of more than only "it crashed". Try to describe everything you did prior to the crash. Did you click on a button, opened a particular website or file which caused problems? That little detail which may look useless to you may be useful for the developer, so just write it down.

A more insightful article on how to write good bug descriptions is available [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html at this link], please read that before reporting bugs.

Don't attach the backtrace to the bug report. Instead, simply paste it. This way it is much easier for developers to search for duplicate reports, because attachments will not be searched.

If you paste a backtrace to a report, make sure you strip all but one or two of the
(no debugging symbols found)
lines from the backtrace as they make it harder to read.

Even though pasting backtraces directly is preferred over adding an attachment, please do not paste other things like logs (valgrind, strace or terminal output) or example data (mails, HTML files and so on). Use attachments for these items.

===Backtraces===

Backtraces are essential. They may look meaningless to you, but they might actually contain a wealth of useful information. A backtrace describes which functions were called prior to the crash, so that developers may track down in which function the mess started. Having good backtraces has a downside: [[Development/Tutorials/Debugging/Debugging_symbols|libraries and executables occupy much more disk space than their optimized counter parts]]. That's the reason why many distros choose to install stripped files, '''which results in useless backtraces''':

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233848624 (LWP 12212)]
[New Thread -1255081072 (LWP 12820)]
[New Thread -1240921200 (LWP 12819)]
[New Thread -1266680944 (LWP 12818)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6a1210b in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6a85afe in ?? () from /usr/lib/libX11.so.6
#3 0x00000003 in ?? ()
#4 0x082149c0 in ?? ()
#5 0x00003ffc in ?? ()
#6 0x00000000 in ?? ()

But no worries, with some modifications you can create full blown backtraces for KDE applications.

===Preparing your KDE packages===

If your distribution has debugging-enabled packages, install them.

It is easy to see which debug packages you are missing from looking at the backtrace. For example, take the following line from a backtrace:

#6 0xb7975bdc in ?? () from /usr/lib/libkmailprivate.so.4

The <tt>??</tt> indicates that the library <tt>libkmailprivate.so.4</tt> does not have debug information, which might be available in separate debug packages. In this case, it is pretty easy to guess that you need to install debug packages for KMail to get a better backtrace.

Sometimes, you need to install more than one debug package to get a good backtrace. This depends on how the distribution splits up the packages. For example, for some distributions it is enough to install the debug package for <tt>kdepim</tt> to get enough debugging information for a crash in KMail, for other distributions there is an additional debug package just for KMail.

Here's a list of how to obtain debug packages for some distributions:

*'''Debian''' - Debian offers <tt>-dbg</tt> packages to easy create useful backtraces. Just install the corresponding <tt>-dbg</tt> package. e.g. <tt>kdepim-dbg</tt> for KMail crashes. The dependencies of -dbg makes sure to pull in the other right packages (kdelibs-dbg, gdb, and so on).
*'''FreeBSD ports''' - Please refer to the [http://freebsd.kde.org/faq.php#AKDEapplicationcrashedandIwanttofileabugreportathttpbugskdeorgbutthebacktraceintheKDECrashManagerisuselessWhatcanIdo KDE on FreeBSD FAQ].
*'''Gentoo''' - Gentoo has its [http://www.gentoo.org/proj/en/qa/backtraces.xml own document] describing how to proceed.
*'''Mandriva''' - Mandriva 2007.0 and up has additional debugging packages for all of KDE (in fact, for all of its packages). Just install the corresponding <tt>-debug</tt> package, like <tt>kdebase-debug</tt> and <tt>kdemultimedia-debug</tt>. You probably want to install <tt>kdelibs-debug</tt> anyways.
** Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
*'''Kubuntu/Ubuntu''' - The Ubuntu family makes things quite easy. Every official KDE module has an additional package in the repository, suffixed with <tt>-dbg</tt>. Always install <tt>kdelibs5-dbg</tt>, because all KDE applications use kdelibs (kdelibs-dbg for KDE 3 applications). Then you should install a -dbg package for the application which crashed. For example if KOrganizer crashed you should install <tt>kdepim-dbg</tt> as well. If the program is not from an official KDE module and has no -dbg package, you can install the -dbgsym package from the repository listed on this [https://wiki.kubuntu.org/DebuggingProgramCrash Debugging Program Crashes] page.
**During the Ubuntu development cycle the Apport crash handler is turned on which will report crashes to launchpad.net and do the backtrace for you, if you would rather use the KDE crash handler turn Apport off in /etc/defaults/apport
**Starting with Lucid Lynx (10.04) Kubuntu will be forwarding all non kubuntu specific bugs upstream and had disabled Apport so that DrKonqui will be th edefault crash handler.
*'''openSUSE''' - You should only install the <tt>-debuginfo</tt> packages, for example: <tt>kdepimlibs4-debuginfo</tt>. You can find these packages in [http://en.opensuse.org/KDE/Repositories KDE repositories]. There is also a dedicated [http://en.opensuse.org/openSUSE:Bugreport_application_crashed openSUSE debugging page].
*'''Fedora''' - In Fedora you just need to do:
*# <tt>yum provides "/usr/lib/libkmailprivate.so.4"</tt> to find out which package provides that file;
*# <tt>debuginfo-install kdepim</tt> as root to install debug packages for that package (dependencies included).
*:A complete and detailed guide for Fedora is available in [http://fedoraproject.org/wiki/StackTraces this document] describing how to proceed. Fedora uses a separate debuginfo repository that has to be enabled. Also consider <tt>auto-update-debug-info</tt> yum plugin to keep debuginfo packages up to date.

If your distribution doesn't have debugging-enabled packages for KDE, you'll have to compile KDE from sources:

* If you're using KDE 3, then at the configure stage, you should supply the parameter <tt>--enable-debug=full</tt> in order to build debug symbols in the resulting files.
* If you're using KDE 4, then at the cmake stage, you should supply the parameter <tt>-DCMAKE_BUILD_TYPE=Debug</tt>. If you want to specify your own CXXFLAGS, then use <tt>-DCMAKE_BUILD_TYPE=None -DCMAKE_CXX_FLAGS=$foo</tt> (where $foo is whatever flags you want to set). Note that the Debug build type is highly recommended for most testers.

Then it's just <tt>make</tt> and <tt>make install</tt> as you're used to.

===Crash!===

Now it's time to crash your application. The KDE Crash Dialog should appear right after the crash, which shows the "Developer Information" tab.

[[Image:Kde-crash-handler.png|center|300px|KDE Crash Dialog]]

Click that tab and wait for a minute. This process may take quite some memory, so things may go sluggish all of a sudden. But the result should look much better. For example:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232783168 (LWP 7604)]
[KCrash handler]
#6 0x0806be76 in TreeMapItem::parent (this=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.h:285
#7 0x08065fea in TreeMapItemList::compareItems (this=0xbfec04a8, item1=0x0,
item2=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:720
#8 0xb7281619 in QGList::operator== () from /usr/qt/3/lib/libqt-mt.so.3
#9 0x0806d498 in QPtrList<TreeMapItem>::operator== (this=0xbfec04a8,
list=@0xbfec0468) at /usr/qt/3/include/qptrlist.h:74
#10 0x08062e18 in TreeMapWidget::mousePressEvent (this=0xbfec03ac,
e=0xbfebff1c)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:1840
#11 0xb7004a63 in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb6f6bca7 in QApplication::internalNotify ()
from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb6f6ca88 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb7725a84 in KApplication::notify (this=0xbfec055c, receiver=0xbfec03ac,
event=0xbfebff1c)
at /home/bram/KDE/kde3/kdelibs/kdecore/kapplication.cpp:550
#15 0xb6f0bfd2 in QETWidget::translateMouseEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb6f0b8b0 in QApplication::x11ProcessEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb6f1b761 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb6f82831 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb6f826b6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb6f6b72f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x0805181e in main (argc=134673960, argv=0xffffffff)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/main.cpp:55

This looks better, right? It shows memory addresses, the source files and line numbers and the parameters passed to functions. Which make it more helpful to the developer where to look for the problem.

{{note|You '''need''' GDB installed to get the backtrace of a crash. Please read the next section to know what GDB is, and how to install it.}}

===Retrieving a backtrace with GDB===

In some cases, it is not possible to create a backtrace with the KDE Crash Dialog. This may be caused by an application which entered an infinite loop, or the crash dialog did not appear at all for some reason. You can try to grab a backtrace with <tt>gdb</tt>, the [http://sourceware.org/gdb/ GNU Debugger]. GDB is widely available through distribution packages.

Invoking GDB differs from the situation. You can run an application from inside gdb, or attach gdb to an already running process. The latter may be useful when an application already has entered an infinite loop. But we will first start with running an application inside gdb. From the shell, run:

$ gdb someKDEapp

The GDB prompt will appear. Note that this does not start the application itself, you should run it by invoking the <tt>run</tt> command:

(gdb) run

This will run the application like you are used to, and you can work with it like normal (it only consumes far more memory and may feel sluggish). Now it's time to reproduce your crash. When you succeed, the application just closes and you should return to your GDB prompt. Now it's time to run the 'backtrace' command:

{{note|Some KDE applications (such as JuK and KTorrent) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "run --nofork" at the (gdb) prompt instead of "run" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

(gdb) thread apply all backtrace

This should give a good backtrace which can be posted at the KDE Bugzilla.

In case you want to attach to an existing process, run the following command in the shell:

$ gdb someKDEapp pid

where ''pid'' is the process ID of the process you want to attach to. Once attached, and the process is in an infinite loop, after using the 'backtrace' command again a useful backtrace will appear. You can use 'continue' command to let the application run again and press Ctrl+C in gdb to be able to again enter commands.

=== Retrieving a backtrace when an uncaught exception is causing a crash ===

If your backtrace looks like this:

Thread 1 (Thread 0xb77be730 (LWP 5794)):
[KCrash Handler]
#7 0x00e9b416 in __kernel_vsyscall ()
#8 0x002b1c8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9 0x002b52b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x001c14ed in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0x001bf283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0x001bf2bf in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0x001bf464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
[...]

then only GDB can help getting a useful backtrace. A few more commands are needed. From the shell, run:

$ gdb someKDEapp

Then start loading the application:

{{note|Some KDE applications (such as KMail or Kontact) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "start --nofork" at the (gdb) prompt instead of "start" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

(gdb) start

The GDB prompt will reappear. Turn logging on:

(gdb) set logging file ~/gdblog.txt
(gdb) set logging on

We must now tell gdb to stop just before the exception is thrown. enter:

(gdb) catch __cxa_rethrow

and finally:

(gdb) cont

This will run the application. Note that the application will consume more memory and be slower.
Now reproduce the crash. When you succeed, the application window will look frozen.

Don't worry and switch back to the shell window.
If you see the gdb prompt, type:

(gdb) thread apply all bt

press enter until the (gdb) prompt reappears.

All done! you can now quit gdb:

(gdb) kill

The kill command will stop the program and now enter:

(gdb) quit

Copy/paste the content saved in the ~/gdblog.txt file to your bug report.

===Retrieving a backtrace with Valgrind===

When it comes to crashes, [http://www.valgrind.org Valgrind] is also a useful tool to create a backtrace. It's not a substitution for GDB, but rather a supplement.

When you run an application in valgrind, every piece of memory read or written by the application is being checked. Valgrind will report erroneous memory operations in the standard output or in a log file. Since most crashes are due to an invalid memory read, valgrind can be useful to track down where the problem occurs.

{{note|Valgrind consists of several tools in order to check or profile an application. For this article, we only use memcheck, the default tool when valgrind is being invoked.}}

Like GDB, Valgrind makes running an application much slower, while consuming a lot more resources.

Start the application within valgrind:

$ valgrind --log-file=someKDEapp someKDEapp

Now reproduce the crash. As soon as this happens, the application and valgrind will terminate. What's left is a file named <tt>someKDEapp.pid</tt> where ''pid'' is replaced by the process ID of the valgrind process. The file may list more errors than the one causing the crash. Here's the bit causing the crash which corresponds to the GDB backtrace above:

==23292== Invalid read of size 4
==23292== at 0x806BD9E: TreeMapItem::parent() const (treemap.h:285)
==23292== by 0x8065FB9: TreeMapItemList::compareItems(void*, void*) (treemap.cpp:720)
==23292== by 0x50AC618: QGList::operator==(QGList const&) const (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x806D3BF: QPtrList<TreeMapItem>::operator==(QPtrList<TreeMapItem> const&) const (qptrlist.h:74)
==23292== by 0x8062DE7: TreeMapWidget::mousePressEvent(QMouseEvent*) (treemap.cpp:1840)
==23292== by 0x4E2FA62: QWidget::event(QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D96CA6: QApplication::internalNotify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D97A87: QApplication::notify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4809AC3: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:550)
==23292== by 0x4D36FD1: QETWidget::translateMouseEvent(_XEvent const*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D368AF: QApplication::x11ProcessEvent(_XEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D46760: QEventLoop::processEvents(unsigned) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== Address 0x2C is not stack'd, malloc'd or (recently) free'd

But to be sure, just attach the whole log file to the crash report.

Development/Tutorials/Debugging/How to create useful crash reports

2012-01-26T18:55:08Z

Krop: Add howto for uncaught exceptions crashes

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Debugging/How to create useful crash reports}}
==Introduction==

This document describes how to reproduce a useful backtrace of crashing KDE applications. First, some general information is given. Then, we will describe for several distributions how to prepare your KDE packages and gaining the backtrace. This should be enough for most people.
There are additional sections on how to create backtraces with the GNU Debugger and with Valgrind, which are in some cases useful.

==How to create useful crash reports==

A good crash report at [http://bugs.kde.org Bugzilla] consists of two parts: a '''description''' of how to reproduce the crash and a '''backtrace''' of the crash. With one of those elements missing, it is much harder (if not impossible) for developers to tackle the problem.

A description should consist of more than only "it crashed". Try to describe everything you did prior to the crash. Did you click on a button, opened a particular website or file which caused problems? That little detail which may look useless to you may be useful for the developer, so just write it down.

A more insightful article on how to write good bug descriptions is available [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html at this link], please read that before reporting bugs.

Don't attach the backtrace to the bug report. Instead, simply paste it. This way it is much easier for developers to search for duplicate reports, because attachments will not be searched.

If you paste a backtrace to a report, make sure you strip all but one or two of the
(no debugging symbols found)
lines from the backtrace as they make it harder to read.

Even though pasting backtraces directly is preferred over adding an attachment, please do not paste other things like logs (valgrind, strace or terminal output) or example data (mails, HTML files and so on). Use attachments for these items.

===Backtraces===

Backtraces are essential. They may look meaningless to you, but they might actually contain a wealth of useful information. A backtrace describes which functions were called prior to the crash, so that developers may track down in which function the mess started. Having good backtraces has a downside: [[Development/Tutorials/Debugging/Debugging_symbols|libraries and executables occupy much more disk space than their optimized counter parts]]. That's the reason why many distros choose to install stripped files, '''which results in useless backtraces''':

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233848624 (LWP 12212)]
[New Thread -1255081072 (LWP 12820)]
[New Thread -1240921200 (LWP 12819)]
[New Thread -1266680944 (LWP 12818)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6a1210b in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6a85afe in ?? () from /usr/lib/libX11.so.6
#3 0x00000003 in ?? ()
#4 0x082149c0 in ?? ()
#5 0x00003ffc in ?? ()
#6 0x00000000 in ?? ()

But no worries, with some modifications you can create full blown backtraces for KDE applications.

===Preparing your KDE packages===

If your distribution has debugging-enabled packages, install them.

It is easy to see which debug packages you are missing from looking at the backtrace. For example, take the following line from a backtrace:

#6 0xb7975bdc in ?? () from /usr/lib/libkmailprivate.so.4

The <tt>??</tt> indicates that the library <tt>libkmailprivate.so.4</tt> does not have debug information, which might be available in separate debug packages. In this case, it is pretty easy to guess that you need to install debug packages for KMail to get a better backtrace.

Sometimes, you need to install more than one debug package to get a good backtrace. This depends on how the distribution splits up the packages. For example, for some distributions it is enough to install the debug package for <tt>kdepim</tt> to get enough debugging information for a crash in KMail, for other distributions there is an additional debug package just for KMail.

Here's a list of how to obtain debug packages for some distributions:

*'''Debian''' - Debian offers <tt>-dbg</tt> packages to easy create useful backtraces. Just install the corresponding <tt>-dbg</tt> package. e.g. <tt>kdepim-dbg</tt> for KMail crashes. The dependencies of -dbg makes sure to pull in the other right packages (kdelibs-dbg, gdb, and so on).
*'''FreeBSD ports''' - Please refer to the [http://freebsd.kde.org/faq.php#AKDEapplicationcrashedandIwanttofileabugreportathttpbugskdeorgbutthebacktraceintheKDECrashManagerisuselessWhatcanIdo KDE on FreeBSD FAQ].
*'''Gentoo''' - Gentoo has its [http://www.gentoo.org/proj/en/qa/backtraces.xml own document] describing how to proceed.
*'''Mandriva''' - Mandriva 2007.0 and up has additional debugging packages for all of KDE (in fact, for all of its packages). Just install the corresponding <tt>-debug</tt> package, like <tt>kdebase-debug</tt> and <tt>kdemultimedia-debug</tt>. You probably want to install <tt>kdelibs-debug</tt> anyways.
** Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
*'''Kubuntu/Ubuntu''' - The Ubuntu family makes things quite easy. Every official KDE module has an additional package in the repository, suffixed with <tt>-dbg</tt>. Always install <tt>kdelibs5-dbg</tt>, because all KDE applications use kdelibs (kdelibs-dbg for KDE 3 applications). Then you should install a -dbg package for the application which crashed. For example if KOrganizer crashed you should install <tt>kdepim-dbg</tt> as well. If the program is not from an official KDE module and has no -dbg package, you can install the -dbgsym package from the repository listed on this [https://wiki.kubuntu.org/DebuggingProgramCrash Debugging Program Crashes] page.
**During the Ubuntu development cycle the Apport crash handler is turned on which will report crashes to launchpad.net and do the backtrace for you, if you would rather use the KDE crash handler turn Apport off in /etc/defaults/apport
**Starting with Lucid Lynx (10.04) Kubuntu will be forwarding all non kubuntu specific bugs upstream and had disabled Apport so that DrKonqui will be th edefault crash handler.
*'''openSUSE''' - You should only install the <tt>-debuginfo</tt> packages, for example: <tt>kdepimlibs4-debuginfo</tt>. You can find these packages in [http://en.opensuse.org/KDE/Repositories KDE repositories]. There is also a dedicated [http://en.opensuse.org/openSUSE:Bugreport_application_crashed openSUSE debugging page].
*'''Fedora''' - In Fedora you just need to do:
*# <tt>yum provides "/usr/lib/libkmailprivate.so.4"</tt> to find out which package provides that file;
*# <tt>debuginfo-install kdepim</tt> as root to install debug packages for that package (dependencies included).
*:A complete and detailed guide for Fedora is available in [http://fedoraproject.org/wiki/StackTraces this document] describing how to proceed. Fedora uses a separate debuginfo repository that has to be enabled. Also consider <tt>auto-update-debug-info</tt> yum plugin to keep debuginfo packages up to date.

If your distribution doesn't have debugging-enabled packages for KDE, you'll have to compile KDE from sources:

* If you're using KDE 3, then at the configure stage, you should supply the parameter <tt>--enable-debug=full</tt> in order to build debug symbols in the resulting files.
* If you're using KDE 4, then at the cmake stage, you should supply the parameter <tt>-DCMAKE_BUILD_TYPE=Debug</tt>. If you want to specify your own CXXFLAGS, then use <tt>-DCMAKE_BUILD_TYPE=None -DCMAKE_CXX_FLAGS=$foo</tt> (where $foo is whatever flags you want to set). Note that the Debug build type is highly recommended for most testers.

Then it's just <tt>make</tt> and <tt>make install</tt> as you're used to.

===Crash!===

Now it's time to crash your application. The KDE Crash Dialog should appear right after the crash, which shows the "Developer Information" tab.

[[Image:Kde-crash-handler.png|center|300px|KDE Crash Dialog]]

Click that tab and wait for a minute. This process may take quite some memory, so things may go sluggish all of a sudden. But the result should look much better. For example:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232783168 (LWP 7604)]
[KCrash handler]
#6 0x0806be76 in TreeMapItem::parent (this=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.h:285
#7 0x08065fea in TreeMapItemList::compareItems (this=0xbfec04a8, item1=0x0,
item2=0x0)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:720
#8 0xb7281619 in QGList::operator== () from /usr/qt/3/lib/libqt-mt.so.3
#9 0x0806d498 in QPtrList<TreeMapItem>::operator== (this=0xbfec04a8,
list=@0xbfec0468) at /usr/qt/3/include/qptrlist.h:74
#10 0x08062e18 in TreeMapWidget::mousePressEvent (this=0xbfec03ac,
e=0xbfebff1c)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/treemap.cpp:1840
#11 0xb7004a63 in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb6f6bca7 in QApplication::internalNotify ()
from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb6f6ca88 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb7725a84 in KApplication::notify (this=0xbfec055c, receiver=0xbfec03ac,
event=0xbfebff1c)
at /home/bram/KDE/kde3/kdelibs/kdecore/kapplication.cpp:550
#15 0xb6f0bfd2 in QETWidget::translateMouseEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb6f0b8b0 in QApplication::x11ProcessEvent ()
from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb6f1b761 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb6f82831 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb6f826b6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb6f6b72f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x0805181e in main (argc=134673960, argv=0xffffffff)
at /home/bram/KDE/kde3/kdeaddons/konq-plugins/fsview/main.cpp:55

This looks better, right? It shows memory addresses, the source files and line numbers and the parameters passed to functions. Which make it more helpful to the developer where to look for the problem.

{{note|You '''need''' GDB installed to get the backtrace of a crash. Please read the next section to know what GDB is, and how to install it.}}

===Retrieving a backtrace with GDB===

In some cases, it is not possible to create a backtrace with the KDE Crash Dialog. This may be caused by an application which entered an infinite loop, or the crash dialog did not appear at all for some reason. You can try to grab a backtrace with <tt>gdb</tt>, the [http://sourceware.org/gdb/ GNU Debugger]. GDB is widely available through distribution packages.

Invoking GDB differs from the situation. You can run an application from inside gdb, or attach gdb to an already running process. The latter may be useful when an application already has entered an infinite loop. But we will first start with running an application inside gdb. From the shell, run:

$ gdb someKDEapp

The GDB prompt will appear. Note that this does not start the application itself, you should run it by invoking the <tt>run</tt> command:

(gdb) run

This will run the application like you are used to, and you can work with it like normal (it only consumes far more memory and may feel sluggish). Now it's time to reproduce your crash. When you succeed, the application just closes and you should return to your GDB prompt. Now it's time to run the 'backtrace' command:

{{note|Some KDE applications (such as JuK and KTorrent) have special code to ensure that there is only one running instance of the application at a time. For these applications you should type in "run --nofork" at the (gdb) prompt instead of "run" because otherwise gdb will try to debug the wrong process. If you are unsure as to whether to use --nofork just try it. If the application says it's an unknown option you can remove --nofork.}}

(gdb) thread apply all backtrace

This should give a good backtrace which can be posted at the KDE Bugzilla.

In case you want to attach to an existing process, run the following command in the shell:

$ gdb someKDEapp pid

where ''pid'' is the process ID of the process you want to attach to. Once attached, and the process is in an infinite loop, after using the 'backtrace' command again a useful backtrace will appear. You can use 'continue' command to let the application run again and press Ctrl+C in gdb to be able to again enter commands.

=== Retrieving a backtrace when an uncaught exception is causing a crash ===

If your backtrace looks like this:

Thread 1 (Thread 0xb77be730 (LWP 5794)):
[KCrash Handler]
#7 0x00e9b416 in __kernel_vsyscall ()
#8 0x002b1c8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9 0x002b52b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x001c14ed in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0x001bf283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0x001bf2bf in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0x001bf464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
[...]

then only GDB can help getting a useful backtrace. A few more commands are needed. From the shell, run:

$ gdb someKDEapp

Then start loading the application:

(gdb) start

The GDB prompt will reappear. Turn logging on:

(gdb) set logging file ~/gdblog.txt
(gdb) set logging on

We must now tell gdb to stop just before the exception is thrown. enter:

(gdb) catch __cxa_rethrow

and finally:

(gdb) cont

This will run the application. Note that the application will consume more memory and be slower.
Now reproduce the crash. When you succeed, the application window will look frozen.

Don't worry and switch back to the shell window.
If you see the gdb prompt, type:

(gdb) thread apply all bt

press enter until the (gdb) prompt reappears.

All done! you can now quit gdb:

(gdb) kill

The kill command will stop the program and now enter:

(gdb) quit

Copy/paste the content saved in the ~/gdblog.txt file to your bug report.

===Retrieving a backtrace with Valgrind===

When it comes to crashes, [http://www.valgrind.org Valgrind] is also a useful tool to create a backtrace. It's not a substitution for GDB, but rather a supplement.

When you run an application in valgrind, every piece of memory read or written by the application is being checked. Valgrind will report erroneous memory operations in the standard output or in a log file. Since most crashes are due to an invalid memory read, valgrind can be useful to track down where the problem occurs.

{{note|Valgrind consists of several tools in order to check or profile an application. For this article, we only use memcheck, the default tool when valgrind is being invoked.}}

Like GDB, Valgrind makes running an application much slower, while consuming a lot more resources.

Start the application within valgrind:

$ valgrind --log-file=someKDEapp someKDEapp

Now reproduce the crash. As soon as this happens, the application and valgrind will terminate. What's left is a file named <tt>someKDEapp.pid</tt> where ''pid'' is replaced by the process ID of the valgrind process. The file may list more errors than the one causing the crash. Here's the bit causing the crash which corresponds to the GDB backtrace above:

==23292== Invalid read of size 4
==23292== at 0x806BD9E: TreeMapItem::parent() const (treemap.h:285)
==23292== by 0x8065FB9: TreeMapItemList::compareItems(void*, void*) (treemap.cpp:720)
==23292== by 0x50AC618: QGList::operator==(QGList const&) const (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x806D3BF: QPtrList<TreeMapItem>::operator==(QPtrList<TreeMapItem> const&) const (qptrlist.h:74)
==23292== by 0x8062DE7: TreeMapWidget::mousePressEvent(QMouseEvent*) (treemap.cpp:1840)
==23292== by 0x4E2FA62: QWidget::event(QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D96CA6: QApplication::internalNotify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D97A87: QApplication::notify(QObject*, QEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4809AC3: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:550)
==23292== by 0x4D36FD1: QETWidget::translateMouseEvent(_XEvent const*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D368AF: QApplication::x11ProcessEvent(_XEvent*) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== by 0x4D46760: QEventLoop::processEvents(unsigned) (in /usr/qt/3/lib/libqt-mt.so.3.3.8)
==23292== Address 0x2C is not stack'd, malloc'd or (recently) free'd

But to be sure, just attach the whole log file to the crash report.

Projects/MovetoGit

2010-10-25T13:05:02Z

Krop: /* Write / update importing rules for svn2git */

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

'''New! [http://community.kde.org/Sysadmin/DeveloperAccessForRuleWriting The best way you can help us migrate]'''

=The Plan=

KDE is, eventually, moving to Git. We will be using gitolite + Redmine + reviewboard on our own servers.

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE.

After it has been decided in Jun 2010 to use our own servers, Amarok and Konversation moved to git.kde.org/projects.kde.org to test the waters and find problems that would affect KDE.

Once those problems have been solved, all of KDE will be able to switch.

A full schedule for the git infrastructure can be found [http://community.kde.org/Sysadmin/GitInfrastructureLaunch here].

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on git.kde.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The projects.kde.org site will have a list (lists?) of all these repositories using the redmine project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.
Details on the reasoning behind this layout is available [[Projects/MoveToGit/Layout|here]].

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

All KDE developers will in principle be able to use their existing "svn" accounts. Developers using HTTPS ideally would request their HTTPS SVN account to be converted to SSH as that makes it easiest for the KDE sysadmins, but alternatively they can also just provide a public key. At some point the KDE sysadmins are going to send everybody with a HTTPS SVN account an email with a link to a web app to collect their key (see http://www.omat.nl/2010/06/13/sysamin-update-your-email-address/).

From the times when gitorious.org was the preferred hosting solution, a procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].
Many points probably still apply, but have to be updated.

=Blockers=

Tasks that need to get done before we can migrate

==Setup git.kde.org==
{{Progress bar|100}}
'''Owner:''' Eike, Jeff, Sysadmin team

'''Status:''' ''Progressing''

: It [http://lists.kde.org/?l=kde-scm-interest&m=127612957219466&w=2 has been decided] to use gitolite + Redmine + reviewboard on our own servers rather than gitorious.org. Sysadmin team is preparing git.kde.org for this.

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - volunteers needed!

'''Status:''' ''sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]]

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|pumphaus/Arno Rehn
|90
|Includes nearly everything; some history from playground might be missing. Some tags from the CVS days don't have a parent yet - still have to figure out why.
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeedu/marble
|jmho
|100
|Contains: trunk with moves (playground->kdereview->kdeedu), regular kde branches/tags and the following other branches: marble-0.4, gsoc-2009 and geodata-nt. Checking done: gitk --all, verify-git-from-svn
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|tnyblom
|95
|Needs verification.
|-
|SC/kdepim-runtime
|tnyblom
|95
|Needs verification.
|-
|SC/kdepimlibs
|tnyblom
|95
|Needs verification.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 85
| Branches are done, I'm working on tags.
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|kdesupport/soprano
|cgiboudeaux
|100
|Ready to migrate
|-
|kdesupport/attica
|cgiboudeaux
|100
|Ready to migrate
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|90}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
*** Internally used tools have been updated and are now being used to access git repos such as dbus.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
*** Most of the technical work regarding migration of kdepim repos has been completed by community member Torgny Nyblom.
* Tool knowledge
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
*** Workshops and use of git-svn have been used to bring developers up to speed on how to use git at some level.

=Nice to have before the migration=

==Push log==
{{Progress bar|100}}
'''Owner:''' sysadmin

'''Status:''' finished

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

-----------

Gitolite includes this functionality inbuilt to itself, although all repositories are logged in the same file - bcooksley

==Script for downloading virtual KDE hierarchies==
{{Progress bar|99}}
'''Owner''':

'''Status:'''

:we already have kdesvn-build, build-tool and mr: three good tools for managing repos.

Most people use kdesrc-build; it will neither eat babies nor kittens. it has options for updating everything or individual modules, can do fetch-only or build-only, etc..
Command-line options for updating the configuration would be a nice addition.

TODO: details on mr and build-tool

note: scripty also has its own list of repos. it's just in a rather weird bash file.

'''Discussion:'''

As far as I can see, kdesvn-build is able to do it, it should be just a matter of providing a configuration. As I'm not using build-tool, I can't say anything about it. --jmho

'''Links'''
*[http://kdesvn-build.kde.org/ kdesvn-build]
*[[Projects/MovetoGit/MassCloneScript]]
*[http://rubyforge.org/projects/build-tool/ build-tool]
*TODO: link to mr

==pre-receive hooks==
{{Progress bar|50}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

This has now been ported to Git - bcooksley

Note however that it doesn't look for a .gitattributes file yet - patches welcome ( see sysadmin/repo-management on git.kde.org )

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Snapshot to read-only svn==
{{Progress bar|100}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

Scripty operates on a git clone of the repo's. No need for this item imho -- toma

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|100}}
'''Owner:''' sysadmin
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''
:sysadmin will add mirrors as needed and is prepared for it. -- toma

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|50|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

Is this section still necessary at all? Perhaps some branding has to be done for redmine or cgit, but I don't know. --jmho

Neverendingo is looking at this as needed --toma

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|100}}

'''Owner:''' sysadmin

:Gitolite allows sysadmin to permit certain people on certain repos only to manage both branches and tag without needing force push rights.

'''Discussion'''

==Account setup for Gitolite==
{{Progress bar|100}}

'''Owner:''' ''sysadmin''

:Accounts for existing SVN accounts which use SSH for access have been automatically granted access to Gitolite. Those who are still using HTTPS need to file a sysadmin bug to change their SVN account to SSH and will recieve Git access automatically.

==post-update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

Working fine in the new setup, --toma

=Completed Tasks=

==Get rid of svn:externals==
{{Progress bar|100}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)

= other notes =

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Development/Tutorials/CMake

2010-10-16T16:53:10Z

Krop: /* Using CMake for a KDE Project */

{{Template:I18n/Language Navigation Bar|Development/Tutorials/CMake}}

== Introduction ==
[http://www.cmake.org CMake] reads script files and produces input files for the native buildsystem of the platform where it runs on. It can create GNU Makefiles, KDevelop project files, XCode project files, and Visual Studio project files.

[http://www.cmake.org CMake] is free software and released under a BSD license. It is developed by [http://www.kitware.com Kitware Inc.]

You can find more CMake related information on the [[Development/CMake | main CMake page]] here on TechBase.

== Why use CMake ? ==
CMake is the official tool of KDE 4 release, decided in March 2006, primarily due to technical merits as compared to the older KDE tools automake and unsermake:
* CMake is developed independently of KDE, it can be used by other projects as well
* Compilation time is much faster, mainly due to not using libtool anymore
* The build files are easier to write

== How to compile KDE using CMake==

=== Get and install CMake ===
==== Linux, BSD, and other Unix Systems ====
Retrieve the latest stable version of CMake from [http://www.cmake.org/HTML/Download.html here].

Once downloaded, unpack and compile it:
<code>
$ mkdir cmake-build
$ cd cmake-build
$ ../bootstrap
$ make
$ make install
</code>

By default, this will install CMake in /usr/local, so make sure to have /usr/local/bin in your execute path. To change the installation prefix (e.g. to /usr in debian), add the '--prefix=PATH' option to the bootstrap command.

Please follow the instructions located [http://cmake.org/HTML/Download.html#cvs here] if you would like to use the current development version.

==== Windows ====
Retrieve the latest stable version of CMake from [http://www.cmake.org/HTML/Download.html here].

Once downloaded, run the cmake installer.

By default, this will install CMake in C:\Program Files\CMake 2.8, so make sure to have <installpath>\bin in your execute path.

Please follow the instructions at [http://cmake.org/HTML/Download.html#cvs here] if you would like to use the current development version.

=== Run CMake ===

==== Linux, BSD, and other Unix Systems ====
You have to run CMake so that it generates the build files for your system. Both in-source and out-of-source builds are supported by CMake, but currently in-source builds are prevented by the KDE implementation.

So, let's say you have kdelibs/ in ~/src/kdelibs/, then do the following:
<code>
$ ls
kdelibs/
$ mkdir kdelibs-build
$ cd kdelibs-build
$ cmake ../kdelibs
</code>
This will generate the Makefiles for building kdelibs/ in kdelibs-build/.

==== Windows ====
You have to run CMake so that it generates the build files for your system. Both in-source and out-of-source builds are supported by CMake, but currently in-source builds are prevented by the KDE implementation.

So, let's say you have kdelibs\ in c:\daten\kde4, then do the following:
<code>
c:\daten\kde4> cd kdelibs\win
c:\daten\kde4> cmake
c:\daten\kde4> make
c:\daten\kde4> make install
c:\daten\kde4> cd ..
c:\daten\kde4> mkdir kdelibs-build
c:\daten\kde4> cd kdelibs-build
c:\daten\kde4\kdelibs-build> cmake ..\kdelibs
</code>

This will generate the Makefiles for building kdelibs\ in kdelibs-build\. See [[Projects/KDE_on_Windows|KDE on Windows]] for more informations about compiling KDE on Windows.

==== KDevelop 3 Project Files ====
If you prefer project files for KDevelop 3 (which will basically be Makefiles accompanied by some extra files for KDevelop), run it like this:
<code>
$ cmake ../kdelibs -GKDevelop3
</code>
Use 'cmake -h' to find out which generators CMake supports and the other options.

==== CMake and Qt4 ====
To locate Qt 4, CMake searches for qmake in your execute path. CMake does ''not'' use the QTDIR environment variable. So make sure that the first qmake found in the execution path is the one you like to use.

==== More Details ====
When CMake has finished, it will have created a file called "CMakeCache.txt". This file contains all the settings CMake has detected on your system. If you want to run CMake with another generator or you want CMake to detect everything again, delete this file.

If CMake didn't find something, but you know it is somewere on your box, you can tell CMake manually where to find it. CMake uses variables to store this information. These variables are cached in the already mentioned file CMakeCache.txt. You have three options to adjust these variables manually:
* tell CMake the correct value via the command line: cmake ../kdelibs -DNAME_OF_THE_VARIABLE=value
* use ccmake, which provides a curses based GUI to adjust the CMake variables (run: ccmake ../kdelibs)
* edit the file CMakeCache.txt directly (not recommended)

You should run "ccmake ../kdelibs" at least once so that you get an impression which variables CMake uses. Press "T" to see also the "advanced" variables. So, if CMake didn't find something, start ccmake and adjust it manually.

==== Command Line Variables ====

Some cmake command line variables you may want to set:
* '''CMAKE_INSTALL_PREFIX''': cmake ../kdelibs -DCMAKE_INSTALL_PREFIX=/opt/kde4 is the equivalent to ./configure --prefix=/opt/kde4
* '''[[Development/CMake/Addons_for_KDE#Buildtypes|CMAKE_BUILD_TYPE]]''': decide which type of build you want. You can choose between "debugfull", "Debug", "Profile", "RelWithDebInfo" and "Release". The default is "RelWithDebInfo". Please refer to page [[Development/CMake/Addons_for_KDE#Buildtypes|CMake Build Types]] for a more detailed explanation.
* '''KDE4_BUILD_TESTS=ON''': creates Makefiles with build test programs and also provides 'test' targets
* '''KDE4_TEST_OUTPUT=xml''': Unit tests using the QTestLib framework will create xml formatted logfiles.
* '''KDE4_DISABLE_MULTIMEDIA=ON''': Build KDE without any multimedia (audio and video) support.
* '''BUILD_foo=OFF''': disables the build for the project in subdirectory 'foo'.
* '''WITH_foo''': there are several options, e.g. WITH_CUPS or WITH_Jasper. If you disable them, cmake will not even try to find this package. If it is enabled, cmake will try to find it. If it fails with this, you can still adjust it manually as described above.

=== Environment Variables ===
If you have headers and libraries installed in non-standard locations that cmake cannot find (e.g., fink on Mac OSX installs to /sw), then populate the environment variable CMAKE_PREFIX_PATH with a list of paths to these locations. When searching for headers, libraries and binaries, CMake will search all the paths in CMAKE_PREFIX_PATH as well as their standard subdirectories ("lib" for libraries, "include" for headers and "bin" for binaries). This can be also very useful e.g. if you install kdesupport to ~/install/kdesupport.
* '''CMAKE_PREFIX_PATH''', eg. export CMAKE_PREFIX_PATH=/sw

If you need to further tweak the search behavior, you can additionally set the
following environment variables in order to add library, include or binary
directories to your search path:
* '''CMAKE_INCLUDE_PATH''', eg. export CMAKE_PREFIX_PATH=/sw/include
* '''CMAKE_LIBRARY_PATH''', eg. export CMAKE_LIBRARY_PATH=/sw/lib
* '''CMAKE_PROGRAM_PATH''', eg. export CMAKE_PROGRAM_PATH=/sw/bin

For more information on variables, see [http://www.cmake.org/Wiki/CMake_Useful_Variables this cmake.org wiki page]

=== Going Further ===
If cmake finishes with "Generating done" then there was no errors, but if it finishes with "Configuring done" then there was errors that you have to fix. Once cmake finishes successfully, run your buildtool (i.e. make, KDevelop, XCode or MSVC) and build and wait until it has finished. Then "make install".

If you got a failure that says something like
<code>
CMake Error: This project requires some variables to be set,
and cmake can not find them.
Please set the following variables:
X11_XTest_LIB (ADVANCED)
</code>
then you may have a missing library (or other dependency). To find
out which library, search in the cmake/modules directory for
the variable that cmake can't find. In the example above, it is
<code>
find_library(X11_XTest_LIB Xtst ${X11_LIB_SEARCH_PATH})
</code>
So the missing library is Xtst. You then need to find it (perhaps installing a libXtst-devel library) and re-run cmake.

== Using CMake for a Simple Application ==

Here's the most simple CMakeLists.txt:
<code>
add_executable(hello main.cpp)
</code>
This will create an executable named "hello" (or "hello.exe" under Windows) from the source file main.cpp. You can mix C and C++ files as you want. You can have multiple executables and libraries in one CMakeLists.txt. The same source file can be used in multiple targets, it will be compiled for each target independently from the other targets. Probably the most important part of the cmake language are the variables:
<code>
set( MY_SOURCES main.cpp widget.cpp)
message(STATUS "my sources: ${MY_SOURCES}")
</code>
So, use the SET() command to set the value of a variable. If you list more than one string, the variable will be a list. A list is a list of strings separated by semicolons. If you set it to only one item, it will have just that value. To get the value of a variable, use ${VAR}.
You can iterate over a list using FOREACH():
<code>
foreach(next_ITEM ${MY_SOURCES})
message(STATUS "next item: ${next_ITEM}")
endforeach(next_ITEM ${MY_SOURCES})
</code>
The commands in CMake are case-insensitive. Names of variables and names of parameter are case-sensitive.

You can also test for various things:
<code>
if (UNIX)
message(STATUS "This is UNIX (including OS X and CygWin)")
endif (UNIX)

if (MSVC)
set(MY_SRCS ${MY_SRCS} winextra.cpp)
endif (MSVC)
</code>
In this second example you can see also how to append items to a list.

In the cmake Wiki there is also a [http://www.cmake.org/Wiki/HowToBuildKDE4Software tutorial] on using cmake to build KDE 4 software. It is recommended reading.

== Using CMake for a KDE Project ==

Here's a basic CMakeList file that builds a small KDE 4 project:
<code>
project( kde4project )
find_package( KDE4 REQUIRED )
include(KDE4Defaults)

include_directories( ${KDE4_INCLUDES} )

set( KDE4ProjectSources kde4mainapp.cpp someclass.cpp someotherclass.cpp )

kde4_add_executable( kde4project ${KDE4ProjectSources} )

target_link_libraries( kde4project ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )

install( TARGETS kde4project ${INSTALL_TARGETS_DEFAULT_ARGS} )
</code>

''target_link_libraries'' contains the development libraries that are linked to your program. E.g. if you want to link to libtidy-devel, your library file name may be called /usr/local/lib/libtidy.a. You would then add -ltidy to a gcc call. Here, you add ''tidy'' to your target_link_libraries. If possible, use pre-defined variables or macros like ${KDE4_KDEUI_LIBS}.

''install (TARGETS'' is where the target will finally be installed. If you do not have this line, make install will not be available.

Variables, macros and other useful information specific to KDE can be found at the [[Development/CMake/Addons for KDE|CMake addons for KDE]] page.

== Extending CMake ==
CMake can be extended using cmake scripts. CMake comes with a number of scripts; under UNIX they are by default installed to /usr/local/share/CMake/Modules/. The KDE libraries install also a set of cmake modules into share/apps/cmake/modules/. The files located there will be preferred over the ones in the system global cmake module path.
For detecting software packages there are FindFOO.cmake files, see [http://www.cmake.org/Wiki/CMake_HowToFindInstalledSoftware here] for more information.
You can also write macros in CMake. They are powerful enough to do most things you will need to build software, but they are not intended to be used as a general purpose programming language.

== Converting autotools-based KDE software to CMake ==
In kdesdk/cmake/ you can find a script am2cmake . This is a ruby script, so you need to have ruby installed. Run am2cmake in the toplevel directory of your sources:
<code>
$ cd src/mykooltool/
$ am2cmake --kde4
</code>
Don't forget the switch "--kde4", otherwise it won't generate files suitable for KDE 4 software. The converted files 'may' work as they are, but complicated projects will require some additional editing.

You may have to:
* add more include direcories, using INCLUDE_DIRECTORIES()
* add more link libraries, using TARGET_LINK_LIBRARIES()
* add some compile switches, using ADD_DEFINITIONS()
* add some "configure" checks, see [http://www.cmake.org/Wiki/CMake_HowToDoPlatformChecks How To Do Platform Checks] and [http://www.cmake.org/Wiki/CMake_HowToFindInstalledSoftware How To Find Installed Software]
* take special care of former libtool convenience libraries. They are not supported by cmake, instead there will be a file ConvenienceLibs.cmake created. In this file you will find for every convenience lib a variable, which contains all source files of this convenience lib. For the targets which linked to this convenience lib, just add the variable to the sources.
* a file AdditionalInfo.txt will be created. There you will see all *.in and *.in.in files of your project. The stuff done in these files will have to be converted manually to cmake.

[[Category:Programming]]
[[Category:Tutorial]]
[[Category:FAQs]]

Projects/MoveToGit/UsingSvn2Git

2010-10-11T12:47:39Z

Krop: /* Getting the tools */

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git]. To get started do:

<code bash>
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://git.kde.org/kde-ruleset.git
</code>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tags/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it
has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <code bash>svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</code>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All matching rules need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

=== Setting up your system ===

You will need ~65GB of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check wether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/trunk/KDE/module</pre>

Please note that '/path/to/kde_svn/' is the path to the 65GB you downloaded, and the 'trunk/KDE/module' is the module you want to write rules for, but those two put together is *not* a path that physically exists on your disk. svn log is smart enough to do what you want.

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the kde_svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module kde_svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Checking for proper history in the new git repository ====
A very easy way to check wether the history was imported properly is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check wether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

==== How to update the account-map file ====

Currently, account-map file is being generated with 'generateAccountMap'[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/generateAccountMap] script which parses kde-common/accounts[http://websvn.kde.org/trunk/kde-common/accounts?view=log] and kde-common/disabled-accounts[http://websvn.kde.org/trunk/kde-common/disabled-accounts?view=log] from SVN.

Once you have your git repository you should check if there are accounts not listed in account-map file (you can use checkMissingAccounts[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/checkMissingAccounts]), if that is the case, check if the missing accounts are listed in kde-common/accounts or kde-common/disabled-accounts, if it's not there file a sysadmin bug report[https://bugs.kde.org/enter_sysadmin_request.cgi] to get your missing account included in disabled-accounts. Once you get your missing accounts included in disabled accounts, you could generate the account-map file running 'bin/generateAccountMap', then run svn-all-fast-export again. Do not edit account-map file directly!

=== Troubleshooting ===

==== Recurse action doesn't work with cvs2svn tag commits ====

You may have to deal with a commit done by cvs2svn to create a tag, for example:
<pre>
r386536 | (no author) | 2005-02-05 22:16:00 +0100 (Sat, 05 Feb 2005) | 2 lines
Changed paths:
A /branches/beta_0_7_branch (from /trunk:386535)
D /branches/beta_0_7_branch/art-devel
D /branches/beta_0_7_branch/arts
D /branches/beta_0_7_branch/bugs
D /branches/beta_0_7_branch/devel-home
D /branches/beta_0_7_branch/developer.kde.org
D /branches/beta_0_7_branch/enterprise.kde.org
D /branches/beta_0_7_branch/events.kde.org
D /branches/beta_0_7_branch/foundation
D /branches/beta_0_7_branch/kckde
D /branches/beta_0_7_branch/kde-common
D /branches/beta_0_7_branch/kde-i18n
D /branches/beta_0_7_branch/kde-qt-addon
D /branches/beta_0_7_branch/kde-women.kde.org
D /branches/beta_0_7_branch/kdeaccessibility
D /branches/beta_0_7_branch/kdeaddons
D /branches/beta_0_7_branch/kdeadmin
D /branches/beta_0_7_branch/kdeartwork
D /branches/beta_0_7_branch/kdebase
D /branches/beta_0_7_branch/kdebindings
D /branches/beta_0_7_branch/kdeedu
D /branches/beta_0_7_branch/kdeextragear-1
D /branches/beta_0_7_branch/kdeextragear-2
M /branches/beta_0_7_branch/kdeextragear-3
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.am.in
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.cvs
D /branches/beta_0_7_branch/kdeextragear-3/README
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.bot
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.in
D /branches/beta_0_7_branch/kdeextragear-3/digikam
D /branches/beta_0_7_branch/kdeextragear-3/digikamimageplugins
D /branches/beta_0_7_branch/kdeextragear-3/doc
D /branches/beta_0_7_branch/kdeextragear-3/filelight
D /branches/beta_0_7_branch/kdeextragear-3/kcfgcreator
D /branches/beta_0_7_branch/kdeextragear-3/kconfigeditor
D /branches/beta_0_7_branch/kdeextragear-3/kdebluetooth
D /branches/beta_0_7_branch/kdeextragear-3/kdetv
D /branches/beta_0_7_branch/kdeextragear-3/keurocalc
D /branches/beta_0_7_branch/kdeextragear-3/kiosktool
D /branches/beta_0_7_branch/kdeextragear-3/klicker
D /branches/beta_0_7_branch/kdeextragear-3/kplayer
D /branches/beta_0_7_branch/kdeextragear-3/pwmanager
D /branches/beta_0_7_branch/kdeextragear-libs-1
D /branches/beta_0_7_branch/kdegames
D /branches/beta_0_7_branch/kdegraphics
D /branches/beta_0_7_branch/kdeinstaller
D /branches/beta_0_7_branch/kdejava
D /branches/beta_0_7_branch/kdekiosk
D /branches/beta_0_7_branch/kdelibs
D /branches/beta_0_7_branch/kdemultimedia
D /branches/beta_0_7_branch/kdenetwork
D /branches/beta_0_7_branch/kdenonbeta
D /branches/beta_0_7_branch/kdenox
D /branches/beta_0_7_branch/kdepim
D /branches/beta_0_7_branch/kdeplayground-artwork
D /branches/beta_0_7_branch/kdeplayground-base
D /branches/beta_0_7_branch/kdeplayground-edu
D /branches/beta_0_7_branch/kdeplayground-games
D /branches/beta_0_7_branch/kdeplayground-ioslaves
D /branches/beta_0_7_branch/kdeplayground-multimedia
D /branches/beta_0_7_branch/kdeplayground-network
D /branches/beta_0_7_branch/kdeplayground-pim
D /branches/beta_0_7_branch/kdeplayground-utils
D /branches/beta_0_7_branch/kdereview
D /branches/beta_0_7_branch/kdesdk
D /branches/beta_0_7_branch/kdesecurity
D /branches/beta_0_7_branch/kdesupport
D /branches/beta_0_7_branch/kdetoys
D /branches/beta_0_7_branch/kdeutils
D /branches/beta_0_7_branch/kdevelop
D /branches/beta_0_7_branch/kdewebdev
D /branches/beta_0_7_branch/kdoc
D /branches/beta_0_7_branch/kfte
D /branches/beta_0_7_branch/khtmltests
D /branches/beta_0_7_branch/klyx
D /branches/beta_0_7_branch/kmusic
D /branches/beta_0_7_branch/koffice
D /branches/beta_0_7_branch/kofficetests
D /branches/beta_0_7_branch/konstruct
D /branches/beta_0_7_branch/qt-copy
D /branches/beta_0_7_branch/quanta
D /branches/beta_0_7_branch/sysconfig
D /branches/beta_0_7_branch/valgrind
D /branches/beta_0_7_branch/www

This commit was manufactured by cvs2svn to create branch
'beta_0_7_branch'.
</pre>
If you do this
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/
min revision 386536
max revision 386536
action recurse
end match
</pre>
svn-all-fast-export will fail, you'll get an error sayining that '/foo/bar/path' was not found where '/foo/bar/path' is one of the deleted paths in the cvs2svn commit. This is because some paths were deleted in the same commit where you want to do an 'action recurse'. Therefore, to avoid matching the deleted paths you should do an action recurse on each intermediate directory from '/branches/beta_0_7_branch/' to '/branches/beta_0_7_branch/kdeextragear-3/krecipes/' and you should use a final '$' to make sure that the deleted paths will not be considered, thusly:
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/kdeextragear-3/$
min revision 386536
max revision 386536
action recurse
end match

match /branches/beta_0_7_branch/$
min revision 386536
max revision 386536
action recurse
end match
</pre>

=== Getting Help ===
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

Projects/MovetoGit

2010-10-11T12:46:04Z

Krop: /* Write / update importing rules for svn2git */

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

=The Plan=

KDE is, eventually, moving to Git. We will be using gitolite + Redmine + reviewboard on our own servers.

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE.

After it has been decided in Jun 2010 to use our own servers, Amarok and Konversation moved to git.kde.org/projects.kde.org to test the waters and find problems that would affect KDE.

Once those problems have been solved, all of KDE will be able to switch.

A full schedule for the git infrastructure can be found [http://community.kde.org/Sysadmin/GitInfrastructureLaunch here].

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on git.kde.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The projects.kde.org site will have a list (lists?) of all these repositories using the redmine project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.
Details on the reasoning behind this layout is available [[Projects/MoveToGit/Layout|here]].

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

All KDE developers will in principle be able to use their existing "svn" accounts. Developers using HTTPS ideally would request their HTTPS SVN account to be converted to SSH as that makes it easiest for the KDE sysadmins, but alternatively they can also just provide a public key. At some point the KDE sysadmins are going to send everybody with a HTTPS SVN account an email with a link to a web app to collect their key (see http://www.omat.nl/2010/06/13/sysamin-update-your-email-address/).

From the times when gitorious.org was the preferred hosting solution, a procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].
Many points probably still apply, but have to be updated.

=Blockers=

Tasks that need to get done before we can migrate

==Setup git.kde.org==
{{Progress bar|40}}
'''Owner:''' Eike, Jeff, Sysadmin team

'''Status:''' ''Progressing''

: It [http://lists.kde.org/?l=kde-scm-interest&m=127612957219466&w=2 has been decided] to use gitolite + Redmine + reviewboard on our own servers rather than gitorious.org. Sysadmin team is preparing git.kde.org for this.

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - volunteers needed!

'''Status:''' ''sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]]

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|pumphaus/Arno Rehn
|90
|Includes nearly everything; some history from playground might be missing. Some tags from the CVS days don't have a parent yet - still have to figure out why.
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeedu/marble
|jmho
|100
|Contains: trunk with moves (playground->kdereview->kdeedu), regular kde branches/tags and the following other branches: marble-0.4, gsoc-2009 and geodata-nt. Checking done: gitk --all, verify-git-from-svn
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|tnyblom
|95
|Needs verification.
|-
|SC/kdepim-runtime
|tnyblom
|95
|Needs verification.
|-
|SC/kdepimlibs
|tnyblom
|95
|Needs verification.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 85
| Branches are done, I'm working on tags.
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|kdesupport/akonadi
|cgiboudeaux
|95
|In progress...
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|90}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
*** Internally used tools have been updated and are now being used to access git repos such as dbus.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
*** Most of the technical work regarding migration of kdepim repos has been completed by community member Torgny Nyblom.
* Tool knowledge
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
*** Workshops and use of git-svn have been used to bring developers up to speed on how to use git at some level.

=Nice to have before the migration=

==Push log==
{{Progress bar|100}}
'''Owner:''' sysadmin

'''Status:''' finished

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

-----------

Gitolite includes this functionality inbuilt to itself, although all repositories are logged in the same file - bcooksley

==Script for downloading virtual KDE hierarchies==
{{Progress bar|99}}
'''Owner''':

'''Status:'''

:we already have kdesvn-build, build-tool and mr: three good tools for managing repos.

Most people use kdesrc-build; it will neither eat babies nor kittens. it has options for updating everything or individual modules, can do fetch-only or build-only, etc..
Command-line options for updating the configuration would be a nice addition.

TODO: details on mr and build-tool

note: scripty also has its own list of repos. it's just in a rather weird bash file.

'''Discussion:'''

As far as I can see, kdesvn-build is able to do it, it should be just a matter of providing a configuration. As I'm not using build-tool, I can't say anything about it. --jmho

'''Links'''
*[http://kdesvn-build.kde.org/ kdesvn-build]
*[[Projects/MovetoGit/MassCloneScript]]
*[http://rubyforge.org/projects/build-tool/ build-tool]
*TODO: link to mr

==pre-receive hooks==
{{Progress bar|50}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

This has now been ported to Git - bcooksley

Note however that it doesn't look for a .gitattributes file yet - patches welcome ( see sysadmin/repo-management on git.kde.org )

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|0}}
'''Owner:''' No one (help!)
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|2|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

Is this section still necessary at all? Perhaps some branding has to be done for redmine or cgit, but I don't know. --jmho

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|100}}

'''Owner:''' sysadmin

:Gitolite allows sysadmin to permit certain people on certain repos only to manage both branches and tag without needing force push rights.

'''Discussion'''

==Account setup for Gitolite==
{{Progress bar|0}}

'''Owner:''' ''sysadmin''

:Accounts for existing SVN accounts which use SSH for access have been automatically granted access to Gitolite. Those who are still using HTTPS need to file a sysadmin bug to change their SVN account to SSH and will recieve Git access automatically.

==post-update hooks==
{{Progress bar|90}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

=Completed Tasks=

==Get rid of svn:externals==
{{Progress bar|100}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)

= other notes =

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Projects/MovetoGit

2010-10-08T00:00:16Z

Krop: /* Write / update importing rules for svn2git */

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

=The Plan=

KDE is, eventually, moving to Git. We will be using gitolite + Redmine + reviewboard on our own servers.

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE.

After it has been decided in Jun 2010 to use our own servers, Amarok and Konversation moved to git.kde.org/projects.kde.org to test the waters and find problems that would affect KDE.

Once those problems have been solved, all of KDE will be able to switch.

A full schedule for the git infrastructure can be found [http://community.kde.org/Sysadmin/GitInfrastructureLaunch here].

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on git.kde.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The projects.kde.org site will have a list (lists?) of all these repositories using the redmine project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.
Details on the reasoning behind this layout is available [[Projects/MoveToGit/Layout|here]].

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

All KDE developers will in principle be able to use their existing "svn" accounts. Developers using HTTPS ideally would request their HTTPS SVN account to be converted to SSH as that makes it easiest for the KDE sysadmins, but alternatively they can also just provide a public key. At some point the KDE sysadmins are going to send everybody with a HTTPS SVN account an email with a link to a web app to collect their key (see http://www.omat.nl/2010/06/13/sysamin-update-your-email-address/).

From the times when gitorious.org was the preferred hosting solution, a procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].
Many points probably still apply, but have to be updated.

=Blockers=

Tasks that need to get done before we can migrate

==Setup git.kde.org==
{{Progress bar|40}}
'''Owner:''' Eike, Jeff, Sysadmin team

'''Status:''' ''Progressing''

: It [http://lists.kde.org/?l=kde-scm-interest&m=127612957219466&w=2 has been decided] to use gitolite + Redmine + reviewboard on our own servers rather than gitorious.org. Sysadmin team is preparing git.kde.org for this.

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - volunteers needed!

'''Status:''' ''sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]]

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|pumphaus/Arno Rehn
|90
|Includes nearly everything; some history from playground might be missing. Some tags from the CVS days don't have a parent yet - still have to figure out why.
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeedu/marble
|jmho
|100
|Contains: trunk with moves (playground->kdereview->kdeedu), regular kde branches/tags and the following other branches: marble-0.4, gsoc-2009 and geodata-nt. Checking done: gitk --all, verify-git-from-svn
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|tnyblom
|95
|Needs verification.
|-
|SC/kdepim-runtime
|tnyblom
|95
|Needs verification.
|-
|SC/kdepimlibs
|tnyblom
|95
|Needs verification.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 85
| Branches are done, I'm working on tags.
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|kdesupport/akonadi
|cgiboudeaux
|60
|In progress...
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|90}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
*** Internally used tools have been updated and are now being used to access git repos such as dbus.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
*** Most of the technical work regarding migration of kdepim repos has been completed by community member Torgny Nyblom.
* Tool knowledge
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
*** Workshops and use of git-svn have been used to bring developers up to speed on how to use git at some level.

=Nice to have before the migration=

==Push log==
{{Progress bar|100}}
'''Owner:''' sysadmin

'''Status:''' finished

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

-----------

Gitolite includes this functionality inbuilt to itself, although all repositories are logged in the same file - bcooksley

==Script for downloading virtual KDE hierarchies==
{{Progress bar|99}}
'''Owner''':

'''Status:'''

:we already have kdesvn-build, build-tool and mr: three good tools for managing repos.

Most people use kdesrc-build; it will neither eat babies nor kittens. it has options for updating everything or individual modules, can do fetch-only or build-only, etc..
Command-line options for updating the configuration would be a nice addition.

TODO: details on mr and build-tool

note: scripty also has its own list of repos. it's just in a rather weird bash file.

'''Discussion:'''

As far as I can see, kdesvn-build is able to do it, it should be just a matter of providing a configuration. As I'm not using build-tool, I can't say anything about it. --jmho

'''Links'''
*[http://kdesvn-build.kde.org/ kdesvn-build]
*[[Projects/MovetoGit/MassCloneScript]]
*[http://rubyforge.org/projects/build-tool/ build-tool]
*TODO: link to mr

==pre-receive hooks==
{{Progress bar|50}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

This has now been ported to Git - bcooksley

Note however that it doesn't look for a .gitattributes file yet - patches welcome ( see sysadmin/repo-management on git.kde.org )

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|0}}
'''Owner:''' No one (help!)
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|2|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

Is this section still necessary at all? Perhaps some branding has to be done for redmine or cgit, but I don't know. --jmho

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|100}}

'''Owner:''' sysadmin

:Gitolite allows sysadmin to permit certain people on certain repos only to manage both branches and tag without needing force push rights.

'''Discussion'''

==Account setup for Gitolite==
{{Progress bar|0}}

'''Owner:''' ''sysadmin''

:Accounts for existing SVN accounts which use SSH for access have been automatically granted access to Gitolite. Those who are still using HTTPS need to file a sysadmin bug to change their SVN account to SSH and will recieve Git access automatically.

==post-update hooks==
{{Progress bar|90}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

=Completed Tasks=

==Get rid of svn:externals==
{{Progress bar|100}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)

= other notes =

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Projects/MovetoGit

2010-10-04T08:39:35Z

Krop: /* Write / update importing rules for svn2git */

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

=The Plan=

KDE is, eventually, moving to Git. We will be using gitolite + Redmine + reviewboard on our own servers.

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE.

After it has been decided in Jun 2010 to use our own servers, Amarok and Konversation moved to git.kde.org/projects.kde.org to test the waters and find problems that would affect KDE.

Once those problems have been solved, all of KDE will be able to switch.

A full schedule for the git infrastructure can be found [http://community.kde.org/Sysadmin/GitInfrastructureLaunch here].

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on git.kde.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The projects.kde.org site will have a list (lists?) of all these repositories using the redmine project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.
Details on the reasoning behind this layout is available [[Projects/MoveToGit/Layout|here]].

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

All KDE developers will in principle be able to use their existing "svn" accounts. Developers using HTTPS ideally would request their HTTPS SVN account to be converted to SSH as that makes it easiest for the KDE sysadmins, but alternatively they can also just provide a public key. At some point the KDE sysadmins are going to send everybody with a HTTPS SVN account an email with a link to a web app to collect their key (see http://www.omat.nl/2010/06/13/sysamin-update-your-email-address/).

From the times when gitorious.org was the preferred hosting solution, a procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].
Many points probably still apply, but have to be updated.

=Blockers=

Tasks that need to get done before we can migrate

==Setup git.kde.org==
{{Progress bar|40}}
'''Owner:''' Eike, Jeff, Sysadmin team

'''Status:''' ''Progressing''

: It [http://lists.kde.org/?l=kde-scm-interest&m=127612957219466&w=2 has been decided] to use gitolite + Redmine + reviewboard on our own servers rather than gitorious.org. Sysadmin team is preparing git.kde.org for this.

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - volunteers needed!

'''Status:''' ''sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]]

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|pumphaus/Arno Rehn
|90
|Includes nearly everything; some history from playground might be missing. Some tags from the CVS days don't have a parent yet - still have to figure out why.
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeedu/marble
|jmho
|100
|Contains: trunk with moves (playground->kdereview->kdeedu), regular kde branches/tags and the following other branches: marble-0.4, gsoc-2009 and geodata-nt. Checking done: gitk --all, verify-git-from-svn
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|tnyblom
|95
|Needs verification.
|-
|SC/kdepim-runtime
|tnyblom
|95
|Needs verification.
|-
|SC/kdepimlibs
|tnyblom
|95
|Needs verification.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 85
| Branches are done, I'm working on tags.
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|kdesupport/akonadi
|cgiboudeaux
|20
|In progress...
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|90}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
*** Internally used tools have been updated and are now being used to access git repos such as dbus.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
*** Most of the technical work regarding migration of kdepim repos has been completed by community member Torgny Nyblom.
* Tool knowledge
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
*** Workshops and use of git-svn have been used to bring developers up to speed on how to use git at some level.

=Nice to have before the migration=

==Push log==
{{Progress bar|100}}
'''Owner:''' sysadmin

'''Status:''' finished

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

-----------

Gitolite includes this functionality inbuilt to itself, although all repositories are logged in the same file - bcooksley

==Script for downloading virtual KDE hierarchies==
{{Progress bar|99}}
'''Owner''':

'''Status:'''

:we already have kdesvn-build, build-tool and mr: three good tools for managing repos.

Most people use kdesrc-build; it will neither eat babies nor kittens. it has options for updating everything or individual modules, can do fetch-only or build-only, etc..
Command-line options for updating the configuration would be a nice addition.

TODO: details on mr and build-tool

note: scripty also has its own list of repos. it's just in a rather weird bash file.

'''Discussion:'''

As far as I can see, kdesvn-build is able to do it, it should be just a matter of providing a configuration. As I'm not using build-tool, I can't say anything about it. --jmho

'''Links'''
*[http://kdesvn-build.kde.org/ kdesvn-build]
*[[Projects/MovetoGit/MassCloneScript]]
*[http://rubyforge.org/projects/build-tool/ build-tool]
*TODO: link to mr

==pre-receive hooks==
{{Progress bar|50}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

This has now been ported to Git - bcooksley

Note however that it doesn't look for a .gitattributes file yet - patches welcome ( see sysadmin/repo-management on git.kde.org )

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|0}}
'''Owner:''' No one (help!)
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|2|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

Is this section still necessary at all? Perhaps some branding has to be done for redmine or cgit, but I don't know. --jmho

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|100}}

'''Owner:''' sysadmin

:Gitolite allows sysadmin to permit certain people on certain repos only to manage both branches and tag without needing force push rights.

'''Discussion'''

==Account setup for Gitolite==
{{Progress bar|0}}

'''Owner:''' ''sysadmin''

:Accounts for existing SVN accounts which use SSH for access have been automatically granted access to Gitolite. Those who are still using HTTPS need to file a sysadmin bug to change their SVN account to SSH and will recieve Git access automatically.

==post-update hooks==
{{Progress bar|90}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

=Completed Tasks=

==Get rid of svn:externals==
{{Progress bar|100}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)

= other notes =

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Development/Tutorials/Akonadi/Application

2010-03-04T09:35:46Z

Krop: /* Promoting Views */

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Akonadi/Application}}

{{TutorialBrowser|

series=[[Development/Tutorials#Personal_Information_Management_.28Akonadi.29|Akonadi Tutorial]]|

name=Using your own data type with Akonadi|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=|

reading=[[Development/Tutorials/CMake|CMake]], [[Projects/PIM/Akonadi/Development_Tools|Akonadi Development Tools]]
}}

This tutorial will guide you through the steps of creating an Akonadi application, an end user program which displays and manipulates PIM data provided by Akonadi.

If you are looking for a tutorial on how to provide data for Akonadi see the
[[Development/Tutorials/Akonadi/Resources|Akonadi Resource Tutorial]]

== Prerequisites ==

{{improve|Describe required versions and build setup}}

== Tutorial Example ==

The goal of the tutorial is to create a simple application allowing a user to "detach" attachments from e-mails, i.e. save them to disk and remove them from the message.

To stay concentrated on Akonadi related steps, all general application or GUI related steps will done in a minimal fashion.

== Preparation ==

We can kick-start the application by using '''KAppTemplate''', which can be found as '''KDE template generator''' in the development section of the K-menu, or by running '''kapptemplate''' in a terminal window.

First, we select the '''KDE4 GUI Application''' in the C++ section of the program, give our project a name and continue through the following pages to complete the template creation.

[[Image:TutorialAkonadiDetacherTemplate.png]]

A look at the generated project top level directory shows us the following files:
<code>
CMakeLists.txt
detacher/
doc/
icons/
README
src/
</code>
and the following files in sub directory '''src''':
<code>
CMakeLists.txt
detacher.cpp
detacher.desktop
detacher.h
detacher.kcfg
detacherui.rc
detacherview_base.ui
detacherview.cpp
detacherview.h
main.cpp
Messages.sh
settings.kcfgc
prefs_base.ui
</code>

At this stage it is already possible to compile the application, so we can already check if our development environment is setup correctly by creating the build directory and having CMake either generate Makefiles or a KDevelop project file.

=== Generating Makefiles ===

From within the generated top level directory:
<code>
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=debugfull ..
</code>
and run the build using make as usual.

=== Generating a KDevelop project file ===

From within the generated top level directory:
<code>
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=debugfull -G KDevelop3 ..
</code>
and open the generated project with KDevelop and run the build process from there.

=== Adjusting the main Qt Designer file ===

Open the file '''detacherview_base.ui''' in Qt Designer and remove the example label.
Remove the widget's main layout by clicking on the now empty widget and use the '''Break Layout''' menu entry in the '''Form''' menu.

Now, from left to right, place two '''Tree Views''' and one '''List Widget''' side-by-side.
Select all three boxes by holding SHIFT and clicking each box with the left mouse button.
Use '''Layout Horizontally in a Splitter''' in the '''Form''' menu and then create a main layout by clicking on their parent widget and using '''Layout Vertically''' in the '''Form''' menu.

A preview ('''Form''' -> '''Preview''') should now look like this:
[[Image:TutorialAkonadiDetacherPreview.png]]

Finally, change the object names for the three widgets by right clicking it and choosing '''Change objectName'''. The left widget should be named '''folderView''', the middle one '''messageView''' and the right one '''attachmentList'''.

In order to make it build again, edit the file '''detacherview.cpp''' and remove the code from the '''settingsChanged''' method.
The application should now build again and be able to run.

{{note|A lot of other code of this generated files is not necessary either, feel free to do more cleanup yourself.}}

== Promoting Views ==

The [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html KDE client library for Akonadi] has a couple of convenience classes which make our life as application developers more pleasant.
Two of these classes are specialized view widgets, one for displaying collections and one for displaying items.

In order to use these widgets instead of ones from Qt we need to use a Qt Designer feature called "promoting".
Right click the left widget and choose '''Promote to'''. Then fill the form like shown in the next screenshot.

[[Image:TutorialAkonadiDetacherPromote.png]]

Click add and promote. Repeat the same for the middle widget, this time using '''Akonadi::ItemView''' as the class name and '''akonadi/itemview.h''' for the header file.

This change also requires a change in the '''CMakeLists.txt''' file in the top level directory and in the one from the source directory.

In the file from the top level directory add the following line
<code>
find_package (KdepimLibs REQUIRED)
</code>

and change

<code>
include_directories( ${KDE4_INCLUDES} ${QT_INCLUDES} )
</code>

into

<code>
include_directories( ${KDE4_INCLUDES} ${KDEPIMLIBS_INCLUDE_DIRS} ${QT_INCLUDES} )
</code>

In the file from the source directory the line
<code>
target_link_libraries(detacher ${KDE4_KDEUI_LIBS})
</code>

has to be changed to

<code>
target_link_libraries(detacher ${KDE4_KDEUI_LIBS} ${KDEPIMLIBS_AKONADI_LIBS})
</code>

== Initialization ==

Since the application will depend on Akonadi running, we can ensure this by starting it if it is not.
This is handled by the [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Control.html Akonadi::Control] class.

In '''detacher.h''' we add another slot called '''delayedInit()''' which will perform this initialization.
A slot so we can delay its executing using a single shot timer, a technique called "Delayed Initialization", i.e. letting the application create and show its GUI as fast as possible and do any probably time consuming initialization after that.

<code cppqt>
private slots:
void fileNew();
void optionsPreferences();
void delayedInit();
</code>

In '''detacher.cpp''' we need two new include directives:
<code cppqt>
#include <QtCore/QTimer>

#include <akonadi/control.h>
</code>

and the slot's implementation
<code cppqt>
void Detacher::delayedInit()
{
if ( !Akonadi::Control::start( this ) ) {
qApp->exit( -1 );
return;
}
}
</code>

If the application fails to start Akonadi, it simply quits. A real application should probably tell the user about that though.

Since we want the slot to be executed delayed, add the following line at the end of the class' constructor

<code cppqt>
QTimer::singleShot( 0, this, SLOT( delayedInit() ) );
</code>

Lets add a new public method to the view class. In '''detacherview.h''' add

<code cppqt>
void createModels();
</code>

and for now with an empty body in '''detacherview.cpp''' (we will get to the implementation shortly)
<code cppqt>
void DetacherView::createModels()
{
}
</code>

and call it from '''Detacher::delayedInit()''' after the Akonadi start succeeded

<code cppqt>
void Detacher::delayedInit()
{
if ( !Akonadi::Control::start( this ) ) {
qApp->exit( -1 );
return;
}

m_view->createModels();
}
</code>

== Connecting Views to Akonadi ==

The actual data connection between our views and Akonadi is conveniently handled by specialized models which are also provided by the KDE client library for Akonadi.

Actually, the data type the application will be working on, MIME messages, has an even further specialized model in a type specific sub library.

To properly link this additional library change the source directory's '''CMakeLists.txt''' to this
<code>
target_link_libraries(detacher ${KDE4_KDEUI_LIBS} ${KDEPIMLIBS_AKONADI_LIBS} ${KDEPIMLIBS_AKONADI_KMIME_LIBS})
</code>

In '''detacherview.cpp'' add the following include directives

<code cppqt>
#include <akonadi/collectionfilterproxymodel.h>
#include <akonadi/collectionmodel.h>
#include <akonadi/kmime/messagemodel.h>
</code>

With that we can now properly implement the '''createModels()''' method:

<code cppqt>
void DetacherView::createModels()
{
Akonadi::CollectionModel *collectionModel = new Akonadi::CollectionModel( this );

Akonadi::CollectionFilterProxyModel *filterModel = new Akonadi::CollectionFilterProxyModel( this );
filterModel->setSourceModel( collectionModel );
filterModel->addMimeTypeFilter( QLatin1String( "message/rfc822" ) );

Akonadi::ItemModel *itemModel = new Akonadi::MessageModel( this );

ui_detacherview_base.folderView->setModel( filterModel );
ui_detacherview_base.messageView->setModel( itemModel );

connect( ui_detacherview_base.folderView, SIGNAL( currentChanged( Akonadi::Collection ) ),
itemModel, SLOT( setCollection( Akonadi::Collection ) ) );
}
</code>

The first line creates a [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionModel.html CollectionModel] which will get all "folders" from Akonadi and keep this data updated as long as the application is running.

However, since this includes collections for other data types as well, we need to filter for the data type we are interested in, MIME messages or in terms of MIME type '''message/rfc822'''.
This kind of filtering is conveniently supplied in the form of a proxy model called [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionFilterProxyModel.html CollectionFilterProxyModel].

The next model, [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1MessageModel.html MessageModel] is an [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemModel.html ItemModel] specialized in dealing with our data type, messages.

Setting the models on the respective view almost completes the setup process, the only thing left is to connect the [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionView.html CollectionView] to the MessageModel so it changes its data depending on which folder gets selected.

At this stage the application is already capable of showing all your mail folders and headers of all your e-mails!

== Getting at the Attachments ==

This task can be split into two steps:
* Getting the message from Akonadi
* Getting the attachments from the message

=== Getting the message from Akonadi ===

While we could have instructed the MessageModel to get all data for each of its entries, the proper way is to retrieve it only for the items that get selected.
Moreover we want to do this asynchronously because we don't want to block the application even is a message is really huge.

The KDE client library for Akonadi offers this kind of functionality through a job-based API, in this case [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemFetchJob.html ItemFetchJob].

Using this is quite simple. First we add a new include and a class forward declaration for '''detacherview.h'''

<code cppqt>
#include <akonadi/item.h>
class KJob;
</code>

In the private member section add an [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Item.html Item] member:
<code cppqt>
private:
Ui::detacherview_base ui_detacherview_base;

Akonadi::Item mItem;
</code>

and two new slots in the private slots section:

<code cppqt>
private slots:
void switchColors();
void settingsChanged();

void itemChanged( const Akonadi::Item &item );
void itemFetchDone( KJob *job );
</code>

In the source file '''detacherview.cpp''' two new includes are required
<code cppqt>
#include <akonadi/itemfetchjob.h>
#include <akonadi/itemfetchscope.h>
</code>

for the implementation of the two new slots
<code cppqt>
void DetacherView::itemChanged( const Akonadi::Item &item )
{
// clear attachment list
ui_detacherview_base.attachmentList->clear();

// re-initialize the member we use for referencing the current item
mItem = Akonadi::Item();

// create fetch job and let it get the whole message
Akonadi::ItemFetchJob *fetchJob = new Akonadi::ItemFetchJob( item, this );
fetchJob->fetchScope().fetchFullPayload();

connect( fetchJob, SIGNAL( result( KJob* ) ), SLOT( itemFetchDone( KJob* ) ) );
}

void DetacherView::itemFetchDone( KJob *job )
{
Akonadi::ItemFetchJob *fetchJob = static_cast<Akonadi::ItemFetchJob*>( job );
if ( job->error() ) {
kError() << job->errorString();
return;
}

if ( fetchJob->items().isEmpty() ) {
kWarning() << "Job did not retrieve any items";
return;
}

mItem = fetchJob->items().first();
if ( !mItem.isValid() ) {
kWarning() << "Item not valid";
return;
}
}
</code>

To trigger the item fetching we connect the first new slot to a signal of the MessageView. In '''DetacherView::createModels()''' add another '''connect''' statement:

<code cppqt>
connect( ui_detacherview_base.messageView, SIGNAL( currentChanged( Akonadi::Item ) ),
SLOT( itemChanged( Akonadi::Item ) ) );
</code>

=== Getting the attachments from the message ===

With the item now fully available, we can proceed to check whether the message has any attachments and if it has display them in the right most widget of our GUI.

MIME messages in KDE are handled by the [http://api.kde.org/4.x-api/kdepimlibs-apidocs/kmime/html/index.html kmime library].

For the application this means two more includes and a typedef:

<code cppqt>
#include <kmime/kmime_message.h>
#include <boost/shared_ptr.hpp>
typedef boost::shared_ptr<KMime::Message> MessagePtr;
</code>

[http://api.kde.org/4.x-api/kdepimlibs-apidocs/kmime/html/classKMime_1_1Message.html KMime::Message] is the data type and we need the [http://www.boost.org/doc/libs/1_37_0/libs/smart_ptr/shared_ptr.htm boost::shared_ptr] to provide us with the value based behavior required by the item's payload methods.

Equipped with this new tools we can extend '''DetacherView::itemFetchDone()''' by adding the following code at its end:

<code cppqt>
if ( !mItem.hasPayload<MessagePtr>() ) {
kWarning() << "Item does not have message payload";
return;
}

const MessagePtr message = mItem.payload<MessagePtr>();
const KMime::Content::List attachments = message->attachments();

foreach ( KMime::Content *attachment, attachments ) {
const QString fileName = attachment->contentDisposition()->filename();
if ( fileName.isEmpty() )
continue;

ui_detacherview_base.attachmentList->addItem( fileName );
}
</code>

{{tip|'''Exercise:''' Instead of using a QListView and simple strings, a model working on the single item would make the application a lot cleaner.}}

== Detaching an Attachment ==

This task can again be split into sub tasks:
* Saving the selected attachment into a file
* Removing the selected attachment from the message

=== Saving Attachment into File ===

First we need a new slot in the private slots section of '''detacherview.h'''

<code cppqt>
void detachAttachment();
</code>

To implement the first sub task, saving the selected attachment into a file, the following new includes are needed in '''detacherview.cpp'''
<code cppqt>
#include <kaction.h>
#include <kfiledialog.h>
#include <kstandardaction.h>
</code>

In the class' constructor create and connect an action and make it available as the attachment list widget's context menu:
<code cppqt>
KAction *detachAction = KStandardAction::cut( this, SLOT( detachAttachment() ), this );
detachAction->setText( i18nc( "@action:button remove an attachment from an email",
"Detach..." ) );

ui_detacherview_base.attachmentList->addAction( detachAction );
ui_detacherview_base.attachmentList->setContextMenuPolicy( Qt::ActionsContextMenu );
</code>

{{note|Abusing a KDE standard action like this is not recommendable for real applications. For the scope of this tutorial we overlook this as it provides a quick way to setup an action.}}

In case the [http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/klocalizedstring_8h.html#c3e33b6ced4f356d040e165094a5c3d5 i18nc] function or the text used in it are unexpected, see the [[Development/Tutorials/Localization/i18n_Semantics|Semantic Markup Tutorial]].

Saving the attachment means we need to ask for a saving location, probably including a filename override and get the data from the message.

This can be implemented like this
<code cppqt>
void DetacherView::detachAttachment()
{
const QList<QListWidgetItem*> items = ui_detacherview_base.attachmentList->selectedItems();

if ( items.isEmpty() ) {
kDebug() << "No attachment selected";
return;
}

if ( !mItem.hasPayload<MessagePtr>() ) {
kWarning() << "Item no longer has a payload";
return;
}

// get the selected list item's text. it is the attachment's filename
const QString fileName = items.first()->text();

// ask for a saving location, using the attachment's filename as a
// suggestion
KFileDialog dialog( KUrl(), QString(), this );
dialog.setMode( KFile::Files | KFile::LocalOnly );
dialog.setOperationMode( KFileDialog::Saving );
dialog.setConfirmOverwrite( true );
dialog.setSelection( fileName );

if ( dialog.exec() != QDialog::Accepted ) {
kDebug() << "Saving cancelled. Aborting detaching";
return;
}

const QString saveFileName = dialog.selectedFile();
if ( saveFileName.isEmpty() ) {
kDebug() << "Empty target file name. Aborting detaching";
return;
}

// find the corresponding attachment data structure
const MessagePtr message = mItem.payload<MessagePtr>();
const KMime::Content::List attachments = message->attachments();

KMime::Content *selectedAttachment = 0;
foreach ( KMime::Content *attachment, attachments ) {
if ( fileName == attachment->contentDisposition()->filename() ) {
selectedAttachment = attachment;
break;
}
}

if ( selectedAttachment == 0 ) {
kWarning() << "Selected attachment file name no longer available in message. Aborting detaching";
return;
}

QFile file( saveFileName );
if ( !file.open( QIODevice::WriteOnly ) ) {
kError() << "Cannot open target file for writing. Aborting detaching.";
return;
}

file.write( selectedAttachment->decodedContent() );
file.close();
}
</code>

{{note|Ideally we would have a direct mapping of file name to attachment pointer, e.g. when using a model working on the Akonadi item.}}

=== Removing the Attachment ===

After successfully saving the attachment we can proceed with removing the attachment from the message data and finally update the item in Akonadi to make it a permanent change.

For the last step another job class is needed: [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemModifyJob.html ItemModifyJob]
<code cppqt>
#include <akonadi/itemmodifyjob.h>
</code>

and can be implemented by appending the following code to '''DetacherView::detachAttachment()'''

<code cppqt>
// remove attachment from message
message->removeContent( selectedAttachment, true );

// and from the listwidget
delete items.first();

// prepare Akonadi update
Akonadi::Item item( mItem );
item.setPayload<MessagePtr>( message );

Akonadi::ItemModifyJob *modifyJob = new Akonadi::ItemModifyJob( item, this );
if ( !modifyJob->exec() ) {
kError() << modifyJob->errorString();
return;
}
</code>

[[Category:Tutorial]]
[[Category:C++]]
[[Category:KDE4]]
[[Category:Akonadi]]
[[Category:PIM]]

Development/Tutorials/Akonadi/Application

2010-03-04T09:34:36Z

Krop: /* Connecting Views to Akonadi */

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Akonadi/Application}}

{{TutorialBrowser|

series=[[Development/Tutorials#Personal_Information_Management_.28Akonadi.29|Akonadi Tutorial]]|

name=Using your own data type with Akonadi|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=|

reading=[[Development/Tutorials/CMake|CMake]], [[Projects/PIM/Akonadi/Development_Tools|Akonadi Development Tools]]
}}

This tutorial will guide you through the steps of creating an Akonadi application, an end user program which displays and manipulates PIM data provided by Akonadi.

If you are looking for a tutorial on how to provide data for Akonadi see the
[[Development/Tutorials/Akonadi/Resources|Akonadi Resource Tutorial]]

== Prerequisites ==

{{improve|Describe required versions and build setup}}

== Tutorial Example ==

The goal of the tutorial is to create a simple application allowing a user to "detach" attachments from e-mails, i.e. save them to disk and remove them from the message.

To stay concentrated on Akonadi related steps, all general application or GUI related steps will done in a minimal fashion.

== Preparation ==

We can kick-start the application by using '''KAppTemplate''', which can be found as '''KDE template generator''' in the development section of the K-menu, or by running '''kapptemplate''' in a terminal window.

First, we select the '''KDE4 GUI Application''' in the C++ section of the program, give our project a name and continue through the following pages to complete the template creation.

[[Image:TutorialAkonadiDetacherTemplate.png]]

A look at the generated project top level directory shows us the following files:
<code>
CMakeLists.txt
detacher/
doc/
icons/
README
src/
</code>
and the following files in sub directory '''src''':
<code>
CMakeLists.txt
detacher.cpp
detacher.desktop
detacher.h
detacher.kcfg
detacherui.rc
detacherview_base.ui
detacherview.cpp
detacherview.h
main.cpp
Messages.sh
settings.kcfgc
prefs_base.ui
</code>

At this stage it is already possible to compile the application, so we can already check if our development environment is setup correctly by creating the build directory and having CMake either generate Makefiles or a KDevelop project file.

=== Generating Makefiles ===

From within the generated top level directory:
<code>
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=debugfull ..
</code>
and run the build using make as usual.

=== Generating a KDevelop project file ===

From within the generated top level directory:
<code>
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=debugfull -G KDevelop3 ..
</code>
and open the generated project with KDevelop and run the build process from there.

=== Adjusting the main Qt Designer file ===

Open the file '''detacherview_base.ui''' in Qt Designer and remove the example label.
Remove the widget's main layout by clicking on the now empty widget and use the '''Break Layout''' menu entry in the '''Form''' menu.

Now, from left to right, place two '''Tree Views''' and one '''List Widget''' side-by-side.
Select all three boxes by holding SHIFT and clicking each box with the left mouse button.
Use '''Layout Horizontally in a Splitter''' in the '''Form''' menu and then create a main layout by clicking on their parent widget and using '''Layout Vertically''' in the '''Form''' menu.

A preview ('''Form''' -> '''Preview''') should now look like this:
[[Image:TutorialAkonadiDetacherPreview.png]]

Finally, change the object names for the three widgets by right clicking it and choosing '''Change objectName'''. The left widget should be named '''folderView''', the middle one '''messageView''' and the right one '''attachmentList'''.

In order to make it build again, edit the file '''detacherview.cpp''' and remove the code from the '''settingsChanged''' method.
The application should now build again and be able to run.

{{note|A lot of other code of this generated files is not necessary either, feel free to do more cleanup yourself.}}

== Promoting Views ==

The [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html KDE client library for Akonadi] has a couple of convenience classes which make our life as application developers more pleasant.
Two of these classes are specialized view widgets, one for displaying collections and one for displaying items.

In order to use these widgets instead of ones from Qt we need to use a Qt Designer feature called "promoting".
Right click the left widget and choose '''Promote to'''. Then fill the form like shown in the next screenshot.

[[Image:TutorialAkonadiDetacherPromote.png]]

Click add and promote. Repeat the same for the middle widget, this time using '''Akonadi::ItemView''' as the class name and '''akonadi/itemview.h''' for the header file.

This change also requires a change in the '''CMakeLists.txt''' file in the top level directory and in the one from the source directory.

In the file from the top level directory add the following line
<code>
find_package (KdepimLibs REQUIRED)
</code>

and change

<code>
include_directories( ${KDE4_INCLUDES} ${QT_INCLUDES} )
</code>

into

<code>
include_directories( ${KDE4_INCLUDES} ${KDEPIMLIBS_INCLUDE_DIR} ${QT_INCLUDES} )
</code>

In the file from the source directory the line
<code>
target_link_libraries(detacher ${KDE4_KDEUI_LIBS})
</code>

has to be changed to

<code>
target_link_libraries(detacher ${KDE4_KDEUI_LIBS} ${KDE4_AKONADI_LIBS})
</code>

== Initialization ==

Since the application will depend on Akonadi running, we can ensure this by starting it if it is not.
This is handled by the [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Control.html Akonadi::Control] class.

In '''detacher.h''' we add another slot called '''delayedInit()''' which will perform this initialization.
A slot so we can delay its executing using a single shot timer, a technique called "Delayed Initialization", i.e. letting the application create and show its GUI as fast as possible and do any probably time consuming initialization after that.

<code cppqt>
private slots:
void fileNew();
void optionsPreferences();
void delayedInit();
</code>

In '''detacher.cpp''' we need two new include directives:
<code cppqt>
#include <QtCore/QTimer>

#include <akonadi/control.h>
</code>

and the slot's implementation
<code cppqt>
void Detacher::delayedInit()
{
if ( !Akonadi::Control::start( this ) ) {
qApp->exit( -1 );
return;
}
}
</code>

If the application fails to start Akonadi, it simply quits. A real application should probably tell the user about that though.

Since we want the slot to be executed delayed, add the following line at the end of the class' constructor

<code cppqt>
QTimer::singleShot( 0, this, SLOT( delayedInit() ) );
</code>

Lets add a new public method to the view class. In '''detacherview.h''' add

<code cppqt>
void createModels();
</code>

and for now with an empty body in '''detacherview.cpp''' (we will get to the implementation shortly)
<code cppqt>
void DetacherView::createModels()
{
}
</code>

and call it from '''Detacher::delayedInit()''' after the Akonadi start succeeded

<code cppqt>
void Detacher::delayedInit()
{
if ( !Akonadi::Control::start( this ) ) {
qApp->exit( -1 );
return;
}

m_view->createModels();
}
</code>

== Connecting Views to Akonadi ==

The actual data connection between our views and Akonadi is conveniently handled by specialized models which are also provided by the KDE client library for Akonadi.

Actually, the data type the application will be working on, MIME messages, has an even further specialized model in a type specific sub library.

To properly link this additional library change the source directory's '''CMakeLists.txt''' to this
<code>
target_link_libraries(detacher ${KDE4_KDEUI_LIBS} ${KDEPIMLIBS_AKONADI_LIBS} ${KDEPIMLIBS_AKONADI_KMIME_LIBS})
</code>

In '''detacherview.cpp'' add the following include directives

<code cppqt>
#include <akonadi/collectionfilterproxymodel.h>
#include <akonadi/collectionmodel.h>
#include <akonadi/kmime/messagemodel.h>
</code>

With that we can now properly implement the '''createModels()''' method:

<code cppqt>
void DetacherView::createModels()
{
Akonadi::CollectionModel *collectionModel = new Akonadi::CollectionModel( this );

Akonadi::CollectionFilterProxyModel *filterModel = new Akonadi::CollectionFilterProxyModel( this );
filterModel->setSourceModel( collectionModel );
filterModel->addMimeTypeFilter( QLatin1String( "message/rfc822" ) );

Akonadi::ItemModel *itemModel = new Akonadi::MessageModel( this );

ui_detacherview_base.folderView->setModel( filterModel );
ui_detacherview_base.messageView->setModel( itemModel );

connect( ui_detacherview_base.folderView, SIGNAL( currentChanged( Akonadi::Collection ) ),
itemModel, SLOT( setCollection( Akonadi::Collection ) ) );
}
</code>

The first line creates a [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionModel.html CollectionModel] which will get all "folders" from Akonadi and keep this data updated as long as the application is running.

However, since this includes collections for other data types as well, we need to filter for the data type we are interested in, MIME messages or in terms of MIME type '''message/rfc822'''.
This kind of filtering is conveniently supplied in the form of a proxy model called [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionFilterProxyModel.html CollectionFilterProxyModel].

The next model, [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1MessageModel.html MessageModel] is an [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemModel.html ItemModel] specialized in dealing with our data type, messages.

Setting the models on the respective view almost completes the setup process, the only thing left is to connect the [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionView.html CollectionView] to the MessageModel so it changes its data depending on which folder gets selected.

At this stage the application is already capable of showing all your mail folders and headers of all your e-mails!

== Getting at the Attachments ==

This task can be split into two steps:
* Getting the message from Akonadi
* Getting the attachments from the message

=== Getting the message from Akonadi ===

While we could have instructed the MessageModel to get all data for each of its entries, the proper way is to retrieve it only for the items that get selected.
Moreover we want to do this asynchronously because we don't want to block the application even is a message is really huge.

The KDE client library for Akonadi offers this kind of functionality through a job-based API, in this case [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemFetchJob.html ItemFetchJob].

Using this is quite simple. First we add a new include and a class forward declaration for '''detacherview.h'''

<code cppqt>
#include <akonadi/item.h>
class KJob;
</code>

In the private member section add an [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Item.html Item] member:
<code cppqt>
private:
Ui::detacherview_base ui_detacherview_base;

Akonadi::Item mItem;
</code>

and two new slots in the private slots section:

<code cppqt>
private slots:
void switchColors();
void settingsChanged();

void itemChanged( const Akonadi::Item &item );
void itemFetchDone( KJob *job );
</code>

In the source file '''detacherview.cpp''' two new includes are required
<code cppqt>
#include <akonadi/itemfetchjob.h>
#include <akonadi/itemfetchscope.h>
</code>

for the implementation of the two new slots
<code cppqt>
void DetacherView::itemChanged( const Akonadi::Item &item )
{
// clear attachment list
ui_detacherview_base.attachmentList->clear();

// re-initialize the member we use for referencing the current item
mItem = Akonadi::Item();

// create fetch job and let it get the whole message
Akonadi::ItemFetchJob *fetchJob = new Akonadi::ItemFetchJob( item, this );
fetchJob->fetchScope().fetchFullPayload();

connect( fetchJob, SIGNAL( result( KJob* ) ), SLOT( itemFetchDone( KJob* ) ) );
}

void DetacherView::itemFetchDone( KJob *job )
{
Akonadi::ItemFetchJob *fetchJob = static_cast<Akonadi::ItemFetchJob*>( job );
if ( job->error() ) {
kError() << job->errorString();
return;
}

if ( fetchJob->items().isEmpty() ) {
kWarning() << "Job did not retrieve any items";
return;
}

mItem = fetchJob->items().first();
if ( !mItem.isValid() ) {
kWarning() << "Item not valid";
return;
}
}
</code>

To trigger the item fetching we connect the first new slot to a signal of the MessageView. In '''DetacherView::createModels()''' add another '''connect''' statement:

<code cppqt>
connect( ui_detacherview_base.messageView, SIGNAL( currentChanged( Akonadi::Item ) ),
SLOT( itemChanged( Akonadi::Item ) ) );
</code>

=== Getting the attachments from the message ===

With the item now fully available, we can proceed to check whether the message has any attachments and if it has display them in the right most widget of our GUI.

MIME messages in KDE are handled by the [http://api.kde.org/4.x-api/kdepimlibs-apidocs/kmime/html/index.html kmime library].

For the application this means two more includes and a typedef:

<code cppqt>
#include <kmime/kmime_message.h>
#include <boost/shared_ptr.hpp>
typedef boost::shared_ptr<KMime::Message> MessagePtr;
</code>

[http://api.kde.org/4.x-api/kdepimlibs-apidocs/kmime/html/classKMime_1_1Message.html KMime::Message] is the data type and we need the [http://www.boost.org/doc/libs/1_37_0/libs/smart_ptr/shared_ptr.htm boost::shared_ptr] to provide us with the value based behavior required by the item's payload methods.

Equipped with this new tools we can extend '''DetacherView::itemFetchDone()''' by adding the following code at its end:

<code cppqt>
if ( !mItem.hasPayload<MessagePtr>() ) {
kWarning() << "Item does not have message payload";
return;
}

const MessagePtr message = mItem.payload<MessagePtr>();
const KMime::Content::List attachments = message->attachments();

foreach ( KMime::Content *attachment, attachments ) {
const QString fileName = attachment->contentDisposition()->filename();
if ( fileName.isEmpty() )
continue;

ui_detacherview_base.attachmentList->addItem( fileName );
}
</code>

{{tip|'''Exercise:''' Instead of using a QListView and simple strings, a model working on the single item would make the application a lot cleaner.}}

== Detaching an Attachment ==

This task can again be split into sub tasks:
* Saving the selected attachment into a file
* Removing the selected attachment from the message

=== Saving Attachment into File ===

First we need a new slot in the private slots section of '''detacherview.h'''

<code cppqt>
void detachAttachment();
</code>

To implement the first sub task, saving the selected attachment into a file, the following new includes are needed in '''detacherview.cpp'''
<code cppqt>
#include <kaction.h>
#include <kfiledialog.h>
#include <kstandardaction.h>
</code>

In the class' constructor create and connect an action and make it available as the attachment list widget's context menu:
<code cppqt>
KAction *detachAction = KStandardAction::cut( this, SLOT( detachAttachment() ), this );
detachAction->setText( i18nc( "@action:button remove an attachment from an email",
"Detach..." ) );

ui_detacherview_base.attachmentList->addAction( detachAction );
ui_detacherview_base.attachmentList->setContextMenuPolicy( Qt::ActionsContextMenu );
</code>

{{note|Abusing a KDE standard action like this is not recommendable for real applications. For the scope of this tutorial we overlook this as it provides a quick way to setup an action.}}

In case the [http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/klocalizedstring_8h.html#c3e33b6ced4f356d040e165094a5c3d5 i18nc] function or the text used in it are unexpected, see the [[Development/Tutorials/Localization/i18n_Semantics|Semantic Markup Tutorial]].

Saving the attachment means we need to ask for a saving location, probably including a filename override and get the data from the message.

This can be implemented like this
<code cppqt>
void DetacherView::detachAttachment()
{
const QList<QListWidgetItem*> items = ui_detacherview_base.attachmentList->selectedItems();

if ( items.isEmpty() ) {
kDebug() << "No attachment selected";
return;
}

if ( !mItem.hasPayload<MessagePtr>() ) {
kWarning() << "Item no longer has a payload";
return;
}

// get the selected list item's text. it is the attachment's filename
const QString fileName = items.first()->text();

// ask for a saving location, using the attachment's filename as a
// suggestion
KFileDialog dialog( KUrl(), QString(), this );
dialog.setMode( KFile::Files | KFile::LocalOnly );
dialog.setOperationMode( KFileDialog::Saving );
dialog.setConfirmOverwrite( true );
dialog.setSelection( fileName );

if ( dialog.exec() != QDialog::Accepted ) {
kDebug() << "Saving cancelled. Aborting detaching";
return;
}

const QString saveFileName = dialog.selectedFile();
if ( saveFileName.isEmpty() ) {
kDebug() << "Empty target file name. Aborting detaching";
return;
}

// find the corresponding attachment data structure
const MessagePtr message = mItem.payload<MessagePtr>();
const KMime::Content::List attachments = message->attachments();

KMime::Content *selectedAttachment = 0;
foreach ( KMime::Content *attachment, attachments ) {
if ( fileName == attachment->contentDisposition()->filename() ) {
selectedAttachment = attachment;
break;
}
}

if ( selectedAttachment == 0 ) {
kWarning() << "Selected attachment file name no longer available in message. Aborting detaching";
return;
}

QFile file( saveFileName );
if ( !file.open( QIODevice::WriteOnly ) ) {
kError() << "Cannot open target file for writing. Aborting detaching.";
return;
}

file.write( selectedAttachment->decodedContent() );
file.close();
}
</code>

{{note|Ideally we would have a direct mapping of file name to attachment pointer, e.g. when using a model working on the Akonadi item.}}

=== Removing the Attachment ===

After successfully saving the attachment we can proceed with removing the attachment from the message data and finally update the item in Akonadi to make it a permanent change.

For the last step another job class is needed: [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemModifyJob.html ItemModifyJob]
<code cppqt>
#include <akonadi/itemmodifyjob.h>
</code>

and can be implemented by appending the following code to '''DetacherView::detachAttachment()'''

<code cppqt>
// remove attachment from message
message->removeContent( selectedAttachment, true );

// and from the listwidget
delete items.first();

// prepare Akonadi update
Akonadi::Item item( mItem );
item.setPayload<MessagePtr>( message );

Akonadi::ItemModifyJob *modifyJob = new Akonadi::ItemModifyJob( item, this );
if ( !modifyJob->exec() ) {
kError() << modifyJob->errorString();
return;
}
</code>

[[Category:Tutorial]]
[[Category:C++]]
[[Category:KDE4]]
[[Category:Akonadi]]
[[Category:PIM]]

Contribute/Bugsquad/BugDays/KDEPimDay2

2008-11-09T15:20:46Z

Krop: /* kmail */

==Introduction==

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

'''The goal of this bug-day is to check if bugs filed against older version of KDE PIM still apply to the new latest version. If a bug is still reproducible our aim will be to find simple step-by-step solutions and/or testcases so it gets easier for the KDE PIM developers to find and fix those bugs.'''

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a recent version of KDE, either svn trunk or the latest release from KDE 4.1.3. Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started/Build/KDE4 found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KDE PIM you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KDE PIM you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. If not do one of the following:
### If the bug is reproducible, set the version field to the version of KDE PIM you are triaging with.
### If the bug is not reproducible, set the version field to the version the bug was reported with.
## Check if the bug's product and component are appropriate. Don't forget to look at the application specific hints. If the bug's product/component needs to be changed but you lack permissions, put it in the "Needs product/component change" section.
## If you lack bugzilla permissions to change the version field, additionally file the bug in the "needs version field change" section. Never change a version if it has already been set to a number!
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create documents that show the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a major feature doesn't work, that is important. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==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 beta2 if you're using that):

{|
|-
!IRC Nickname !! KDE PIM version used for testing
|-
|[[User:Lemma|Lemma]]||svn trunk r881868 ||
|-
|[[User:jtamate|jtamate]]|| opensuse 4.1.72 ||
|-
|[[User:JLP|JLP]]||svn trunk r881890||
|-
|[[User:opensourcecat|opensourcecat]]||svn trunk r881888||
|-
|[[User:Dtritscher|dtritscher]]||Kubuntu 4.1.3||
|-
|[[User:Blauzahl|Blauzahl]]||svn trunk kdepim 881804||
|-
|[[User:Krop|Krop]]||svn trunk kdepim 881888||
|-
|[[User:Gkiagia|gkiagia]]||svn trunk r881933||
|-
|[[User:katastrophe|katastrophe]]||svn trunk 881393||
|-
|[[User:fvilas|fvilas]]||Slackware 4.1.2||
|}

==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 month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

The bugs presented on this page are only a selection of the bugs that need triaging. If you run out of bugs to do, please tell on IRC and we'll provide new batches.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===kmail===

Information mostly for people organizing:
* The template query for kmail is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].

Additional information:
* KMail just added the new folder- and messagelist developed in one of this year's SoC project. If you find any bugs related to those lists, please let someone with a recent build of trunk who has the new views triage the bug.
::A list of known bugs of the SoC project can be found [[Projects/PIM/KMail_SoC_regressions|here]]. However, new bugs should not be reported there, they should go to bugzilla.
::Bug reports about the new message list or the new folder tree should be changed to the "new message list" or "new folder tree" component. When changing the component, please also reassign to the owner of the component, which is not kdepim-bugs but the SoC student.
::You need the newest version of qt-copy, otherwise you'll get random crashes, see [http://bugs.kde.org/show_bug.cgi?id=174065 bug 174065].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=91776&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=92308 Query]
|-
| 2 || 10 || [[User:Lemma|Lemma]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=37306&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=57193 Query]
|-
| 3 || 10 || [[User:fvilas|fvilas]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=57340&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=72311 Query]
|-
| 4 || 10 || [[User:JLP|JLP]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=73214&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=77059 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=77087&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=78750 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=79167&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=80177 Query]
|-
| 7 || 10 ||[[User:opensourcecat|opensourcecat]]||done|| [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=80308&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=83415 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=83486&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=84687 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=84946&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=86157 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=86521&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=87932 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=88038&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=88950 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=89045&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=89879 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=90091&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=90962 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=91047&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=91706 Query]
|}

===korganizer===

Information mostly for people organizing:
* The template query for korganizer is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || katastrophe || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=32042&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=77072 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=78802&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=86096 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=89418&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=93810 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=94101&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=98813 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=98998&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=102873 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=103095&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=106946 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=107003&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=108921 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=109158&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=110558 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=110648&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=112210 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=112234&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=114187 Query]
|}

===akregator===

Information mostly for people organizing:
* The template query for akregator is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=%255BBug+creation%255D&type0-0-0=noop&value0-0-0= this one].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:jtamate|jtamate]] || only one done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=96796&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=111548 Query]
|-
| 2 || 10 || [[User:Dtritscher|dtritscher]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=111907&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=118485 Query]
|-
| 3 || 10 || [[User:Dtritscher|dtritscher]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=118907&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=123585 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=124052&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=129112 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=130697&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=136367 Query]
|}

===kaddressbook===

Information mostly for people organizing:
* The template query for kaddressbook is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=68324&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=126850 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=127107&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=133381 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=133444&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=138679 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=138908&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=145272 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=145324&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=147917 Query]
|}

===knode===

Information mostly for people organizing:
* The template query for knode is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=33035&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=62537 Query]
|-
| 2 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=63888&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=73813 Query]
|-
| 3 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=73851&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=78190 Query]
|-
| 4 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=79057&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=88287 Query]
|-
| 5 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=89489&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=95917 Query]
|}

===kontact===

Information mostly for people organizing:
* The template query for kontact is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=92813&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=114014 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=114651&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=129258 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=129469&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=137106 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=137327&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=139740 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=139974&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=142657 Query]
|}

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs needing productcomponent changed}}

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

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs with step-by-step instructions}}

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

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs that should be WISHES}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Non english locales}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs awaiting feedback}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/High profile}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs not related to KDEPim}}

Contribute/Bugsquad/BugDays/KDEPimDay2

2008-11-09T11:21:23Z

Krop: /* kmail */

==Introduction==

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

'''The goal of this bug-day is to check if bugs filed against older version of KDE PIM still apply to the new latest version. If a bug is still reproducible our aim will be to find simple step-by-step solutions and/or testcases so it gets easier for the KDE PIM developers to find and fix those bugs.'''

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a recent version of KDE, either svn trunk or the latest release from KDE 4.1.3. Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started/Build/KDE4 found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KDE PIM you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KDE PIM you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. If not do one of the following:
### If the bug is reproducible, set the version field to the version of KDE PIM you are triaging with.
### If the bug is not reproducible, set the version field to the version the bug was reported with.
## Check if the bug's product and component are appropriate. Don't forget to look at the application specific hints. If the bug's product/component needs to be changed but you lack permissions, put it in the "Needs product/component change" section.
## If you lack bugzilla permissions to change the version field, additionally file the bug in the "needs version field change" section. Never change a version if it has already been set to a number!
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create documents that show the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a major feature doesn't work, that is important. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==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 beta2 if you're using that):

{|
|-
!IRC Nickname !! KDE PIM version used for testing
|-
|[[User:Lemma|Lemma]]||svn trunk r881868 ||
|-
|[[User:jtamate|jtamate]]|| opensuse 4.1.72 ||
|-
|[[User:JLP|JLP]]||svn trunk r881890||
|-
|[[User:opensourcecat|opensourcecat]]||svn trunk r881888||
|-
|[[User:Dtritscher|dtritscher]]||Kubuntu 4.1.3||
|-
|[[User:Blauzahl|Blauzahl]]||svn trunk kdepim 881804||
|-
|[[User:Krop|Krop]]||svn trunk kdepim 881888||
|}

==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 month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

The bugs presented on this page are only a selection of the bugs that need triaging. If you run out of bugs to do, please tell on IRC and we'll provide new batches.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===kmail===

Information mostly for people organizing:
* The template query for kmail is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].

Additional information:
* KMail just added the new folder- and messagelist developed in one of this year's SoC project. If you find any bugs related to those lists, please let someone with a recent build of trunk who has the new views triage the bug.
::A list of known bugs of the SoC project can be found [[Projects/PIM/KMail_SoC_regressions|here]]. However, new bugs should not be reported there, they should go to bugzilla.
::Bug reports about the new message list or the new folder tree should be changed to the "new message list" or "new folder tree" component. When changing the component, please also reassign to the owner of the component, which is not kdepim-bugs but the SoC student.
::You need the newest version of qt-copy, otherwise you'll get random crashes, see [http://bugs.kde.org/show_bug.cgi?id=174065 bug 174065].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=91776&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=92308 Query]
|-
| 2 || 10 || [[User:Lemma|Lemma]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=37306&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=57193 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=57340&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=72311 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=73214&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=77059 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=77087&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=78750 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=79167&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=80177 Query]
|-
| 7 || 10 ||[[User:opensourcecat|opensourcecat]]||starting|| [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=80308&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=83415 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=83486&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=84687 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=84946&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=86157 Query]
|-
| 10 || 10 || [[User:Krop|krop]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=86521&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=87932 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=88038&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=88950 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=89045&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=89879 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=90091&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=90962 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=91047&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=91706 Query]
|}

===korganizer===

Information mostly for people organizing:
* The template query for korganizer is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=32042&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=77072 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=78802&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=86096 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=89418&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=93810 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=94101&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=98813 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=98998&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=102873 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=103095&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=106946 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=107003&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=108921 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=109158&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=110558 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=110648&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=112210 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=112234&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=114187 Query]
|}

===akregator===

Information mostly for people organizing:
* The template query for akregator is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=%255BBug+creation%255D&type0-0-0=noop&value0-0-0= this one].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:jtamate|jtamate]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=96796&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=111548 Query]
|-
| 2 || 10 || [[User:Dtritscher|dtritscher]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=111907&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=118485 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=118907&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=123585 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=124052&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=129112 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=130697&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=136367 Query]
|}

===kaddressbook===

Information mostly for people organizing:
* The template query for kaddressbook is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=68324&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=126850 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=127107&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=133381 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=133444&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=138679 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=138908&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=145272 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=145324&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=147917 Query]
|}

===knode===

Information mostly for people organizing:
* The template query for knode is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=33035&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=62537 Query]
|-
| 2 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=63888&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=73813 Query]
|-
| 3 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=73851&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=78190 Query]
|-
| 4 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=79057&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=88287 Query]
|-
| 5 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=89489&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=95917 Query]
|}

===kontact===

Information mostly for people organizing:
* The template query for kontact is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=92813&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=114014 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=114651&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=129258 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=129469&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=137106 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=137327&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=139740 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=139974&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=142657 Query]
|}

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs needing productcomponent changed}}

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

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs with step-by-step instructions}}

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

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs that should be WISHES}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Non english locales}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs awaiting feedback}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/High profile}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs not related to KDEPim}}

Contribute/Bugsquad/BugDays/KDEPimDay2

2008-11-09T11:15:03Z

Krop: /* Sign-in */

==Introduction==

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

'''The goal of this bug-day is to check if bugs filed against older version of KDE PIM still apply to the new latest version. If a bug is still reproducible our aim will be to find simple step-by-step solutions and/or testcases so it gets easier for the KDE PIM developers to find and fix those bugs.'''

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a recent version of KDE, either svn trunk or the latest release from KDE 4.1.3. Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started/Build/KDE4 found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KDE PIM you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KDE PIM you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. If not do one of the following:
### If the bug is reproducible, set the version field to the version of KDE PIM you are triaging with.
### If the bug is not reproducible, set the version field to the version the bug was reported with.
## Check if the bug's product and component are appropriate. Don't forget to look at the application specific hints. If the bug's product/component needs to be changed but you lack permissions, put it in the "Needs product/component change" section.
## If you lack bugzilla permissions to change the version field, additionally file the bug in the "needs version field change" section. Never change a version if it has already been set to a number!
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create documents that show the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a major feature doesn't work, that is important. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==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 beta2 if you're using that):

{|
|-
!IRC Nickname !! KDE PIM version used for testing
|-
|[[User:Lemma|Lemma]]||svn trunk r881868 ||
|-
|[[User:jtamate|jtamate]]|| opensuse 4.1.72 ||
|-
|[[User:JLP|JLP]]||svn trunk r881890||
|-
|[[User:opensourcecat|opensourcecat]]||svn trunk r881888||
|-
|[[User:Dtritscher|dtritscher]]||Kubuntu 4.1.3||
|-
|[[User:Blauzahl|Blauzahl]]||svn trunk kdepim 881804||
|-
|[[User:Krop|Krop]]||svn trunk kdepim 881888||
|}

==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 month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

The bugs presented on this page are only a selection of the bugs that need triaging. If you run out of bugs to do, please tell on IRC and we'll provide new batches.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===kmail===

Information mostly for people organizing:
* The template query for kmail is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].

Additional information:
* KMail just added the new folder- and messagelist developed in one of this year's SoC project. If you find any bugs related to those lists, please let someone with a recent build of trunk who has the new views triage the bug.
::A list of known bugs of the SoC project can be found [[Projects/PIM/KMail_SoC_regressions|here]]. However, new bugs should not be reported there, they should go to bugzilla.
::Bug reports about the new message list or the new folder tree should be changed to the "new message list" or "new folder tree" component. When changing the component, please also reassign to the owner of the component, which is not kdepim-bugs but the SoC student.
::You need the newest version of qt-copy, otherwise you'll get random crashes, see [http://bugs.kde.org/show_bug.cgi?id=174065 bug 174065].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=91776&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=92308 Query]
|-
| 2 || 10 || [[User:Lemma|Lemma]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=37306&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=57193 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=57340&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=72311 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=73214&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=77059 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=77087&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=78750 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=79167&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=80177 Query]
|-
| 7 || 10 ||[[User:opensourcecat|opensourcecat]]||starting|| [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=80308&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=83415 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=83486&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=84687 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=84946&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=86157 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=86521&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=87932 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=88038&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=88950 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=89045&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=89879 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=90091&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=90962 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=91047&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=91706 Query]
|}

===korganizer===

Information mostly for people organizing:
* The template query for korganizer is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=32042&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=77072 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=78802&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=86096 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=89418&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=93810 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=94101&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=98813 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=98998&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=102873 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=103095&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=106946 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=107003&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=108921 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=109158&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=110558 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=110648&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=112210 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=korganizer&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=112234&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=114187 Query]
|}

===akregator===

Information mostly for people organizing:
* The template query for akregator is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=%255BBug+creation%255D&type0-0-0=noop&value0-0-0= this one].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:jtamate|jtamate]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=96796&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=111548 Query]
|-
| 2 || 10 || [[User:Dtritscher|dtritscher]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=111907&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=118485 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=118907&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=123585 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=124052&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=129112 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=130697&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=136367 Query]
|}

===kaddressbook===

Information mostly for people organizing:
* The template query for kaddressbook is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=68324&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=126850 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=127107&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=133381 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=133444&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=138679 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=138908&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=145272 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kaddressbook&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=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=145324&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=147917 Query]
|}

===knode===

Information mostly for people organizing:
* The template query for knode is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=33035&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=62537 Query]
|-
| 2 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=63888&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=73813 Query]
|-
| 3 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=73851&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=78190 Query]
|-
| 4 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=79057&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=88287 Query]
|-
| 5 || 10 || || || [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=knode&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=89489&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=95917 Query]
|}

===kontact===

Information mostly for people organizing:
* The template query for kontact is [ this one].
* Check for [ untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=92813&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=114014 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=114651&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=129258 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=129469&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=137106 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=137327&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=139740 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kontact&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=139974&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=142657 Query]
|}

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs needing productcomponent changed}}

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

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs with step-by-step instructions}}

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

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs that should be WISHES}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Non english locales}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs awaiting feedback}}

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

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/High profile}}

{{:Contribute/Bugsquad/BugDays/KDEPimDay2/Bugs not related to KDEPim}}

Projects/PIM/Akonadi

2008-08-19T13:15:19Z

Krop: removing "on ubuntu" since both the hardy backports and the intrepid packages have an apparmor profile for akonadi

== Akonadi TODO ==
The following list contains the things which need to be done for Akonadi.

Note: The person noted in the "Contact" column is not necessarily the one implementing that feature, but the one who can tell you what to do and how to help, i.e. you can also contribute to those tasks ;-)

=== Core ===

==== 4.1 ====

Urgent tasks that need to be finished for the KDE 4.1 release ('''May 19th'''):

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureDone|Item streaming in ItemSync/ResourceBase|As discussed in Osnabrueck|Tom/Volker}}
{{FeatureDone|Payload serialization format versioning|see below
tokoe@kde.org|Tobias}}
{{FeatureDone|API for additional item parts|As discussed in Osnabruck|Volker/Tobias}}
{{FeatureDone|Infrastructure for showing additional dialogs from agents/resources|As discussed in Osnabrueck|Tom}}
{{FeatureDone|Allow to limit ItemFetchJob to current cache content|Prevents search index feeder agents from downloading all remote data|vkrause@kde.org|Volker}}
{{FeatureDone|Fix API for item/collection modifications|See Osnabrueck meeting notes for details|vkrause@kde.org|Volker}}
{{FeatureDone|Plugin Versioning|For serializer plugins, also check using Qt plugin stuff instead of the libkdepim plugin framework|tokoe@kde.org|Tobias}}
{{FeatureDone|Tray app|small app to control the server and have a something that can report errors|tomalbers@kde.nl|Toma}}
{{FeatureDone|Backup support|Dump & Restore database contents, also useful when upgrading to a newer database version|tomalbers@kde.nl}}
|}

==== Scheduled for 4.2 ====

That's the stuff we want to have in 4.2, very roughly ordered by priority.

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureTodo|Better error detection|Sane error message when the server is not running or if there is some other problem communicating with it. This is a must-have for 4.2 when planning to migrate the resources.|}}
{{FeatureInProgress|KResource migration tool|For KABC and KCal resources, setting up Akonadi <-> KResource bridges where needed|Volker}}
{{FeatureInProgress|KResource bridges|Subresource support still has to be done|Kevin}}
{{FeatureTodo|Complete iCal resource|error handling, robustness, legacy formats, etc.|}}
{{FeatureTodo|Complete vCard resource|same as iCal|}}
{{FeatureInProgress|Item size|Needed by Mailody|thomas.mcguire@gmx.net}}
{{FeatureInProgress|Finish collection model/view|see below|thomas.mcguire@gmx.net}}
{{FeatureInProgress|Collection statistics for sub-trees|Provide a CollectionStatus object covering the full sub-tree in the model, allowing accumulated unread counts etc.|Thomas}}
{{FeatureTodo|Batch jobs for modifying/deleting collections/items|it would be great to have jobs which perform operations on several entities in one sitting (a use-case: mark all as read).|}}
{{FeatureTodo|Batch job to retrieve a set of items from Akonadi|Those items don't belong to the same collection, rather they are located in different collections|}}
{{FeatureTodo|CollectionFetchJob/ItemFetchJob should be able to retrieve entities by remote id/mimetype|
This is problematic with change notifications, as they have to know about the filtering with the \Seen flag as well.
This type of filtering would be possible with full Nepomuk interface though. We don't want yet another query language here. The plan is to fix the nepomuk agent and use that as semi-public interface for now.|}}
{{FeatureTodo|ResourceBase::collectionsRetrievalDone is missing|I'm working around by calling collectionsRetrievedIncremental() with empty collection lists|}}
{{FeatureTodo|LINK command|Adding items to virtual collections, required for external search, |}}
|}

==== Post 4.2 ====

This stuff is currently not considered for 4.2 due to lack of resources. Of course it will be added nevertheless if someone implements it. The list is completely unsorted.

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureTodo|Error reporting|Akonadi::Job basically has only one error code: Unknown|Tobias}}
{{FeatureInProgress|Akonadi Artwork|Icon for the tray app|tomalbers@kde.nl|Toma}}
{{FeatureTodo|Nepomuk integration|Generic Item tag/rate/comment, etc.|Tom}}
{{FeatureTodo|Account creation wizard|as discussed in Berlin, see below|}}
{{FeatureTodo|Sync collection tree after creating setting up a resource|see AgentInstanceCreateJob|}}
{{FeatureTodo|Support standard commands for QUndo framework||}}
{{FeatureTodo|Conflict detection in resources|See Osnabrueck meeting notes for details|}}
{{FeatureInProgress|Action framework|see below|vkrause@kde.org|Volker}}
{{FeatureTodo|Solid integration|Switch online/offline state in ResourceBase automatically|}}
{{FeatureTodo|Make unittests work without destroying the production database||}}
{{FeatureInProgress|Fix API docs|The libakonadi move as well as the huge API changes following it broke lots of the docs technical and content-wise, see below|Tobias}}
{{FeatureTodo|Filesystem Backend|Store content data in files instead of the database, transfer filehandles instead of data to the client|}}
{{FeatureTodo|Migration|Data and settings from pre-Akonadi times, see below|}}
{{FeatureTodo|Remote Search|Delegating searches to resources, see below|}}
{{FeatureTodo|Extended notifications|Item change notification do not yet include their source collections (real and virtual)|}}
{{FeatureTodo|Alternative for Akonadi::ResourceBase|Not using the scheduler to avoid the serialization of operations, see RSS resource. (This will get very complicated. Maybe use a proxy ResourceBase for this, which is thread-pooled?)|}}
{{FeatureTodo|Collection parameter for Monitor::itemChanged() and Monitor::itemRemoved()|
If the item resides in several collections (normal + virtual collections) then emit those signals for each collection. Adding this would mean changing it in many places (Monitor, Observer, ...), this is lots of work but probably the right thing to do.
Related to virtual collections, since with them, items can be in multiple collections. Better wait until the Nepomuk stuff is finished?|}}
|}

=== Supported Types ===

Overview on the current state of support for various types:

{|
|-
! Type !! Serializer !! Multipart Support !! Models !! Views !! Resources !! Notes
|-
|Email||yes||partial||MessageModel, MessageCollectionModel, threading proxy model||?||maildir, IMAP||threading agent
|-
|News||yes (1)||partial (1)||(1)||(1)||NNTP||
|-
|Contact||yes||no||ContactModel||-||vCard, facebook, KRes||
|-
|Events||yes||no||EventModel||-||iCal, KRes||
|-
|Notes||no||no||-||-||-||not started yet
|-
|Feeds||yes||no||Feeds, Items||?||OPML||GSoC in playground/pim
|-
|Bookmarks||yes||no||-||-||local bookmarks, del.icio.us||
|}

(1) see Email

=== Mail specific extensions ===

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureTodo|Extend Message Model|Add all required columns, save/restore layout, flag delegate, configurable columns, etc.|}}
{{FeatureTodo|Share mail flag code|Standard actions, standard flag enum/constants, Nepomuk interaction|}}
{{FeatureTodo|Extend ENVELOPE|Add more information to the envelope payload part in the serializer plugin, eg. trheading information is missing|}}
{{FeatureTodo|Fix/finish threading||}}
|}

=== Event/Todo/Journal specific extensions ===

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureTodo|Todo proxy model|See KOrganizers To-Do view|Bruno?}}
{{FeatureInProgress|Subtype identification|See discussion on kde-pim mailinglist|Kevin?}}
{{FeatureTodo|Agenda view|KOrganizer agenda view based on Akonadi|Bruno?}}
{{FeatureTodo|Month view|KOrganizer month view based on Akonadi|Bruno?}}
{{FeatureTodo|Timeline view|KOrganizer timeline view based on Akonadi|}}
|}

=== Resources, Agents and others ===

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureInProgress|KResource Akonadi bridge|for applications using KCal or KABC|kevin.krammer@gmx.at|Kevin}}
{{FeatureInProgress|Akonadi KResource bridge|for data accessed through KCal or KABC resources|kevin.krammer@gmx.at|Kevin}}
{{FeatureTodo|Expire Agent||}}
{{FeatureTodo|MBOX Resource||Thomas}}
{{FeatureTodo|Extend IMAP Resource||}}
{{FeatureTodo|POP3 Resource||Thomas}}
{{FeatureInProgress|RSS Resource|GSoC in playground/pim ([[Projects/PIM/RSS_framework_for_Akonadi|Details]])|Dmitry}}
{{FeatureTodo|Filter Agent||}}
{{FeatureTodo|Search||}}
{{FeatureTodo|Filter Rule GUI|Used by filters and searches|}}
|}

Resource status overview (this should list all resources existing in KDE3 or already under development for Akonadi):

{|
|-
! Resource !! Retrieve Collections !! Retrieve Items !! Change Collections !! Change Items !! Configuration !! Notes
|-
|iCal||yes (4)||yes (1) (2)||no||yes (5)||yes||does not yet watch for file changes
|-
|vCard||yes (4)||yes (1) (2)||no||?||yes||does not yet watch for file changes
|-
|maildir||yes (1) (4)||yes (1) (2)||?||?||yes||
|-
|mbox||no||no||no||no||no||not started yet, code exists in KMail
|-
|IMAP||yes (1) (4)?||yes (1) (2)||no||no||no||code exists in kio_imap4 and Mailody, support for extensions: quota, ACL, annotations missing, what about Kolab and Scalix?
|-
|POP3||no||no||no||no||no||not started yet,code exists in kio_pop3
|-
|NNTP||yes (4)||yes (2)||n/a||n/a||yes||Needs support for local collection names and collection hierarchy
|-
|Local Bookmarks||?||?||?||?||(3)||Code in akonadi/resources
|-
|OpenChange||?||?||?||?||?||Code in akonadi/resources
|-
|Facebook||?||?||?||?||?||Code in playground/pim
|-
|del.icio.us||?||?||?||yes||no||Code in playground/pim
|-
|KABC||no||yes||no||yes||yes||
|-
|KCal||no||yes||no||yes||yes||
|}

(1) only full sync supported currently, need optimization
(2) does not yet honor cache policy
(3) still relies on QSettings for configuration and/or doesn't provide configuration over D-Bus
(4) does not yet provide correct access control settings
(5) only adding new items, not changing existing ones

== Akonadi Braindump ==
Ideas/notes etc. on various open issues in Akonadi.

=== Akonadi Standard Actions ===

Idea: Have something like KStandardAction for Akonadi that not only includes the representation of the action but also its state management and the actual operations. Like libakonadi that should be splitted into a generic, type-independent part and be extensible for type-specific actions. This will enable code sharing among many applications and guarantee consistent actions everywhere.

State management: watch selection models of a collection and/or item model.

Use KXMLGUI for context menus in standard views to allow easy extensibility with custom actions.

Generic actions:
* new collection [done]
* new virtual collection
* delete collection [done for single selection]
* copy collection [done]
* cut collection
* paste collection [done]
* synchronize collection [done for single selection]
* synchronize resource
* synchronize everything
* show collection properties dialog [done]
* delete item(s) [done]
* copy item(s) [done]
* cut item(s)
* paste item(s) [done]
* paste native data
* tag item(s)
* comment item
* rate item(s)
* configure resource
* add resource? (would need a type parameter, etc.)
* delete resource
* manage local subscriptions [done]
* move to submenu
* copy to submenu

The list is definitely long enough to make this worthwhile.

=== Collection Model / Collection View ===

Ideas/missing features/bugs of the collection model/view:

* Enable/disable status columns
* Show status after the name (see KMail)
* Size column
* Save/restore layout
* Custom collection icons (see KMail, also needed for resource defined special folders (eg. Inbox)
* Status tooltips (see KMail in 3.5.9)
* Quick search
* Favorite folder view as proxy model on top of the normal collection model (FlatCollectionProxyModel might be helpful for there)
* Accumulated statistics (unread, total, size)
* Fix dnd: move/copy/cancel menu always shows up and never has any effect

=== Compatibility ===

Notes on how to keep long-term protocol, source and binary compatibility.

* <s>Detect server version in Akonadi::Session, might be useful in case of protocol extensions/changes</s>
* What about database server version updates?
* <s>Versioning or any other kind of serialization format meta data, we'll need that in case of changes in serialization formats (see eg. Robert's compression patch where this is needed)</s>
* <s>We currently use 32 bit ids, probably hard to change later on, is that enough?</s>
* <s>Plugin versioning</s>

=== Resource API issues ===

Notes/ideas/complaints about the Akonadi::ResourceBase API:

* Extremely error prone:
** Scheduler dead-locks when a requested operation is not correctly announced as finished, esp. a problem in error cases.
** Using the result methods multiple times or when not requested asserts
* <s>Item streaming is missing, requiring all data to be in memory at once</s>
* Non-incremental updates need to know the results of ItemSync to not have to provide all data, even for already existing/unchanged items.

=== API / BC issues ===

Smaller stuff that should be fixed before the ABI freeze and is not yet listed above:

* Cleanup the D-Bus format used by NotificationMessage
* No mentioning of "IMAP" in the public API, we are not using IMAP
* Naming and installed location of libraries, headers and executables (see discussion on kde-pim ML)
* <s>Payload part labels are QStrings, attribute types are QByteArray</s>

=== Deployment issues ===

* Multiple access: Should multiple Akonadi instances' mysqlds access a single set of data files the mysql will likely corrupt the data. This can happen in any NFS+YP installation where users can log onto any machine and access shared homes. MySQL relies on filesystem locking to prevent multiple access. [http://dev.mysql.com/doc/refman/6.0/en/multiple-servers.html MySQL multiple instance docu].
* [http://dev.mysql.com/doc/refman/6.0/en/innodb-restrictions.html InnoDB tables should not be used on NFS].
* NFS speed: MySQL documentation recommends against locating its data files on network shares.
* AppArmor: Distros' AppArmor profiles prevent MySQL from writing outside its defined data directory (usually /var/lib/mysql). This is a problem at least with *buntu and openSUSE. These will need to be adapted. It is possible to daisy-chain profiles so that MySQL started by Akonadi receives a different profile to MySQL running standalone. An empty profile has all rights. Another possibility is to adapt the general MySQL profile so it can write to ${XDG_DATA_HOME}/akonadi(usually ${HOME/}.local/share/akonadi). Both support for profile chaining and ${HOME} may depend on the version of AppArmor installed. What about SELinux?
* Backup: MySQL data files should not be backed up without telling the mysqld process, otherwise a corrupt backup will be made. LOCK TABLES and FLUSH TABLES at the least. A dump can be made or mysqlhotbackup may be used in some circumstances. We should consider sysadmins' backup techniques when planning/promoting Akonadi, as a simple rsync cronjob with running Akonadi will not work. [http://dev.mysql.com/doc/refman/6.0/en/backup.html MySQL backup advice].

=== Account Creation Wizard ===

Notes on the resource configuration wizard discussion.

* WizardBase class
* Wizard discovery via .desktop files
* A wizard can configure multiple resources (eg. IMAP + LDAP for Kolab) and non-resources (mailtransport)
* Optionally hide resources completely covered by wizards in the Add Account dialog
* List wizards in the Add Account dialog
* Store Account -> Resources information to offer deletion of depending resources

=== PostgreSQL datastore support ===

First review of the akonadi code reveals PGSQL Qt driver is already supported, but the code is not totally ready for it. Some first reading comments about where to patch for supporting PostgreSQL too:

==== akonadi/server/src/storage/dbinitializer.cpp ====

* line 201..., ALTER TABLE ADD [UNIQUE] INDEX syntax is MySQL only, better use the common one CREATE [UNIQUE] INDEX ... one [done with revision 789899]
* line 303, QString DbInitializer::sqlType(const QString & type), LONGBLOB is the MySQL type, PostgreSQL will use BYTEA.
* line 362, qFatal("Implement index support for your database!");
mysql: SHOW INDEXES FROM %1
pgsql: SELECT c2.relname, i.indisprimary, i.indisunique, i.indisclustered, i.indisvalid, pg_catalog.pg_get_indexdef(i.indexrelid, 0, true), c2.reltablespace
FROM pg_catalog.pg_class c, pg_catalog.pg_class c2, pg_catalog.pg_index i
WHERE c.oid = '16713' AND c.oid = i.indrelid AND i.indexrelid = c2.oid
ORDER BY i.indisprimary DESC, i.indisunique DESC, c2.relname

relname | indisprimary | indisunique | indisclustered | indisvalid | pg_get_indexdef | reltablespace
--------------+--------------+-------------+----------------+------------+--------------------------------------------------------------+---------------
foo_pkey | t | t | f | t | CREATE UNIQUE INDEX foo_pkey ON foo USING btree (id) | 0
foo_time_key | f | t | f | t | CREATE UNIQUE INDEX foo_time_key ON foo USING btree ("time") | 0
(2 lignes)

==== akonadi/server/src/storage/datastore.cpp ====

* line 700, qint64 DataStore::highestPimItemId() const, seems wrong for a concurrent program (SELECT MAX(col) FROM table; is not reliable if another thread is inserting at the same time) : check the callers
* line 794, qint64 DataStore::lastInsertId( const QSqlQuery & query ), PostgreSQL doesn't provide concurrent-bogus last_insert_id, but from 8.2 accepts the syntax INSERT INTO ... RETURNING col1, col2, ...;
* line 806, QString DataStore::dateTimeFromQDateTime( const QDateTime & dateTime ), use PostgreSQL to_char() formatting function for date rather than having Qt do it

=== Documentation ===

* Avoid examples using KJob::exec() due to its problematic side-effects.
* Examples in the ItemCreateJob docs (and maybe others) operate on items in the root collection which does not work at all
* Resurrect the server API docs

=== Migration of pre-Akonadi data and settings ===

* KCal/KABC
** switch KRes resources to Akonadi KRes compat resources, use KRes Akonadi compat resource, basically injecting Akonadi inbetween
** Replace Akonadi KRes compat resources with their ported equivalent
** Application side does not need migration code, "only" port to Akonadi
* KMail
** Should migrate to one resource per account + one for previous local folders
** Problem: local folders are mixed mbox/maildir
*** Dedicated KMail compat resource?
*** Convert everything to maildir first?
** Flags are stored in proprietary binary format
* KNode
** Migrate every account to NNTP resource
** Local flags should be preserved, stored in proprietary binary format
** Local subscription state should be preserved (where is that stored?)
** Local folders using MBOX format + proprietary binary index
* Akregator

=== Search ===

* Delegation to resources still completely missing
** Requires query transformation
** Requires management for live searches
** Requires the ability to report search results (needs protocol extension)
* Query language still undecided, current options: XESAM, SPARQL
* Backend still undecided, current options: XESAM, Nepomuk

== KMail Breakdown Plan ==
The current plan is to put some parts of KMail into a stand-alone
library, independent of KMail. This increases code reuse (for example, the message composer could be shared with Mailody) and makes the code a lot easier to maintain and to port to Akonadi.

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureTodo|Bodypart formatters||}}
{{FeatureTodo|Reader Window||}}
{{FeatureTodo|Composer: Editor||}}
{{FeatureTodo|Composer: Message Composer||}}
{{FeatureTodo|Composer: GUI Window||}}
{{FeatureTodo|Queue Manager for mailtransport||}}
{{FeatureTodo|Templates: Core||}}
{{FeatureTodo|Templates: GUI||}}
{{FeatureTodo|Port KMCommands||}}
{{FeatureTodo|Port away from KMMessage and KMFolder* everywhere it is left|An idea might be: wrap KMMsgBase/KMMessage inside a reference counted Message class. Insulate everything else from it by wrapper functions. KMFolder should be easier...|}}
{{FeatureTodo|Migration application for index and other config||}}
{{FeatureTodo|Port MDNs||}}
|}

== The Road to World Domination ==

Sort of related so the stuff above but with a scope for all of KDE PIM and beyond.

{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Item !! Description !! Contact
{{FeatureTodo|Share identity config GUI parts|eg. the signature configuration widget|}}
{{FeatureTodo|Mailtransport Agent|Global shared outbox, central mail sending instance|}}
{{FeatureTodo|Recently sent to support in mailtransport|related to above, based on Akonadi/Nepomuk|}}
{{FeatureTodo|Composer engine|Shared stuff for KMail/KNode/Mailody: Crypto, editor, editor actions, attachment model, message assembly, etc.|}}
|}

== Akonadi FAQ ==

=== Where do I find the Akonadi config files? ===

''~/.config/akonadi/''

=== Where does Akonadi store my data? ===

''~/.local/share/akonadi/''

=== Which DBMS does Akonadi use? ===

So far only MySQL. There is some work on PostgreSQL support going on though. Basically, every database that is supported by QtSQL can be used, requiring minimal changes in the code at most. However, not all of them provide the features needed by Akonadi (see next two questions).

=== Why not use sqlite? ===

We tried. Really. It can't handle the concurrent access very well, in the best case this means ''very'' slow operations, but we've also seen deadlocks and failing transactions. Once that's fixed in sqlite, adjusting Akonadi to use it again instead of MySQL is no problem.

=== Why not use MySQL/Embedded? ===

We tried that as well, there are two reasons for not using it: No support for the InnoDB engine (which we need for transaction support) and poor availability (only OpenSUSE provided usable packages, needed a patched QSQL driver).

=== Do I need a running MySQL server? ===

No. Akonadi starts its own local MySQL server (unless configured otherwise, see next question). All you need is having the 'mysqld' binary installed at runtime (usually found in the mysql-server package of your distribution).

=== Can Akonadi use a normal MySQL server running on my system? ===

Yes, it can. You find the corresponding settings in ''~/.config/akonadi/akonadiserverrc''.

=== I don't like a database server because of backups/running on NFS/etc. ===

See section "Deployment Issues" above, we are aware of that and working on it. Some of these, like backup/restore are already implemented. But please be aware that most of this issues also existed before (eg. with KMail's custom binary indexes).

=== Can a single Akonadi instance be used by multiple users? ===

No. There has to be one Akonadi server instance per user. However, it is possible to use a shared database server.

=== Can I access the Akonadi server on a remote machine? ===
No. Akonadi is not a groupware server. It's a local cache only.

=== I have an unknown error 255 when running akonadictl ===
Distributions using Apparmor require you to run '''aa-complain mysqld''' with root privileges then reload apparmor.

=== I get a "DB error: 'Could not open required defaults file: /home/$username/.local/share/akonadi//mysql.conf" ===
Although you probably don't have an apparmor in your processlist, you are still using it, run '''aa-complain mysqld''' and try again.

=== What's the difference to EDS? ===
EDS is limited to contacts and calendar data, Akonadi is type-independent. Especially, Akonadi is designed to also handle high-volume data such as email. Akonadi and EDS also differ largely in their access protocol on the technical level (Corba/D-Bus vs. local socket with IMAP-like protocol/D-Bus) as well as one the protocol level (type specific vs. generic).

[[Category:PIM]]

Contribute/Bugsquad/BugDays/KDEPIMKrush1/KMail

2008-08-13T14:29:48Z

Krop: /* Bugs */

===KMail===

====Application specific tips====
any application specific tips for KMail go here.

====Testers====
Please put your IRC nickname and KDE PIM svn revision number in the table if you are testing this app.
{|
|-
!IRC Nickname !! KDE PIM svn revision number tested. !! Testing details
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r818299 || testing... ||
|-
|[[User:Earthwings|Earthwings]]|| svn trunk r812281 || done ||
|-
|gemegik || debian exp 4.0.74-1 || done
|-
|[[User:philrod|PhilRod]]||svn trunk r812108 || flicking through ||
|-
|[[User:Gkiagia|gkiagia]]||svn trunk r846201 || in progress ||
|}

====Bugs====
Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with <nowiki>~~~</nowiki>.

* <s>Crash when clicking on the "Inbox" folder of my IMAP account just after creating it with the first start wizard. Backtrace at http://pastebin.ca/1028716. Notice that the server uses Maildir, not mbox. After a restart of kmail it works now. [[User:Earthwings|Earthwings]]</s>
** IMAP layer has changed substantially, and since we cannot reproduce this, closing. ([[User:Grundleborg|Grundleborg]] and tmcguire).
* <s>The first start wizard seems to have added the SMTP server twice. [[User:Earthwings|Earthwings]]</s>
** FIXED. tmcguire
* <s>Per default I don't get any new mail notification: kmail.notifyrc has Actions=None for new mail and the systray is not show per default. [[User:Earthwings|Earthwings]]</s>
** These are both intentional behaviour. tmcguire
* Clicking on the "Searches" folder brings up the standard "Welcome to kmail" widget. It would be nice if one would be directed to the "Find Messages" widget in some way. [[User:Earthwings|Earthwings]]
* I think the "Search" button should be on top in the "Find Messages" widget, not the "Stop" button. Maybe both could even be the same button, they should be mutually disabled anyway? [[User:Earthwings|Earthwings]]
* "Switch Application Language" is listed in the Help menu. I think it should be in Tools, if it should be there at all. [[User:Earthwings|Earthwings]]
** [[User:finex|FiNeX]] it is the default position for all KDE4 apps.
* "Switch Application Language" should resize when adding a new fallback language, or start with a larger default size. [[User:Earthwings|Earthwings]]
** This dialog comes from kdelibs -- [[User:TMG|TMG]] 18:39, 6 June 2008 (CEST)

* Kleopatra Self Test Result shows a message with tags (para, application, icode) for the "GpGConf (Configuration) installation" item in the "Proposed Corrective Action" section. [[User:Earthwings|Earthwings]]

* Kleopatra startup height is too small. [[User:Earthwings|Earthwings]]

* Kleopatra fails to import my S/MIME X.509 Certificate: "An error occurred while trying to import the certificate /home/kde-devel/thawte.p12: Decryption failed". I can import that certificate in Thunderbird. [[User:Earthwings|Earthwings]]

* Kleopatra crashes when clicking on "Settings", "Configure Kleopatra", backtrace at http://pastebin.ca/1028744. [[User:Earthwings|Earthwings]]

* I can select my OpenGPG key for encryption, but not for signing: It's not listed for selection. Kleopatra says it's fine for signing, and I use it in other applications for signing. [[User:Earthwings|Earthwings]]

* "Check Messsages" does not seem to trigger the new messages event: The number of mails in the systray increases, but I don't get a popup. Clicking on a folder that has new messages (IMAP) triggers the event though. [[User:Earthwings|Earthwings]]

* <s>New message : View > All fields. Comboboxes don't show immediately. They show up on next "new message". -- gemegik</s>
** Already fixed. -- [[User:TMG|TMG]] 18:39, 6 June 2008 (CEST)

* In custom searches, next/previous toolbar buttons not working. -- gemegik

* Enabling the "out of office reply" through sieve (which my server does not support), I got some error messages (fine so far). Later I found kio_sieve in the process list, CPU usage 100% for some hours. [[User:Earthwings|Earthwings]]

* Encoding problem in searches names in french (saved in utf8, displayed as iso-8859-15) -- gemegik

* Crash when deleting a couple of messages (non-contiguous), backtrace at http://pastebin.ca/1028815. [[User:Earthwings|Earthwings]]

* In message edition : "edit > remove quote characters" only works for the first line of a selection. -- gemegik

* <s> Menu item "help > about kmail" and "help > kmail introduction" change icon when hovering. Same for systray.</s> -- gemegik

* [[User:Krop|Krop]] Crash when a filter on incoming message move an inbox message to an imap directory : http://pastebin.com/m633cf585

* [[User:Krop|Krop]] <s>Settings/security/S-Mime tab is fully greyed even if gpgsm is detected</s>
** [[User:Krop|Krop]] Solved after installing gnupg2

* [[User:Krop|Krop]] Chiasmus detection returns (when not detected) : The file /usr/local/bin/chiasmus doesn't exist or is not executable. Doesn't it look in all directories in $PATH ?

* Right-click on a message from a ML -> "create filter" -> "filter on mailing list" is disabled. Right click on the message again, and the option appears. In the "Message" menu, the "filter on mailing list" option is never enabled, AFAICT. [[User:Philrod|Philrod]]

* <s>After starting KMail, the text "Starting..." stays in the status bar indefinitely. [[User:Grundleborg|Grundleborg]]</s>
** <s>If, for example, you select "Local folders" in the sidebar, then click on the link to "documentation" in the main view, the status bar changes to "Opening URL..." and stays at that even after the URL has been opened and then closed. [[User:Grundleborg|Grundleborg]]</s>
*** Fixed those two cases in r818405. --[[User:TMG|TMG]] 16:13, 8 June 2008 (CEST)

* <s>"Ham" and "Spam" toolbar buttons are enabled even when no emails are selected. [[User:Grundleborg|Grundleborg]]</s>
** Fixed in r818362

* <s>If I select Tools->Anti-Spam wizard, the bottom line of text in the dialog that opens (starting "Sorry, no spam detection tools...") does not wrap, so at the default dialog size, it gets cut off after the word "found". If you resize the dialog, more of the line becomes visible, but it doesn't ever wrap. [http://www.grundleborg.com/kde/bugsquad/screenshots/anti-spam-wizard-bug.png Screenshot of the bug.] [[User:Grundleborg|Grundleborg]]</s>
** svn commit 818344 fixes this. [[User:Grundleborg|Grundleborg]]

* <s>When resizing horizontally the Tools->Anti-virus wizard dialog on the first page, the image area gets wider, and the text area stays the same. [http://www.grundleborg.com/kde/bugsquad/screenshots/anti-virus-wizard-bug.png screenshot of the resized dialog.] [[User:Grundleborg|Grundleborg]]</s>
** svn commit 818355 fixes this. [[User:Grundleborg|Grundleborg]]

* [[User:Gkiagia|gkiagia]] View->Headers setting is not saved in the mail windows. I open the mail in a new window, set the header, close it, then reopen it and the default header is shown again. There is no option to set this from the configuration dialog too.

* [[User:Gkiagia|gkiagia]] Attachments are reported with the wrong size. I have a testcase here where a photo of 3.2 MB is displayed as 4.3 MB. This happens with any attachment but it is more visible with big sizes. Contact me to forward you the testcase if you want.

* [[User:finex|FiNeX]] Template parsing doesn't consider "%CURSOR" on forward.

* [[User:Krop|Krop]] When minimized in the systray, restoring kmail will bring the window on the first desktop (expected : on the current desktop)

Contribute/Bugsquad/BugDays/KDEPIMKrush1/Akregator

2008-07-05T08:21:22Z

Krop: /* Bugs */

===Akregator===

====Application specific tips====
any application specific tips go here.

====Testers====
Please put your IRC nickname and KDE PIM svn revision number in the table if you are testing this app.
{|
|-
!IRC Nickname !! KDE PIM svn revision number tested. !! Testing details
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r803492 || not tested yet
|-
|[[User:reldruh|reldruh]]||4.1 Beta1 || done
|-
|gemegik || 4.0.74-1 debian experimental || done
|-
|FilledVoid || 4.1 Beta1 || done
|-
|[[User:krop|krop]]||svn trunk r812273 || ||
|-
|andy_ || svn trunk r818102 || ||
|-
|[[User:Blauzahl|Blauzahl]] || svn trunk pimlibs r816572 apps r816865 || doing
|}

====Bugs====
Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with <nowiki>~~~</nowiki>.

* Bug: Add 1 feed to an already existing folder in akregator (I used http://arstechnica.com/index.rssx). This should work fine. Try to add a second feed to the same folder (I used http://www.osnews.com/files/recent.xml). This should not work. Try to add the second feed again and akregator should crash. Backtrace is at http://pastebin.ca/1028657 -- [[User:Reldruh|Reldruh]]

* Bug: when loading the full site in the preview pane (advanced option) and scolling and article with the mouse whell, scroll goes out of page boundaries and the preview pane only displays garbage then. -- gemegik

* Bug: When I hide the 'total' and 'not read' columns from the feed list, they reappear at next startup. -- gemegik

*<s> Bug: Feed favicons don't stay between sessions, they only appear when fetching the feed. -- gemegik
** Confirmed [[User:Krop|Krop]]</s>

* Regression: In 3.5, akregator printed "$feedname ($unread_count)" as the feed title if the 'total' and 'not read' columns were hidden. -- gemegik

* Regression: Doesn't follow the konqueror preferences for smooth scrolling (active in akregator while disabled in konqui). -- gemegik

* [[User:Krop|Krop]] Settings/Archive/"limit feed archive size to..." doesn't accept values > 99 (same thing for "delete articles older than...")

* <s>[[User:Krop|Krop]] Settings/Archive/"keep all articles" and "disable archiving" buttons is always unchecked when you open settings.</s>

* <s>[[User:Krop|Krop]] Settings/Advanced : the "Configure" button is always greyed whatever choice you make.</s>

* [[User:Med|Med]] When a new feed entry is received, it it contains an apostrophe in the title, it will be displayed as '. It works when marking a message as unread too. If i restart akregator, the apostrophes are displayed correctly. Images that illustrate the problem [http://mboquien.free.fr/akregator_1.png receiving a new entry] and [http://mboquien.free.fr/akregator_2.png after having clicked on this entry].

*When opening an article in a new tab, ctrl+w does not close it. [[User:Med|Med]]
**[http://pastebin.com/m531e246b One liner patch]. Link sent on #kontact but i put it here too in case it would be lost. [[User:Med|Med]] 03:15, 28 May 2008 (CEST)

*When opening an article in a tab, if the page contains an error, a small red bug is displayed at the bottom of the screen. Unfortunately they are not removed when a tab is closed. I think the expected behaviour would be that the bug is present only in relation to the active tab (therefore no bug would be displayed if there are bugs in inactive pages). [[User:Med|Med]]

*<s>When sorting articles after Date, new articles of are showing between Yesterday and Thursday, see [http://img55.imageshack.us/img55/6729/snapshot1vu1.png here].</s> -- andy_

*When toggling View Modes ( Normal -> Combined -> Normal ) the feed preview list becomes empty. However does change back on clicking on another feed and returning back. See [http://img300.imageshack.us/img300/8796/verysmallbugth6.jpg here ] -- FilledVoid

*Marking an article with a shortcut does not work (ctrl+I for important, ctrl+U for unread, etc.). It works when right-clicking and selecting in the menu though. [[User:Med|Med]]

*(Usability) When opening, "Feeds" is very narrow compared to the other fields, or at least it is narrow enough that I can't see what any of the default feeds are. I figure this is probably the most important field, but at first I didn't realize it was something I wanted to be reading.[[User:Blauzahl|Blauzahl]]

Contribute/Bugsquad/BugDays/KDEPIMKrush1/Kontact

2008-07-05T08:13:04Z

Krop: /* Bugs */

===Kontact===

====Application specific tips====
any application specific tips go here.

====Testers====
Please put your IRC nickname and KDE PIM svn revision number in the table if you are testing this app.
{|
|-
!IRC Nickname !! KDE PIM svn revision number tested. !! Testing details
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r803492 || not tested yet ||
|-
|[[User:krop|krop]]||svn trunk r812273 || Done ||
|}

====Bugs====
Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with <nowiki>~~~</nowiki>.

* <s>[[User:Krop|Krop]] Akregator toolbars troubles when embedded in Kontact: RMB/toolbar in a standalone akregator: http://tinyurl.com/4cu6hj // same menu in kontact: http://tinyurl.com/5vcx35</s>

* <s>[[User:Krop|Krop]] Kontact ruins the toolbars position (#1): Akregator standalone: http://tinyurl.com/4lb9wb // embedded Akregator: http://tinyurl.com/5eeyuo If you change the active element then come back on akregator, the toolbar will reappear on the right border (same behaviour with Korganizer & Kjots)</s>

* <s>[[User:Krop|Krop]] Kontact shows an empty window when trying to configure embedded akregator: http://tinyurl.com/3otwkc</s>

* <s>[[User:Krop|Krop]] Incomplete line in Kontact settings/Next events : http://tinyurl.com/5xsj8s </s>
** [[User:finex|FiNeX]] Fixed.

* <s>[[User:Krop|Krop]] The Kmail "Create To-Do" button has no effect when kmail is embedded in Kontact</s>
** [[User:vkrause|Volker]] Fixed in revision 813654.

*<s>[[User:Krop|Krop]] Help/About kontact and Help/About kontact/License show a copyright 2001-'''2004'''</s>

*<s>[[User:Krop|Krop]] Kontact/Time tracker : the "New task" button has no effect as discussed at https://bugs.kde.org/show_bug.cgi?id=162725.</s>
** [[User:tstaerk|Thorsten]] Fixed in revision 818274.

*<s> [[User:Glenner|Glenner]] maintoolbar in kontact does not appear. The kontactui.rc file does not get installed. Adding "install( FILES kontactui.rc DESTINATION ${DATA_INSTALL_DIR}/kontact)" to CMakeLists.txt fixes this here, but i am not sure if this correct since there must be a reason this line got removed recently..</s>
** [[User:Glenner|Glenner]] Fixed in r818440

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

2008-06-28T14:13:29Z

Krop: /* Bugs no longer present in 4.x */

===Bugs no longer present in 4.x===
If a bug is reported against a version of KDE before 4.0, but the bug can no longer be reproduced in KDE 4.x, then it should be listed here. Please '''do not''' close the bug. The Konqueror developers would like to check each one before they are closed.

*<s>{{Bug|159643}} Works as expected in svn revision 823139</s>.
*{{Bug|159599}} Works as expected on svn revision 823139.
*{{Bug|139567}} No more freezes here. [[User:Jtamate|Jtamate]] katastrophe 02:55, 20 June 2008 (CEST) i found a bug there
*<s>{{Bug|139734}} the right button in scrollbars shows a menu. [[User:Jtamate|Jtamate]]</s> closed with then, hope thats right katastrophe 02:50, 20 June 2008 (CEST)
*<s>{{Bug|160207}} State remains across different views. Shortcut works too. [[User:Dpalacio|dpalacio]]</s> katastrophe 03:19, 20 June 2008 (CEST) closed as later
*<s>{{Bug|161363}} the favicons behave correctly when opening new tabs in the steps given [[User:Ramblurr|Ramblurr]]</s>
*{{Bug|161375}} flash seems to be working properly, though i am not using x86_64 and the reporter was. [[User:Ramblurr|Ramblurr]]
** flash is a pain. we should get someone with 64 to test that to make double sure (until recently it didn't work, hey everyone help me figure out how recently and fill in the flash chart above in the labor section), and then i'll write some nice anti-3.5.9 comment if need be. In general, a lot of the flash bugs are dups.[[User:Blauzahl|Blauzahl]]
*<s>{{Bug|160416}} can't reproduce a crash for that. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|139504}} asks and sends the cookies as expected. Also it is a possible duplicate bug</s> [[User:Jtamate|Jtamate]]
** has been marked as duplicate.
*<s>{{Bug|162969}} can't reproduce [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|139667}} can't reproduce [[User:Jtamate|Jtamate]]
** I can't either, but i asked the reporter to see if it still happens. [[User:Sahaqiel|sahaqiel]]</s>
*{{Bug|141351}} Can reproduce it in 3.5.9 , but not in trunk [[User:Sahaqiel|sahaqiel]]
*<s>{{Bug|141128}} Can't reproduce with either kde 3.5.9 or trunk. [[User:Sahaqiel|sahaqiel]]</s>
*<s>{{Bug|133924}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s> katastrophe
*<s>{{Bug|133526}} Fixed in runk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|133410}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|133592}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|133783}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|133951}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|133957}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|134105}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|161532}} Can't reproduce in trunk 814918 [[User:Ramblurr|Ramblurr]]</s>
*<s>{{Bug|141550}} Can't reproduce with 3.5.9 and apparently neither can the reporter. </s>[[User:Sahaqiel|sahaqiel]]
*{{Bug|141157}} Still present in 3.5.9. Dolphin can only show autocomplete for folders, and all characters show up in konq4 trunk. [[User:Sahaqiel|sahaqiel]]
*{{Bug|141510}} Still there in 3.5.9 but fixed in trunk. [[User:Sahaqiel|sahaqiel]]
*<s>{{Bug|161676}} Can't reproduce in trunk r814918 [[User:Ramblurr|Ramblurr]]</s>
*<s>{{Bug|161656}} Can't reproduce in trunk r814918 [[User:Ramblurr|Ramblurr]]</s>
*<s>{{Bug|134452}} File navigation through keyboard is fine. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|134361}} Fixed in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|134378}} confirmed in 3.5.9 (where probably it won't be fixed). Dolphin instead doesn't have this feature (added ppenz on CC). [[User:Finex|FiNeX]]</s>
*<s>{{Bug|134570}} Probably the bug was about amule, not KDE. Anyway there is no feedback from the reporter (since 16 months) and the bug seems not be reproduced anymore with recent amule/kde versions. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|134776}} Confirmed that digg.com registration process is correctly rendered and it doesn't consume a lot of CPU. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|155325}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*<s>{{Bug|155307}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*<s>{{Bug|155236}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*<s>{{Bug|154993}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*<s>{{Bug|154965}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*<s>{{Bug|155025}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*{{Bug|155077}} Can't reproduce in trunk [[User:Krop|Krop]]
*<s>{{Bug|155130}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*{{Bug|155247}} Can't reproduce in trunk [[User:Krop|Krop]]
*<s>{{Bug|139112 }} fixed in trunk and 3.5.9. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|161689}} Gmail doesn't crash r814918 [[User:Ramblurr|Ramblurr]]</s>
*<s>{{Bug|161719}} spell checking works [[User:Ramblurr|Ramblurr]]</s>
*<s>{{Bug|139126}} Solved in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*{{Bug|139339}} Solved in 3.5.9 and trunk. [[User:Finex|FiNeX]]
*<s>{{Bug|139437}} Cannot reproduce in 3.5.9 and trunk.</s> [[User:Finex|FiNeX]]
** I can't either. WORKSFORME [[User:Sahaqiel|sahaqiel]]
*<s>{{Bug|139412}} Cannot reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]
*<s>{{Bug|138219}} cannot reproduce in 3.5.9 and trunk.</s> [[User:Frank78ac|Frank78ac]] closed by reporter. [[User:Frank78ac|Frank78ac]]
*<s>{{Bug|157439}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*<s>{{Bug|157073}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*{{Bug|157076}} Can't reproduce in trunk [[User:Krop|Krop]]
** I can reproduce it in both 3.5.9 and trunk, but it seems a feature. The devs have to make a call on that one. [[User:Sahaqiel|sahaqiel]]
<s>*{{Bug|157112}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
*<s>{{Bug|157217}} Can't reproduce in trunk [[User:Krop|Krop]]</s>
** WORKSFORME too [[User:Sahaqiel|sahaqiel]]
*<s>{{Bug|157334}} Can't reproduce in trunk [[User:Krop|Krop]]</s> closed katastrophe 01:35, 20 June 2008 (CEST)
*<s>{{Bug|140487}} Solved in trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|140057}} Confirmed that it is solved in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|140315}} KDE 4 doesnt have "settings:/" anymore. Bug not reproducible. (fixed in 3.5.9)</s>
*{{Bug|140110}} The page seems correctly rendered in 3.5.9 and trunk. [[User:Finex|FiNeX]]
** Only renders correctly in trunk, and renders correctly sometimes in 3.5.9, but a reload fixes the issue. I placed two different renders from kde 3.5.9 as attachments. [[User:Sahaqiel|sahaqiel]]
*{{Bug|140229}} Solved in trunk. [[User:Finex|FiNeX]]
*<s>{{Bug|141125}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|141128}} Confirmed that the crash doesn't happen on a specific webpage. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|141246}} "system:/" doesn't exist anymore on KDE4. [[User:Finex|FiNeX]]</s>
*<s>{{Bug|141510}} Fixed in trunk. [[User:Finex|FiNeX]]</s>
*{{Bug|141269}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]
*{{Bug|141268}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]
*<s>{{Bug|141550}} Can't reproduce in 3.5.9 and trunk. </s>[[User:Finex|FiNeX]]
** Since we both can't reproduce, WORKSFORME [[User:Sahaqiel|sahaqiel]]
*{{Bug|141525}} Can't reproduce in 3.5.9 and trunk. [[User:Finex|FiNeX]]
*<s>{{Bug|160735}} Can't reproduce in 3.5.8 and trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|160819}} Can't reproduce in 3.5.8 and trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|160886}} Can't reproduce in 3.5.8 and trunk. </s>[[User:knusperfrosch|knusperfrosch]]
*<s>{{Bug|161008}} Can't reproduce in 3.5.8 and trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|161165}} Can't reproduce in 3.5.8 and trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|161178}} Can't reproduce in 3.5.8 and trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|146539}} kde4 trash files are in $HOME/.local/share/Trash/files/ [[User:Jtamate|Jtamate]]</s>
*{{Bug|128353}} Can't reproduce in trunk. --[[User:Jtamate|Jtamate]] 17:48, 6 June 2008 (CEST)
*{{Bug|79348}} Can't reproduce in trunk --[[User:Jtamate|Jtamate]] 18:15, 6 June 2008 (CEST)
*<s>{{Bug|138802}} Works for me in 3.5.9 and trunk.[[User:Frank78ac|Frank78ac]]</s>
**Closed by reporter.
**Note that I got a crash in trunk, but this is a separate issue. [[User:Frank78ac|Frank78ac]]
*<s>{{Bug|138810}} Works for me in 3.5.9 and trunk. [[User:Frank78ac|Frank78ac]]</s>
** Same with me, WORKSFORME. [[User:Sahaqiel|sahaqiel]]
*<s>{{Bug|138815}} Works for me in 3.5.9 and trunk.</s> [[User:Frank78ac|Frank78ac]]
**Reporter confirmed that it works, closing bug. [[User:Frank78ac|Frank78ac]]
*<s>{{Bug|159266}} Works for me in kde beta 1. [[User:tazz|gaurav]] And me in 823139. [[User:hays|hays]]</s> katastrophe
*<s>{{Bug|159814}} Can't reproduce in trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|159984}} Can't reproduce in trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|160066}} Can't reproduce in trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|159849}} Can't reproduce in trunk. [[User:knusperfrosch|knusperfrosch]]</s> me too, im closing with worksforme katastrophe 03:28, 20 June 2008 (CEST)
*<s>{{Bug|159814}} Can't reproduce in trunk. [[User:knusperfrosch|knusperfrosch]]</s>
*<s>{{Bug|160442}} Can't reproduce in trunk. [[User:knusperfrosch|knusperfrosch]]</s> worksforme katastrophe 14:58, 20 June 2008 (CEST)
*{{Bug|138849}} Can't reproduce in 3.5.9 and trunk. [[User:Frank78ac|Frank78ac]]
*<s>{{Bug|75809}} Can't reproduce in 3.5.9 and trunk. --[[User:Jtamate|Jtamate]] 22:19, 11 June 2008 (CEST)</s> katastrophe 14:04, 27 June 2008 (CEST)
*{{Bug|135622}} the settings dialog can be resized down to 520x520 katastrophe 05:25, 20 June 2008 (CEST)
*{{Bug|135623}} cant reproduce with trunk katastrophe 05:38, 20 June 2008 (CEST)
*{{Bug|136030}} works for me in trunk katastrophe 06:21, 20 June 2008 (CEST)
*{{Bug|136316}} cant reproduce with trunk katastrophe 07:07, 20 June 2008 (CEST)
*{{Bug|136544}} cant reproduce, seems ok with trunk katastrophe 07:46, 20 June 2008 (CEST)
*{{Bug|141625}} i think the reporter means the search bar, but i cant reproduce in trunk katastrophe 17:15, 20 June 2008 (CEST)

The following bugs are clear wishes that I think are implemented in kde 4.
*<s>{{Bug|69389}} show disk space --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)</s> katastrophe 17:17, 21 June 2008 (CEST)
*{{Bug|69437}} user agent configurable in gui --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST) --- yes, but you cant still add new custom browser identification strings in the gui, i think that was meant
*<s>Bug|125429}} the directory sorting is stored and retrieved in .directory files --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)</s> closed katastrophe 17:29, 21 June 2008 (CEST)
*<s>{{Bug|134009}} the directory sorting is stored and retrieved in .directory files --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)</s> katastrophe 17:17, 21 June 2008 (CEST)
*{{Bug|53805}} ads supression --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)

The following bugs are wishes that looks like bugs instead of wishes.
*{{Bug|88642}} view menu order --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)
*{{Bug|132780}} page with a lot of input boxes is redered slowly --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)
*{{Bug|136025}} slow rendering of tables --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)
*{{Bug|137330}} do not recognize the mime tipe of mbox file --[[User:Jtamate|Jtamate]] 15:20, 12 June 2008 (CEST)
*{{Bug|141726}} cant reproduce with trunk katastrophe
*{{Bug|141815}} cant reproduce with trunk katastrophe

Contribute/Bugsquad/BugDays/AmarokDay1

2008-06-17T09:05:13Z

Krop: /* Division of Labour */

{{warning|Instead of editing the whole wiki page, please enable editing by section in your preferences and click the Edit link next to each section header to edit content. Like this we'll mostly prevent conflicts if several people edit the page at once.}}

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

'''The goal of this bug-day is to check for bugs that are fixed, duplicates, are not going to be fixed in Amarok 1.4.x or are already fixed/implemented in Amarok 2. This will enable the Amarok developers to deal with bugs more easily, and so have more time left to actually code on Amarok 2.''' When you have closed or commented on a bug, please list it in the appropriate section below, so that a second triager can see if they can confirm it.

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. Amarok team members will be both there and in #amarok to answer your questions. If none of them are around please note the bug in the list below so they can be dealt with later.

You should be working with Amarok 1.4.9.1 and Amarok 2 for testing these bugs. To make it easier for you to obtain Amarok 2 we provide nightly builds of it. So far Packages for Kubuntu and openSUSE are available. For more information check out the [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Neon wiki page]. For openSUSE packages please also ask in #amarok.neon. Amarok 1.4.9.1 should be available in your distro repositories.

Please mention which version and distro you are working with if necessary. (For Neon mention the build date from the Amarok about dialog. It is in the middle of the first tab.)

===Unclear===
If a bug report has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a bug is severe we want to know about it.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to the version specified in the other fields of the original bug report.

===What to close?===
Amarok 1 and Amarok 2 are very different and a lot of bugs of 1 don't apply to 2 and vice-versa. Amarok 1.4.x is in bugfix-only mode. This means we are only going to fix bugs where the risk of regression is minimal. No new features are going to be implemented in Amarok 1.4.x. So please be aggressive with closing bugs that are not going to get fixed in 1.4.x anyway. No need to keep them around. For feature requests please check Amarok 2. If it is implemented there then close the bug, otherwise please speak with the Amarok team to see if they plan to implement it. If they don't, then close it as WONTFIX.

'''REMEMBER: If you think a bug should be closed, list it in the appropriate section below BEFORE closing it, so another triager can check it. Before a bug can be closed it must be checked by TWO triagers. Not just you!'''

===How to comment===
Please add a note like "comment from KDE bugsquad member" at the top of your comments so Amarok developers know who you are. Always leave a comment explaining why you change something. If you spoke with a member of the Amarok team please mention who. If you close a bug report for 1.4.x you might want to consider using one of the following stock replies:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.''

And if a feature request has to be moved to Amarok 2:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your feature request can not be implemented in Amarok 1, as Amarok developers do not have the resources for it and risk of regression would be too high. I am therefore moving your request to Amarok 2. I cannot make any guarantee as to whether is will get implemented there or not though. Thank you for your report.''

And if something has already been implemented in Amarok 2:

''This feature is already implemented in Amarok 2. However, Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2, so your feature request can not be implemented in Amarok 1 as the risk of regression would be too high. I am therefore closing this report. Thank you for your report and have fun with Amarok.''

===Double Check!===
'''Please list and sort bugs below to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.''' Things which are not closes can be changed as you go.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Always add your comments on bugzilla as well as the wiki for a more complete feedback by users and developers.

==Details==

Please get a bugzilla account (bugs.kde.org) and a techbase.kde.org account. Then "sign in" below, and select a period 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, as we will cross-check everybody else's bugs. This will help to reduce the number of incorrect actions taken on bugs.'''

==How to get a Backtrace with Amarok==

Simple gdb howto:

# start Amarok
$ amarok

#switch terminals and get amarok's pid
$ pgrep amarok

#start gdb
gdb

#attach to amarok's process
gdb> attach <pid>

#let it load debugging symbols, then type continue
(gdb) continue

#Do what you want to amarok to make it crash. Once it has crashed type
(gdb) bt

==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.)
{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Ramblurr|Ramblurr]] || svn trunk latest ||
|-
|[[User:Kage Jittai|Kage_Jittai]] || kdelibs r818475 a2 r820610 ||
|-
|[[User:Blauzahl|Blauzahl]] || kdelibs r820643 a2 r820651 & debian sid 1.4.9.1 ||
|-
|[[User:Mdhowe|Artisian]] (also Mdhowe) || Ubuntu Nightly r820526 & Ubunutu 1.4.9.1 ||
|-
|[[User:Aides|Aides]] || kdelibs r820524 a2 r820697 & Gentoo 1.4.9.1 ||
|-
||[[User:lemma|lemma]] || kdelibs r820510, a2 820602, debian sid 1.4.9.1 ||
|-
||[[User:annma|annma]] || svn trunk latest Revision: 820699||
|-
||[[User:progger1986|progger1986]] || kdelibs r812186 & 1.4.9.1||
|-
||[[User:Krop|Krop]] || kdelibs r820750, a2 820750, debian sid 1.4.9.1 ||
|-
||[[User:Leuty|Leuty]] || Kubuntu Nightly r820526 and Kubuntu 1.4.9.1 ||
|-
|| [[User:Grundleborg|Grundleborg]] || kdelibs r820659, a2 r820677, mdk 2008.1 1.4.8||
|-
|| [[User:Mamarok|Mamarok]] || Kubuntu 1.4.9.1 and Kubuntu Nightly r820526 ||
|-
|| [[User:Bram85|Bram85]] || SVN 820K and Amarok 1.4.9.1 ||
|}
{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a month that is not already taken from the list below and then query bugs.kde.org for all bugs in that month. Please put your irc nickname in the table below next to the month so we don't duplicate months.

The bugzilla query to use for this triage day is TBD. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month/time period !! IRC Nickname !! Status !! Query !! Number of Bugs
|-
| 2005-03 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-03-01&chfieldto=2005-03-31&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-04 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-04-01&chfieldto=2005-04-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-06 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-06-01&chfieldto=2005-06-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-09 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-09-01&chfieldto=2005-09-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-10 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-10-01&chfieldto=2005-10-31&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-11 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-11-01&chfieldto=2005-11-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-12 || [[User:Mdhowe|Artisian]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-12-01&chfieldto=2005-12-31&chfieldvalue=&newqueryname= Query] || 6
|-
| 2006-02 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query] || 2
|-
| 2006-03 || [[User:Blauzahl|Blauzahl]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query] || 7
|-
| 2006-04 || [[User:Mdhowe|Artisian]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query] || 6
|-
| 2006-05 || [[User:Kage Jittai|Kage Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query] || 8
|-
| 2006-06 || [[User:Mamarok|Mamarok]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query] || 12
|-
| 2006-07 || [[User:Aides|Aides]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query] || 13
|-
| 2006-08 || [[User:Annma|Annma]]|| Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query] || 13
|-
| 2006-09 || [[User:progger1986|progger1986]]|| Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query] || 17
|-
| 2006-10 || [[User:Aides|Aides]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2006-11 || [[User:Lemma|Lemma]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query] || 14
|-
| 2006-12 || [[User:Lemma|Lemma]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query] || 16
|-
| 2007-01.1 || [[User:Krop|Krop]] || Incomplete || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=139722%2C140134%2C140078%2C139756%2C140020%2C140270%2C139610%2C139897%2C139497%2C139538%2C139549%2C139647%2C139716%2C139763%2C139764%2C139772%2C&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-01.2 || [[User:Lemma|Lemma]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=139803%2C139805%2C139836%2C139889%2C139963%2C140001%2C140080%2C140170%2C140338%2C140357%2C140428%2C140461%2C140462%2C140618%2C140752%2C140757%2C140795&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-02.1 || [[User:Nightrose|Nightrose]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=141780%2C142278%2C141935%2C142111%2C141578%2C141404%2C142282%2C141049%2C141103%2C141147%2C141276%2C141291%2C141323%2C141412%2C141426%2C141431&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-02.2 || [[User:Nightrose|Nightrose]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=141445%2C141466%2C141571%2C141581%2C141634%2C141652%2C141736%2C141777%2C141856%2C141894%2C141930%2C142099%2C142114%2C142156%2C142174%2C142192%2C142230&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-03.1 || [[User:Aides|Aides]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=142757%2C142712%2C142899%2C143420%2C143485%2C143624%2C143163%2C142680%2C143421%2C142364%2C142433%2C142437%2C142797%2C142804%2C142805%2C&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-03.2 || [[User:Mamarok|Mamarok]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=142991%2C143006%2C143013%2C143014%2C143143%2C143361%2C143379%2C143433%2C143438%2C143521%2C143560%2C143575%2C143582%2C143603&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 14
|-
| 2007-04.1 || [[User:Grundleborg|Grundleborg]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=143959%2C144144%2C143764%2C144010%2C144236%2C144516%2C144580%2C144028%2C143882%2C143893%2C143923&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 11
|-
| 2007-04.2 || [[User:Bram85|Bram85]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=144041%2C144053%2C144075%2C144080%2C144081%2C144137%2C144160%2C144310%2C144432%2C144538%2C144550%2C144826&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-05 || [[User:Mamarok|Mamarok]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-05-01&chfieldto=2007-05-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2007-06.1 || [[User:Ramblurr|Ramblurr]] || complete || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147351%2C147051%2C146617%2C146743%2C146750%2C147039%2C147239%2C147342%2C147146%2C147288%2C146899%2C146265%2C146382%2C146435%2C146492&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-06.2 || [[User:Ramblurr|Ramblurr]] ||complete || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=146520%2C146531%2C146649%2C146751%2C146970%2C147042%2C147045%2C147157%2C147219%2C147232%2C147273%2C147276%2C147277%2C147290%2C147343%2C147369&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-07.1 || [[User:Leuty|Leuty]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147692%2C147758%2C147847%2C148364%2C148369%2C147424%2C147507%2C147521%2C147547%2C147587%2C147658%2C147675&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-07.2 || [[User:Aides|Aides]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147710%2C147725%2C147755%2C147764%2C147796%2C147803%2C147890%2C147908%2C147913%2C148088%2C148108%2C148126&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-08.1 || [[User:Mamarok|Mamarok]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=148586%2C148625%2C148462%2C148664%2C148804%2C149014%2C148973%2C148423%2C148440%2C148473%2C148488%2C148665%2C148666&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-08.2 || [[User:Mamarok|Mamarok]] || working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=148675%2C148691%2C148692%2C148719%2C148726%2C148730%2C148740%2C148811%2C148829%2C148898%2C148923%2C149129%2C149306&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-09.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=149536%2C149574%2C149800%2C150184%2C149444%2C149593%2C149604%2C149662%2C149694%2C149734%2C149833%2C149885%2C149919&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-09.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=149959%2C149962%2C150002%2C150051%2C150059%2C150095%2C150096%2C150099%2C150146%2C150185%2C150196%2C150300%2C150308&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-10.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=150431%2C151390%2C151463%2C151466%2C150601%2C151235%2C151441%2C150403%2C150573%2C150587%2C150590%2C150642%2C150651%2C150754%2C150764%2C150795&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-10.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=150914%2C151051%2C151108%2C151151%2C151203%2C151234%2C151329%2C151366%2C151370%2C151410%2C151476%2C151479%2C151495%2C151497%2C151498%2C151502%2C151568&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-11.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=151748%2C152586%2C152821%2C153100%2C151856%2C151868%2C151879%2C151888%2C151964%2C151990%2C152001%2C152027%2C152033%2C152036%2C152063%2C152066&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-11.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=152193%2C152376%2C152426%2C152491%2C152642%2C152795%2C152814%2C152828%2C152870%2C152871%2C152896%2C152901%2C152906%2C153015%2C153030%2C153059&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-12.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=154495%2C153559%2C153243%2C153801%2C154641%2C154446%2C153364%2C153455%2C153523%2C153531%2C153592%2C153607%2C153755%2C153760%2C153887&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-12.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=154030%2C154160%2C154192%2C154255%2C154271%2C154291%2C154336%2C154406%2C154407%2C154731%2C154795%2C154867&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2008-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=155197%2C156622%2C156156%2C156758%2C156818%2C156821%2C156961%2C155036%2C155594%2C154994%2C155073%2C155088%2C155089%2C155102%2C155205%2C155396%2C155741&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2008-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=155813%2C155970%2C156005%2C156017%2C156052%2C156059%2C156086%2C156094%2C156110%2C156182%2C156455%2C156471%2C156516%2C156603%2C156664%2C156725%2C156973&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2008-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-02-01&chfieldto=2008-02-29&chfieldvalue=&newqueryname= Query] || 18
|-
| 2008-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-03-01&chfieldto=2008-03-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2008-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-04-01&chfieldto=2008-04-30&chfieldvalue=&newqueryname= Query] || 13
|-
| 2008-05.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-01&chfieldto=2008-05-10&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query] || 12
|-
| 2008-05.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-11&chfieldto=2008-05-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query] || 9
|-
| 2008-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-06-01&chfieldto=now&chfieldvalue=&newqueryname= Query] || 18
|-
|}

== 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/AmarokDay1/Bugs no longer present in 2.x}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Functionality not yet present in Amarok 2}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed}}

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

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs still present in Amarok 2}}

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs not related to today}}

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/High profile}}

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs no longer present in 2.x

2008-06-15T22:04:17Z

Krop: /* Bugs no longer present in 2.x */

===Bugs no longer present in 2.x===
If a bug is reported against a version of Amarok before 2.x, but the bug can no longer be reproduced in Amarok 2.x, then it should be listed here. Please '''do not''' close the bug. The Amarok developers would like to check each one before they are closed.

*{{Bug|103289}} eean said bug could be closed. [[User:Kage Jittai|Kage Jittai]]
** ack --[[User:Nightrose|Nightrose]] 09:32, 15 June 2008 (CEST)

*{{Bug|119169}} probably won't be fixed in 1.x, not relevant for 2.x. [[User:Mdhowe|Mdhowe]] 04:28, 15 June 2008 (CEST)

*{{Bug|118694}} fixed in 2.x, probably won't be fixed in 1.x [[User:Mdhowe|Mdhowe]] 04:54, 15 June 2008 (CEST)
** done --[[User:Nightrose|Nightrose]] 09:32, 15 June 2008 (CEST)

*{{Bug|126454}} fixed in 2.x though still present in 1.4.9.1 [[User:Mdhowe|Mdhowe]] 09:05, 15 June 2008 (CEST)
** done --[[User:Nightrose|Nightrose]] 09:32, 15 June 2008 (CEST)

*{{Bug|130501}} fixed in 2.x as well as in 1.4.9.1 [[User:Aides|Aides]] 11:46, 15 June 2008 (CEST)

*{{Bug|130503}} could not reproduce neither in 1.4 nor in 2 (advised fixed by Nightrose and grundleborg) [[User:Aides|Aides]] 11:56, 15 June 2008 (CEST)

*{{Bug|133519}} could not reproduce neither in 1.4 nor in 2 [[User:progger1986|progger1986]] 12:00, 15 June 2008 (CEST)

*{{Bug|133918}} could not reproduce neither in 1.4 nor in 2[[User:progger1986|progger1986]] 13:17, 15 June
2008 (CEST)

*{{Bug|130622}} fixed in 1.4 and 2 -- [[User:Aides|Aides]]

*{{Bug|134779}} Cannot reproduce neither in 1.4 nor in 2[[User:progger1986|progger1986]] 13:17, 15 June
2008 (CEST)

*{{Bug|130936}} Fixed by newer score scripts -- [[User:Aides|Aides]]

*{{Bug|137217}} - A certain popup menu doesn't show if using the Motif style. No longer reproducible in 1.4.9.1 and trunk. [[User:Lemma|Lemma]]

*{{Bug|138711}} - Not reproducible in 1.4.9.1 and trunk.

*{{Bug|131426}} fixed in 1.4, in 2 it works, but all the scripts are stopped, when restoring session -- [[User:Aides|Aides]]

*{{Bug|143882}} - Can't reproduce in a2, and probably fixed by major changes anyway. [[User:Grundleborg|Grundleborg]]

*{{Bug|134940}} <s>fixed in 1.4</s> turned out to be completely messed up, according to new follow-ups; can't test in 2.0 since it crashes ({{Bug|164144}}) -- [[User:Aides|Aides]]

*{{Bug|135080}} fixed -- [[User:Aides|Aides]]

*{{Bug|135089}} fixed and lacking feedback (auth by Nightrose) -- [[User:Aides|Aides]]

*{{Bug|143923}} - seems fixed in trunk. [[User:Grundleborg|Grundleborg]]

*{{Bug|135286}} fixed, as evidenced by lack of feedback -- [[User:Aides|Aides]]

*{{Bug|135337}} no longer valid, since no Postgres in 2.x -- [[User:Aides|Aides]]

*{{Bug|144516}} - seems to be fixed in trunk. [[User:Grundleborg|Grundleborg]]

*{{Bug|136419}} fixed as of 1.4.9.1 -- [[User:Aides|Aides]]

*{{Bug|136491}} unapplicable to svn-2.0 (no queue atm, and different UI), wontfix for 1.4 -- [[User:Aides|Aides]]

*{{bug|139803}} - TRUE and FALSE macros (EBN/krazy), already fixed. [[User:Lemma|Lemma]]

*{{bug|139963}} - Hard to explain but reproducible in 1.4.9.1. Fixed in trunk. [[User:Lemma|Lemma]]

*{{bug|147587}} - Cant be reproduced in 1.4.9.1 or 2.x. Nightly r820526. Fixed [[User:Leuty|Leuty]]

*{{bug|147658}} - If I see this correctly this is resolved in 1.4.9.1 and 2.x. Not the way the bugopener wanted it but doable. If I do not completly missunderstand him. Else WONTFIX [[User:Leuty|Leuty]]

*{{Bug|142364}} fixed in 1.4.9.1 and in 2.x -- [[User:Aides|Aides]]

*{{Bug|148364}} There's no option yet to sort the playlist in 2.x WONTFIX -- [[User:Leuty|Leuty]]

*{{Bug|148369}} I was told PgSQL is abandoned. WONTFIX -- [[User:Leuty|Leuty]]

*{{Bug|140134}} - can't reproduce in 1.4.9 / trunk [[User:Krop|Krop]]

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing users with particular setups

2008-06-15T21:31:36Z

Krop: /* Bugs needing users with particular setups */

===Bugs needing users with particular setups===
Bugs that require particular software or hardware that you don't have available should be listed here with a description of the non-standard requirement.

*{{Bug|118288}} Requires a proxy setup for port 80. [[User:Mdhowe|Mdhowe]]

*{{Bug|116220}} Needs KDE3 running, i really want to close this as INVALID or something :P [[User:Blauzahl|Blauzahl]]
**Ramblurr says that if this still exists, its a WONTFIX
**ack for WONTFIX --[[User:Nightrose|Nightrose]] 09:52, 15 June 2008 (CEST)

*{{Bug|119087}} Needs KDE3. [[User:Mdhowe|Mdhowe]]
** WONTFIX - even if it is still present we will not fix it --[[User:Nightrose|Nightrose]] 09:52, 15 June 2008 (CEST)

*{{Bug|114285}} Needs two screens [[User:Blauzahl|Blauzahl]]
** very old - likely fixed - WONTFIX anyway --[[User:Nightrose|Nightrose]] 09:52, 15 June 2008 (CEST)

*{{Bug|119026}} Requires a RTL language setup such as Arabic or Hebrew. [[User:Mdhowe|Mdhowe]]
** close due to lag of feedback - WONTFIX anyway --[[User:Nightrose|Nightrose]] 09:52, 15 June 2008 (CEST)
** I'll close it as a REMIND, who knows, maybe they'll give you a patch for 2 :D [[User:Blauzahl|Blauzahl]]

*{{Bug|112437}} Needs a proxy [[User:Kage Jittai|Kage Jittai]]

*{{Bug|137346}} crash Needs portable media device to check. [[User:Lemma|Lemma]]

*{{Bug|133609}} Can't get transcode working [[User:progger1986|progger1986]]

*{{Bug|133764}} Needs a DAAP share [[User:progger1986|progger1986]]

*{{Bug|130597}} Need some unplayable files, reporter mentions m4a -- [[User:Aides|Aides]]

*{{Bug|134544}} Needs almost none free disk space [[User:progger1986|progger1986]]

*{{Bug|134614}} Needs mDNSresponder and iTunes 7 [[User:progger1986|progger1986]]

*{{Bug|134718}} Needs cue sheets ans last.fm account [[User:progger1986|progger1986]]

*{{Bug|130929}} Needs media device -- [[User:Aides|Aides]]

*{{Bug|134416}} Needs DAAP client [[User:progger1986|progger1986]]

*{{bug|139030}} - Needs someone with a lot of mp3 files and PostgreSQL. [[User:Lemma|Lemma]]

*{{bug|138240}} - patch Needs someone with a portable media device, includes a patch. [[User:Lemma|Lemma]]

*{{bug|138743}} - crash Needs an mtp mp3 player. [[User:Lemma|Lemma]]

*{{bug|138850}} - Needs someone with an ipod to check. [[User:Lemma|Lemma]]

*{{bug|139218}} - Needs a Creative Vision M portable media device to check. [[User:Lemma|Lemma]]

*{{bug|139271}} - Needs a Creative Zen Vision portable media device to check. [[User:Lemma|Lemma]]

*{{bug|135466}} need an Ogg with multiple logical streams -- [[User:Aides|Aides]]

*{{bug|135665}} need an iPod -- [[User:Aides|Aides]]

*{{bug|135681}} need a media device. -- [[User:Aides|Aides]]

*{{bug|135938}} need a Samba share -- [[User:Aides|Aides]]

*{{bug|135823}} yet to be tested with amarok 2, mark as LATER (conf. by Nightrose) -- [[User:Aides|Aides]]

*{{bug|136153}} should be fixed with recent libgpod (as stated in last comment), but can't verify without iPod -- [[User:Aides|Aides]]

*{{bug|139805}} - Needs a portable media device. [[User:Lemma|Lemma]]

*{{bug|139836}} - Needs someone with Amarok/MySQL to recheck. [[User:Lemma|Lemma]]

*{{bug|140170}} - Needs someone with a MTP media device to check. [[User:Lemma|Lemma]]

*{{bug|140752}} - Needs a podcast with a missing file (possibly a webserver 404 error page). [[User:Lemma|Lemma]]

*{{bug|140752}} - Needs IPod-Nano. Most likely resolved in 1.4.9.1 [[User:Leuty|Leuty]]

*{{bug|142680}} need media with cue-sheet -- [[User:Aides|Aides]]

*{{bug|143421}} need someone to test podcast issues -- [[User:Aides|Aides]]

*{{bug|143485}} another cue-sheet related bug -- [[User:Aides|Aides]]

*{{Bug|139538}} - Need a Sandisk player [[User:Krop|Krop]]
*{{Bug|140270}} - Need a MTP compatible device [[User:Krop|Krop]]
*{{Bug|139772}} - Need someone running KDE3 and Amarok 1.4 (global shortcuts have no effects in KDE4) [[User:Krop|Krop]]

Contribute/Bugsquad/BugDays/AmarokDay1

2008-06-15T12:20:15Z

Krop: /* Division of Labour */

{{warning|Instead of editing the whole wiki page, please enable editing by section in your preferences and click the Edit link next to each section header to edit content. Like this we'll mostly prevent conflicts if several people edit the page at once.}}

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

'''The goal of this bug-day is to check for bugs that are fixed, duplicates, are not going to be fixed in Amarok 1.4.x or are already fixed/implemented in Amarok 2. This will enable the Amarok developers to deal with bugs more easily, and so have more time left to actually code on Amarok 2.''' When you have closed or commented on a bug, please list it in the appropriate section below, so that a second triager can see if they can confirm it.

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. Amarok team members will be both there and in #amarok to answer your questions. If none of them are around please note the bug in the list below so they can be dealt with later.

You should be working with Amarok 1.4.9.1 and Amarok 2 for testing these bugs. To make it easier for you to obtain Amarok 2 we provide nightly builds of it. So far Packages for Kubuntu and openSUSE are available. For more information check out the [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Neon wiki page]. For openSUSE packages please also ask in #amarok.neon. Amarok 1.4.9.1 should be available in your distro repositories.

Please mention which version and distro you are working with if necessary. (For Neon mention the build date from the Amarok about dialog. It is in the middle of the first tab.)

===Unclear===
If a bug report has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a bug is severe we want to know about it.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to the version specified in the other fields of the original bug report.

===What to close?===
Amarok 1 and Amarok 2 are very different and a lot of bugs of 1 don't apply to 2 and vice-versa. Amarok 1.4.x is in bugfix-only mode. This means we are only going to fix bugs where the risk of regression is minimal. No new features are going to be implemented in Amarok 1.4.x. So please be aggressive with closing bugs that are not going to get fixed in 1.4.x anyway. No need to keep them around. For feature requests please check Amarok 2. If it is implemented there then close the bug, otherwise please speak with the Amarok team to see if they plan to implement it. If they don't, then close it as WONTFIX.

'''REMEMBER: If you think a bug should be closed, list it in the appropriate section below BEFORE closing it, so another triager can check it. Before a bug can be closed it must be checked by TWO triagers. Not just you!'''

===How to comment===
Please add a note like "comment from KDE bugsquad member" at the top of your comments so Amarok developers know who you are. Always leave a comment explaining why you change something. If you spoke with a member of the Amarok team please mention who. If you close a bug report for 1.4.x you might want to consider using one of the following stock replies:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.''

And if a feature request has to be moved to Amarok 2:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your feature request can not be implemented in Amarok 1, as Amarok developers do not have the resources for it and risk of regression would be too high. I am therefore moving your request to Amarok 2. I cannot make any guarantee as to whether is will get implemented there or not though. Thank you for your report.''

And if something has already been implemented in Amarok 2:

''This feature is already implemented in Amarok 2. However, Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2, so your feature request can not be implemented in Amarok 1 as the risk of regression would be too high. I am therefore closing this report. Thank you for your report and have fun with Amarok.''

===Double Check!===
'''Please list and sort bugs below to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.''' Things which are not closes can be changed as you go.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Always add your comments on bugzilla as well as the wiki for a more complete feedback by users and developers.

==Details==

Please get a bugzilla account (bugs.kde.org) and a techbase.kde.org account. Then "sign in" below, and select a period 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, as we will cross-check everybody else's bugs. This will help to reduce the number of incorrect actions taken on bugs.'''

==How to get a Backtrace with Amarok==

Simple gdb howto:

# start Amarok
$ amarok

#switch terminals and get amarok's pid
$ pgrep amarok

#start gdb
gdb

#attach to amarok's process
gdb> attach <pid>

#let it load debugging symbols, then type continue
(gdb) continue

#Do what you want to amarok to make it crash. Once it has crashed type
(gdb) bt

==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.)
{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Ramblurr|Ramblurr]] || svn trunk latest ||
|-
|[[User:Kage Jittai|Kage_Jittai]] || kdelibs r818475 a2 r820610 ||
|-
|[[User:Blauzahl|Blauzahl]] || kdelibs r820643 a2 r820651 & debian sid 1.4.9.1 ||
|-
|[[User:Mdhowe|Artisian]] (also Mdhowe) || Ubuntu Nightly r820526 & Ubunutu 1.4.9.1 ||
|-
|[[User:Aides|Aides]] || kdelibs r820524 a2 r820697 & Gentoo 1.4.9.1 ||
|-
||[[User:lemma|lemma]] || kdelibs r820510, a2 820602, debian sid 1.4.9.1 ||
|-
||[[User:annma|annma]] || svn trunk latest Revision: 820699||
|-
||[[User:progger1986|progger1986]] || kdelibs r812186 & 1.4.9.1||
|-
||[[User:Krop|Krop]] || kdelibs r820750, a2 820750, debian sid 1.4.9.1 ||
|}
{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a month that is not already taken from the list below and then query bugs.kde.org for all bugs in that month. Please put your irc nickname in the table below next to the month so we don't duplicate months.

The bugzilla query to use for this triage day is TBD. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month/time period !! IRC Nickname !! Status !! Query !! Number of Bugs
|-
| 2005-03 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-03-01&chfieldto=2005-03-31&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-04 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-04-01&chfieldto=2005-04-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-06 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-06-01&chfieldto=2005-06-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-09 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-09-01&chfieldto=2005-09-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-10 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-10-01&chfieldto=2005-10-31&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-11 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-11-01&chfieldto=2005-11-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-12 || [[User:Mdhowe|Artisian]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-12-01&chfieldto=2005-12-31&chfieldvalue=&newqueryname= Query] || 6
|-
| 2006-02 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query] || 2
|-
| 2006-03 || [[User:Blauzahl|Blauzahl]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query] || 7
|-
| 2006-04 || [[User:Mdhowe|Artisian]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query] || 6
|-
| 2006-05 || [[User:Kage Jittai|Kage Jittai]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query] || 8
|-
| 2006-06 || [[User:Kage Jittai|Kage Jittai]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query] || 12
|-
| 2006-07 || [[User:Aides|Aides]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query] || 13
|-
| 2006-08 || [[User:Annma|Annma]]|| Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query] || 13
|-
| 2006-09 || [[User:progger1986|progger1986]]|| Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query] || 17
|-
| 2006-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2006-11 || [[User:Lemma|Lemma]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query] || 14
|-
| 2006-12 || [[User:Lemma|Lemma]] || working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query] || 16
|-
| 2007-01.1 || [[User:Krop|Krop]] || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=139722%2C140134%2C140078%2C139756%2C140020%2C140270%2C139610%2C139897%2C139497%2C139538%2C139549%2C139647%2C139716%2C139763%2C139764%2C139772%2C&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=139803%2C139805%2C139836%2C139889%2C139963%2C140001%2C140080%2C140170%2C140338%2C140357%2C140428%2C140461%2C140462%2C140618%2C140752%2C140757%2C140795&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-02.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=141780%2C142278%2C141935%2C142111%2C141578%2C141404%2C142282%2C141049%2C141103%2C141147%2C141276%2C141291%2C141323%2C141412%2C141426%2C141431&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-02.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=141445%2C141466%2C141571%2C141581%2C141634%2C141652%2C141736%2C141777%2C141856%2C141894%2C141930%2C142099%2C142114%2C142156%2C142174%2C142192%2C142230&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-03.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=142757%2C142712%2C142899%2C143420%2C143485%2C143624%2C143163%2C142680%2C143421%2C142364%2C142433%2C142437%2C142797%2C142804%2C142805%2C&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-03.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=142991%2C143006%2C143013%2C143014%2C143143%2C143361%2C143379%2C143433%2C143438%2C143521%2C143560%2C143575%2C143582%2C143603&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 14
|-
| 2007-04.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=143959%2C144144%2C143764%2C144010%2C144236%2C144516%2C144580%2C144028%2C143882%2C143893%2C143923&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 11
|-
| 2007-04.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=144041%2C144053%2C144075%2C144080%2C144081%2C144137%2C144160%2C144310%2C144432%2C144538%2C144550%2C144826&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-05-01&chfieldto=2007-05-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2007-06.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147351%2C147051%2C146617%2C146743%2C146750%2C147039%2C147239%2C147342%2C147146%2C147288%2C146899%2C146265%2C146382%2C146435%2C146492&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-06.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=146520%2C146531%2C146649%2C146751%2C146970%2C147042%2C147045%2C147157%2C147219%2C147232%2C147273%2C147276%2C147277%2C147290%2C147343%2C147369&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-07.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147692%2C147758%2C147847%2C148364%2C148369%2C147424%2C147507%2C147521%2C147547%2C147587%2C147658%2C147675&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-07.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147710%2C147725%2C147755%2C147764%2C147796%2C147803%2C147890%2C147908%2C147913%2C148088%2C148108%2C148126&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-08.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=148586%2C148625%2C148462%2C148664%2C148804%2C149014%2C148973%2C148423%2C148440%2C148473%2C148488%2C148665%2C148666&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-08.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=148675%2C148691%2C148692%2C148719%2C148726%2C148730%2C148740%2C148811%2C148829%2C148898%2C148923%2C149129%2C149306&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-09.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=149536%2C149574%2C149800%2C150184%2C149444%2C149593%2C149604%2C149662%2C149694%2C149734%2C149833%2C149885%2C149919&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-09.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=149959%2C149962%2C150002%2C150051%2C150059%2C150095%2C150096%2C150099%2C150146%2C150185%2C150196%2C150300%2C150308&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-10.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=150431%2C151390%2C151463%2C151466%2C150601%2C151235%2C151441%2C150403%2C150573%2C150587%2C150590%2C150642%2C150651%2C150754%2C150764%2C150795&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-10.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=150914%2C151051%2C151108%2C151151%2C151203%2C151234%2C151329%2C151366%2C151370%2C151410%2C151476%2C151479%2C151495%2C151497%2C151498%2C151502%2C151568&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-11.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=151748%2C152586%2C152821%2C153100%2C151856%2C151868%2C151879%2C151888%2C151964%2C151990%2C152001%2C152027%2C152033%2C152036%2C152063%2C152066&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-11.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=152193%2C152376%2C152426%2C152491%2C152642%2C152795%2C152814%2C152828%2C152870%2C152871%2C152896%2C152901%2C152906%2C153015%2C153030%2C153059&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-12.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=154495%2C153559%2C153243%2C153801%2C154641%2C154446%2C153364%2C153455%2C153523%2C153531%2C153592%2C153607%2C153755%2C153760%2C153887&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-12.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=154030%2C154160%2C154192%2C154255%2C154271%2C154291%2C154336%2C154406%2C154407%2C154731%2C154795%2C154867&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2008-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=155197%2C156622%2C156156%2C156758%2C156818%2C156821%2C156961%2C155036%2C155594%2C154994%2C155073%2C155088%2C155089%2C155102%2C155205%2C155396%2C155741&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2008-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=155813%2C155970%2C156005%2C156017%2C156052%2C156059%2C156086%2C156094%2C156110%2C156182%2C156455%2C156471%2C156516%2C156603%2C156664%2C156725%2C156973&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2008-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-02-01&chfieldto=2008-02-29&chfieldvalue=&newqueryname= Query] || 18
|-
| 2008-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-03-01&chfieldto=2008-03-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2008-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-04-01&chfieldto=2008-04-30&chfieldvalue=&newqueryname= Query] || 13
|-
| 2008-05.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-01&chfieldto=2008-05-10&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query] || 12
|-
| 2008-05.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-11&chfieldto=2008-05-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query] || 9
|-
| 2008-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-06-01&chfieldto=now&chfieldvalue=&newqueryname= Query] || 18
|-
|}

== 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/AmarokDay1/Bugs no longer present in 2.x}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Functionality not yet present in Amarok 2}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed}}

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

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs still present in Amarok 2}}

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs not related to today}}

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/High profile}}

Contribute/Bugsquad/BugDays/AmarokDay1

2008-06-15T12:19:42Z

Krop: /* Sign-in */

{{warning|Instead of editing the whole wiki page, please enable editing by section in your preferences and click the Edit link next to each section header to edit content. Like this we'll mostly prevent conflicts if several people edit the page at once.}}

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

'''The goal of this bug-day is to check for bugs that are fixed, duplicates, are not going to be fixed in Amarok 1.4.x or are already fixed/implemented in Amarok 2. This will enable the Amarok developers to deal with bugs more easily, and so have more time left to actually code on Amarok 2.''' When you have closed or commented on a bug, please list it in the appropriate section below, so that a second triager can see if they can confirm it.

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. Amarok team members will be both there and in #amarok to answer your questions. If none of them are around please note the bug in the list below so they can be dealt with later.

You should be working with Amarok 1.4.9.1 and Amarok 2 for testing these bugs. To make it easier for you to obtain Amarok 2 we provide nightly builds of it. So far Packages for Kubuntu and openSUSE are available. For more information check out the [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Neon wiki page]. For openSUSE packages please also ask in #amarok.neon. Amarok 1.4.9.1 should be available in your distro repositories.

Please mention which version and distro you are working with if necessary. (For Neon mention the build date from the Amarok about dialog. It is in the middle of the first tab.)

===Unclear===
If a bug report has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a bug is severe we want to know about it.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to the version specified in the other fields of the original bug report.

===What to close?===
Amarok 1 and Amarok 2 are very different and a lot of bugs of 1 don't apply to 2 and vice-versa. Amarok 1.4.x is in bugfix-only mode. This means we are only going to fix bugs where the risk of regression is minimal. No new features are going to be implemented in Amarok 1.4.x. So please be aggressive with closing bugs that are not going to get fixed in 1.4.x anyway. No need to keep them around. For feature requests please check Amarok 2. If it is implemented there then close the bug, otherwise please speak with the Amarok team to see if they plan to implement it. If they don't, then close it as WONTFIX.

'''REMEMBER: If you think a bug should be closed, list it in the appropriate section below BEFORE closing it, so another triager can check it. Before a bug can be closed it must be checked by TWO triagers. Not just you!'''

===How to comment===
Please add a note like "comment from KDE bugsquad member" at the top of your comments so Amarok developers know who you are. Always leave a comment explaining why you change something. If you spoke with a member of the Amarok team please mention who. If you close a bug report for 1.4.x you might want to consider using one of the following stock replies:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.''

And if a feature request has to be moved to Amarok 2:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your feature request can not be implemented in Amarok 1, as Amarok developers do not have the resources for it and risk of regression would be too high. I am therefore moving your request to Amarok 2. I cannot make any guarantee as to whether is will get implemented there or not though. Thank you for your report.''

And if something has already been implemented in Amarok 2:

''This feature is already implemented in Amarok 2. However, Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2, so your feature request can not be implemented in Amarok 1 as the risk of regression would be too high. I am therefore closing this report. Thank you for your report and have fun with Amarok.''

===Double Check!===
'''Please list and sort bugs below to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.''' Things which are not closes can be changed as you go.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Always add your comments on bugzilla as well as the wiki for a more complete feedback by users and developers.

==Details==

Please get a bugzilla account (bugs.kde.org) and a techbase.kde.org account. Then "sign in" below, and select a period 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, as we will cross-check everybody else's bugs. This will help to reduce the number of incorrect actions taken on bugs.'''

==How to get a Backtrace with Amarok==

Simple gdb howto:

# start Amarok
$ amarok

#switch terminals and get amarok's pid
$ pgrep amarok

#start gdb
gdb

#attach to amarok's process
gdb> attach <pid>

#let it load debugging symbols, then type continue
(gdb) continue

#Do what you want to amarok to make it crash. Once it has crashed type
(gdb) bt

==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.)
{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Ramblurr|Ramblurr]] || svn trunk latest ||
|-
|[[User:Kage Jittai|Kage_Jittai]] || kdelibs r818475 a2 r820610 ||
|-
|[[User:Blauzahl|Blauzahl]] || kdelibs r820643 a2 r820651 & debian sid 1.4.9.1 ||
|-
|[[User:Mdhowe|Artisian]] (also Mdhowe) || Ubuntu Nightly r820526 & Ubunutu 1.4.9.1 ||
|-
|[[User:Aides|Aides]] || kdelibs r820524 a2 r820697 & Gentoo 1.4.9.1 ||
|-
||[[User:lemma|lemma]] || kdelibs r820510, a2 820602, debian sid 1.4.9.1 ||
|-
||[[User:annma|annma]] || svn trunk latest Revision: 820699||
|-
||[[User:progger1986|progger1986]] || kdelibs r812186 & 1.4.9.1||
|-
||[[User:Krop|Krop]] || kdelibs r820750, a2 820750, debian sid 1.4.9.1 ||
|}
{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a month that is not already taken from the list below and then query bugs.kde.org for all bugs in that month. Please put your irc nickname in the table below next to the month so we don't duplicate months.

The bugzilla query to use for this triage day is TBD. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month/time period !! IRC Nickname !! Status !! Query !! Number of Bugs
|-
| 2005-03 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-03-01&chfieldto=2005-03-31&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-04 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-04-01&chfieldto=2005-04-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-06 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-06-01&chfieldto=2005-06-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-09 || [[User:Kage Jittai|Kage_Jittai]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-09-01&chfieldto=2005-09-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-10 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-10-01&chfieldto=2005-10-31&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-11 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-11-01&chfieldto=2005-11-30&chfieldvalue=&newqueryname= Query] || 1
|-
| 2005-12 || [[User:Mdhowe|Artisian]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-12-01&chfieldto=2005-12-31&chfieldvalue=&newqueryname= Query] || 6
|-
| 2006-02 || [[User:Blauzahl|Blauzahl]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query] || 2
|-
| 2006-03 || [[User:Blauzahl|Blauzahl]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query] || 7
|-
| 2006-04 || [[User:Mdhowe|Artisian]] || Done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query] || 6
|-
| 2006-05 || [[User:Kage Jittai|Kage Jittai]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query] || 8
|-
| 2006-06 || [[User:Kage Jittai|Kage Jittai]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query] || 12
|-
| 2006-07 || [[User:Aides|Aides]] || Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query] || 13
|-
| 2006-08 || [[User:Annma|Annma]]|| Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query] || 13
|-
| 2006-09 || [[User:progger1986|progger1986]]|| Working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query] || 17
|-
| 2006-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2006-11 || [[User:Lemma|Lemma]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query] || 14
|-
| 2006-12 || [[User:Lemma|Lemma]] || working || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query] || 16
|-
| 2007-01.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=139722%2C140134%2C140078%2C139756%2C140020%2C140270%2C139610%2C139897%2C139497%2C139538%2C139549%2C139647%2C139716%2C139763%2C139764%2C139772%2C&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=139803%2C139805%2C139836%2C139889%2C139963%2C140001%2C140080%2C140170%2C140338%2C140357%2C140428%2C140461%2C140462%2C140618%2C140752%2C140757%2C140795&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-02.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=141780%2C142278%2C141935%2C142111%2C141578%2C141404%2C142282%2C141049%2C141103%2C141147%2C141276%2C141291%2C141323%2C141412%2C141426%2C141431&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-02.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=141445%2C141466%2C141571%2C141581%2C141634%2C141652%2C141736%2C141777%2C141856%2C141894%2C141930%2C142099%2C142114%2C142156%2C142174%2C142192%2C142230&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-03.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=142757%2C142712%2C142899%2C143420%2C143485%2C143624%2C143163%2C142680%2C143421%2C142364%2C142433%2C142437%2C142797%2C142804%2C142805%2C&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-03.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=142991%2C143006%2C143013%2C143014%2C143143%2C143361%2C143379%2C143433%2C143438%2C143521%2C143560%2C143575%2C143582%2C143603&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 14
|-
| 2007-04.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=143959%2C144144%2C143764%2C144010%2C144236%2C144516%2C144580%2C144028%2C143882%2C143893%2C143923&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 11
|-
| 2007-04.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=144041%2C144053%2C144075%2C144080%2C144081%2C144137%2C144160%2C144310%2C144432%2C144538%2C144550%2C144826&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-05-01&chfieldto=2007-05-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2007-06.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147351%2C147051%2C146617%2C146743%2C146750%2C147039%2C147239%2C147342%2C147146%2C147288%2C146899%2C146265%2C146382%2C146435%2C146492&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-06.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=146520%2C146531%2C146649%2C146751%2C146970%2C147042%2C147045%2C147157%2C147219%2C147232%2C147273%2C147276%2C147277%2C147290%2C147343%2C147369&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-07.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147692%2C147758%2C147847%2C148364%2C148369%2C147424%2C147507%2C147521%2C147547%2C147587%2C147658%2C147675&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-07.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=147710%2C147725%2C147755%2C147764%2C147796%2C147803%2C147890%2C147908%2C147913%2C148088%2C148108%2C148126&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2007-08.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=148586%2C148625%2C148462%2C148664%2C148804%2C149014%2C148973%2C148423%2C148440%2C148473%2C148488%2C148665%2C148666&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-08.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=148675%2C148691%2C148692%2C148719%2C148726%2C148730%2C148740%2C148811%2C148829%2C148898%2C148923%2C149129%2C149306&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-09.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=149536%2C149574%2C149800%2C150184%2C149444%2C149593%2C149604%2C149662%2C149694%2C149734%2C149833%2C149885%2C149919&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-09.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=149959%2C149962%2C150002%2C150051%2C150059%2C150095%2C150096%2C150099%2C150146%2C150185%2C150196%2C150300%2C150308&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 13
|-
| 2007-10.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=150431%2C151390%2C151463%2C151466%2C150601%2C151235%2C151441%2C150403%2C150573%2C150587%2C150590%2C150642%2C150651%2C150754%2C150764%2C150795&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-10.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=150914%2C151051%2C151108%2C151151%2C151203%2C151234%2C151329%2C151366%2C151370%2C151410%2C151476%2C151479%2C151495%2C151497%2C151498%2C151502%2C151568&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2007-11.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=151748%2C152586%2C152821%2C153100%2C151856%2C151868%2C151879%2C151888%2C151964%2C151990%2C152001%2C152027%2C152033%2C152036%2C152063%2C152066&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-11.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=152193%2C152376%2C152426%2C152491%2C152642%2C152795%2C152814%2C152828%2C152870%2C152871%2C152896%2C152901%2C152906%2C153015%2C153030%2C153059&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 16
|-
| 2007-12.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=154495%2C153559%2C153243%2C153801%2C154641%2C154446%2C153364%2C153455%2C153523%2C153531%2C153592%2C153607%2C153755%2C153760%2C153887&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 15
|-
| 2007-12.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=154030%2C154160%2C154192%2C154255%2C154271%2C154291%2C154336%2C154406%2C154407%2C154731%2C154795%2C154867&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 12
|-
| 2008-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=155197%2C156622%2C156156%2C156758%2C156818%2C156821%2C156961%2C155036%2C155594%2C154994%2C155073%2C155088%2C155089%2C155102%2C155205%2C155396%2C155741&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2008-01.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=155813%2C155970%2C156005%2C156017%2C156052%2C156059%2C156086%2C156094%2C156110%2C156182%2C156455%2C156471%2C156516%2C156603%2C156664%2C156725%2C156973&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname= Query] || 17
|-
| 2008-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-02-01&chfieldto=2008-02-29&chfieldvalue=&newqueryname= Query] || 18
|-
| 2008-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-03-01&chfieldto=2008-03-31&chfieldvalue=&newqueryname= Query] || 19
|-
| 2008-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-04-01&chfieldto=2008-04-30&chfieldvalue=&newqueryname= Query] || 13
|-
| 2008-05.1 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-01&chfieldto=2008-05-10&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query] || 12
|-
| 2008-05.2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-11&chfieldto=2008-05-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query] || 9
|-
| 2008-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-06-01&chfieldto=now&chfieldvalue=&newqueryname= Query] || 18
|-
|}

== 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/AmarokDay1/Bugs no longer present in 2.x}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Functionality not yet present in Amarok 2}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed}}

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

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs still present in Amarok 2}}

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs not related to today}}

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/High profile}}

Contribute/Bugsquad/BugDays/AmarokDay1

2008-06-14T09:02:21Z

Krop: /* Division of Labour */

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

'''The goal of this bug-day is to check for bugs that are fixed, duplicates, are not going to be fixed in Amarok 1.4.x or are already fixed/implemented in Amarok 2. This will enable the Amarok developers to deal with bugs more easily, and so have more time left to actually code on Amarok 2.''' When you have closed or commented on a bug, please list it in the appropriate section below, so that a second triager can see if they can confirm it.

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. Amarok team members will be both there and in #amarok to answer your questions. If none of them are around please note the bug in the list below so they can be dealt with later.

You should be working with Amarok 1.4.9.1 and Amarok 2 for testing these bugs. To make it easier for you to obtain Amarok 2 we provide nightly builds of it. So far Packages for Kubuntu and openSUSE are available. For more information check out the [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Neon wiki page]. For openSUSE packages please also ask in #amarok.neon. Amarok 1.4.9.1 should be available in your distro repositories.

Please mention which version and distro you are working with if necessary. (For Neon mention the build date from the Amarok about dialog. It is in the middle of the first tab.)

===Unclear===
If a bug report has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a bug is severe we want to know about it.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to the version specified in the other fields of the original bug report.

===What to close?===
Amarok 1 and Amarok 2 are very different and a lot of bugs of 1 don't apply to 2 and vice-versa. Amarok 1.4.x is in bugfix-only mode. This means we are only going to fix bugs where the risk of regression is minimal. No new features are going to be implemented in Amarok 1.4.x. So please be aggressive with closing bugs that are not going to get fixed in 1.4.x anyway. No need to keep them around. For feature requests please check Amarok 2. If it is implemented there then close the bug, otherwise please speak with the Amarok team to see if they plan to implement it. If they don't, then close it as WONTFIX.

'''REMEMBER: If you think a bug should be closed, list it in the appropriate section below BEFORE closing it, so another triager can check it. Before a bug can be closed it must be checked by TWO triagers. Not just you!'''

===How to comment===
Please add a note like "comment from KDE bugsquad member" at the top of your comments so Amarok developers know who you are. Always leave a comment explaining why you change something. If you spoke with a member of the Amarok team please mention who. If you close a bug report for 1.4.x you might want to consider using one of the following stock replies:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.''

And if a feature request has to be moved to Amarok 2:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your feature request can not be implemented in Amarok 1, as Amarok developers do not have the resources for it and risk of regression would be too high. I am therefore moving your request to Amarok 2. I cannot make any guarantee as to whether is will get implemented there or not though. Thank you for your report.''

And if something has already been implemented in Amarok 2:

''This feature is already implemented in Amarok 2. However, Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2, so your feature request can not be implemented in Amarok 1 as the risk of regression would be too high. I am therefore closing this report. Thank you for your report and have fun with Amarok.''

===Double Check!===
'''Please list and sort bugs below to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.''' Things which are not closes can be changed as you go.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Always add your comments on bugzilla as well as the wiki for a more complete feedback by users and developers.

==Details==

Please get a bugzilla account (bugs.kde.org) and a techbase.kde.org account. Then "sign in" below, and select a period 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, as we will cross-check everybody else's bugs. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)
{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Ramblurr|Ramblurr]] || svn trunk latest ||
|}
{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a month that is not already taken from the list below and then query bugs.kde.org for all bugs in that month. Please put your irc nickname in the table below next to the month so we don't duplicate months.

The bugzilla query to use for this triage day is TBD. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month/time period !! IRC Nickname !! Status !! Query
|-
| 2005-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-01-01&chfieldto=2005-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-02-01&chfieldto=2005-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2005-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-03-01&chfieldto=2005-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-04-01&chfieldto=2005-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-05-01&chfieldto=2005-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-06-01&chfieldto=2005-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-07-01&chfieldto=2005-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-08-01&chfieldto=2005-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-09-01&chfieldto=2005-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-10-01&chfieldto=2005-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-11-01&chfieldto=2005-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-12-01&chfieldto=2005-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-01-01&chfieldto=2006-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2006-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2007-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-05-01&chfieldto=2007-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-02-01&chfieldto=2008-02-29&chfieldvalue=&newqueryname= Query]
|-
| 2008-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-03-01&chfieldto=2008-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-04-01&chfieldto=2008-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2008-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-01&chfieldto=2008-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-06-01&chfieldto=now&chfieldvalue=&newqueryname= Query]
|-
|}

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to '''enable section editing''' by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs no longer present in 2.x}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed}}

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

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

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

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs not related to today}}

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/High profile}}

Contribute/Bugsquad/BugDays/AmarokDay1

2008-06-14T09:00:50Z

Krop: /* Division of Labour */

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

'''The goal of this bug-day is to check for bugs that are fixed, duplicates, are not going to be fixed in Amarok 1.4.x or are already fixed/implemented in Amarok 2. This will enable the Amarok developers to deal with bugs more easily, and so have more time left to actually code on Amarok 2.''' When you have closed or commented on a bug, please list it in the appropriate section below, so that a second triager can see if they can confirm it.

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. Amarok team members will be both there and in #amarok to answer your questions. If none of them are around please note the bug in the list below so they can be dealt with later.

You should be working with Amarok 1.4.9.1 and Amarok 2 for testing these bugs. To make it easier for you to obtain Amarok 2 we provide nightly builds of it. So far Packages for Kubuntu and openSUSE are available. For more information check out the [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Neon wiki page]. For openSUSE packages please also ask in #amarok.neon. Amarok 1.4.9.1 should be available in your distro repositories.

Please mention which version and distro you are working with if necessary. (For Neon mention the build date from the Amarok about dialog. It is in the middle of the first tab.)

===Unclear===
If a bug report has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a bug is severe we want to know about it.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to the version specified in the other fields of the original bug report.

===What to close?===
Amarok 1 and Amarok 2 are very different and a lot of bugs of 1 don't apply to 2 and vice-versa. Amarok 1.4.x is in bugfix-only mode. This means we are only going to fix bugs where the risk of regression is minimal. No new features are going to be implemented in Amarok 1.4.x. So please be aggressive with closing bugs that are not going to get fixed in 1.4.x anyway. No need to keep them around. For feature requests please check Amarok 2. If it is implemented there then close the bug, otherwise please speak with the Amarok team to see if they plan to implement it. If they don't, then close it as WONTFIX.

'''REMEMBER: If you think a bug should be closed, list it in the appropriate section below BEFORE closing it, so another triager can check it. Before a bug can be closed it must be checked by TWO triagers. Not just you!'''

===How to comment===
Please add a note like "comment from KDE bugsquad member" at the top of your comments so Amarok developers know who you are. Always leave a comment explaining why you change something. If you spoke with a member of the Amarok team please mention who. If you close a bug report for 1.4.x you might want to consider using one of the following stock replies:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.''

And if a feature request has to be moved to Amarok 2:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your feature request can not be implemented in Amarok 1, as Amarok developers do not have the resources for it and risk of regression would be too high. I am therefore moving your request to Amarok 2. I cannot make any guarantee as to whether is will get implemented there or not though. Thank you for your report.''

And if something has already been implemented in Amarok 2:

''This feature is already implemented in Amarok 2. However, Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2, so your feature request can not be implemented in Amarok 1 as the risk of regression would be too high. I am therefore closing this report. Thank you for your report and have fun with Amarok.''

===Double Check!===
'''Please list and sort bugs below to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.''' Things which are not closes can be changed as you go.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Always add your comments on bugzilla as well as the wiki for a more complete feedback by users and developers.

==Details==

Please get a bugzilla account (bugs.kde.org) and a techbase.kde.org account. Then "sign in" below, and select a period 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, as we will cross-check everybody else's bugs. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)
{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Ramblurr|Ramblurr]] || svn trunk latest ||
|}
{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a month that is not already taken from the list below and then query bugs.kde.org for all bugs in that month. Please put your irc nickname in the table below next to the month so we don't duplicate months.

The bugzilla query to use for this triage day is TBD. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month/time period !! IRC Nickname !! Status !! Query
|-
| 2005-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-01-01&chfieldto=2005-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-02-01&chfieldto=2005-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2005-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-03-01&chfieldto=2005-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-04-01&chfieldto=2005-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-05-01&chfieldto=2005-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-06-01&chfieldto=2005-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-07-01&chfieldto=2005-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-08-01&chfieldto=2005-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-09-01&chfieldto=2005-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-10-01&chfieldto=2005-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-11-01&chfieldto=2005-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-12-01&chfieldto=2005-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-01-01&chfieldto=2006-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2006-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2007-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-05-01&chfieldto=2007-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-01-01&chfieldto=2006-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2006-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-02-01&chfieldto=2008-02-29&chfieldvalue=&newqueryname= Query]
|-
| 2008-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-03-01&chfieldto=2008-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-04-01&chfieldto=2008-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2008-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-01&chfieldto=2008-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-06-01&chfieldto=now&chfieldvalue=&newqueryname= Query]
|-
|}

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to '''enable section editing''' by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs no longer present in 2.x}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed}}

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

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

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

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs not related to today}}

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/High profile}}

Contribute/Bugsquad/BugDays/AmarokDay1

2008-06-14T08:59:29Z

Krop: /* Division of Labour */

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

'''The goal of this bug-day is to check for bugs that are fixed, duplicates, are not going to be fixed in Amarok 1.4.x or are already fixed/implemented in Amarok 2. This will enable the Amarok developers to deal with bugs more easily, and so have more time left to actually code on Amarok 2.''' When you have closed or commented on a bug, please list it in the appropriate section below, so that a second triager can see if they can confirm it.

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. Amarok team members will be both there and in #amarok to answer your questions. If none of them are around please note the bug in the list below so they can be dealt with later.

You should be working with Amarok 1.4.9.1 and Amarok 2 for testing these bugs. To make it easier for you to obtain Amarok 2 we provide nightly builds of it. So far Packages for Kubuntu and openSUSE are available. For more information check out the [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Neon wiki page]. For openSUSE packages please also ask in #amarok.neon. Amarok 1.4.9.1 should be available in your distro repositories.

Please mention which version and distro you are working with if necessary. (For Neon mention the build date from the Amarok about dialog. It is in the middle of the first tab.)

===Unclear===
If a bug report has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a bug is severe we want to know about it.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to the version specified in the other fields of the original bug report.

===What to close?===
Amarok 1 and Amarok 2 are very different and a lot of bugs of 1 don't apply to 2 and vice-versa. Amarok 1.4.x is in bugfix-only mode. This means we are only going to fix bugs where the risk of regression is minimal. No new features are going to be implemented in Amarok 1.4.x. So please be aggressive with closing bugs that are not going to get fixed in 1.4.x anyway. No need to keep them around. For feature requests please check Amarok 2. If it is implemented there then close the bug, otherwise please speak with the Amarok team to see if they plan to implement it. If they don't, then close it as WONTFIX.

'''REMEMBER: If you think a bug should be closed, list it in the appropriate section below BEFORE closing it, so another triager can check it. Before a bug can be closed it must be checked by TWO triagers. Not just you!'''

===How to comment===
Please add a note like "comment from KDE bugsquad member" at the top of your comments so Amarok developers know who you are. Always leave a comment explaining why you change something. If you spoke with a member of the Amarok team please mention who. If you close a bug report for 1.4.x you might want to consider using one of the following stock replies:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.''

And if a feature request has to be moved to Amarok 2:

''Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your feature request can not be implemented in Amarok 1, as Amarok developers do not have the resources for it and risk of regression would be too high. I am therefore moving your request to Amarok 2. I cannot make any guarantee as to whether is will get implemented there or not though. Thank you for your report.''

And if something has already been implemented in Amarok 2:

''This feature is already implemented in Amarok 2. However, Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2, so your feature request can not be implemented in Amarok 1 as the risk of regression would be too high. I am therefore closing this report. Thank you for your report and have fun with Amarok.''

===Double Check!===
'''Please list and sort bugs below to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.''' Things which are not closes can be changed as you go.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Always add your comments on bugzilla as well as the wiki for a more complete feedback by users and developers.

==Details==

Please get a bugzilla account (bugs.kde.org) and a techbase.kde.org account. Then "sign in" below, and select a period 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, as we will cross-check everybody else's bugs. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)
{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Ramblurr|Ramblurr]] || svn trunk latest ||
|}
{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a month that is not already taken from the list below and then query bugs.kde.org for all bugs in that month. Please put your irc nickname in the table below next to the month so we don't duplicate months.

The bugzilla query to use for this triage day is TBD. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month/time period !! IRC Nickname !! Status !! Query
|-
| 2005-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-01-01&chfieldto=2005-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-02-01&chfieldto=2005-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2005-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-03-01&chfieldto=2005-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-04-01&chfieldto=2005-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-05-01&chfieldto=2005-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-06-01&chfieldto=2005-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-07-01&chfieldto=2005-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-08-01&chfieldto=2005-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-09-01&chfieldto=2005-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-10-01&chfieldto=2005-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2005-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-11-01&chfieldto=2005-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2005-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2005-12-01&chfieldto=2005-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-01-01&chfieldto=2006-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2006-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-01-01&chfieldto=2007-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-02-01&chfieldto=2007-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2007-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-03-01&chfieldto=2007-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-04-01&chfieldto=2007-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-05-01&chfieldto=2007-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-06-01&chfieldto=2007-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-01&chfieldto=2007-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-08-01&chfieldto=2007-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-09-01&chfieldto=2007-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=2007-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-01-01&chfieldto=2006-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-02-01&chfieldto=2006-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2006-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-03-01&chfieldto=2006-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-04-01&chfieldto=2006-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-05-01&chfieldto=2006-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-06-01&chfieldto=2006-06-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-07 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-07-01&chfieldto=2006-07-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-08 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-08-01&chfieldto=2006-08-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-09 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-09-01&chfieldto=2006-09-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-10-01&chfieldto=2006-10-31&chfieldvalue=&newqueryname= Query]
|-
| 2006-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-11-01&chfieldto=2006-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2006-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-01&chfieldto=2006-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2007-11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-11-01&chfieldto=2007-11-30&chfieldvalue=&newqueryname= Query]
|-
| 2007-12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-12-01&chfieldto=2007-12-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-01 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-01&chfieldto=2008-01-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-02 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-02-01&chfieldto=2008-02-28&chfieldvalue=&newqueryname= Query]
|-
| 2008-03 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-03-01&chfieldto=2008-03-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-04 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-04-01&chfieldto=2008-04-30&chfieldvalue=&newqueryname= Query]
|-
| 2008-05 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-01&chfieldto=2008-05-31&chfieldvalue=&newqueryname= Query]
|-
| 2008-06 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=amarok&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailtype1=substring&email1=&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-06-01&chfieldto=now&chfieldvalue=&newqueryname= Query]
|-
|}

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to '''enable section editing''' by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs no longer present in 2.x}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed}}

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

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

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

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

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/AmarokDay1/Bugs not related to today}}

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

{{:Contribute/Bugsquad/BugDays/AmarokDay1/High profile}}

Contribute/Bugsquad/BugDays/AmarokDay1

2008-06-14T08:55:32Z

Krop: /* Division of Labour */

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs to be marked as INVALID

2008-06-14T08:43:46Z

Krop: /* Bugs to be marked as INVALID */

===Bugs to be marked as INVALID===
Bugs which are no longer valid go here. A link to the bug and why it qualifies as invalid should be provided.

Some examples of when a bug should be closed as INVALID:
*The reported behavior is not a bug
*The bug is completely unrelated to Amarok

This list is not exhaustive. If you feel a bug is invalid for any other reason, be sure to list it here, mentioning why you think it is invalid.

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs to be marked as RESOLVED

2008-06-14T08:43:31Z

Krop: /* Bugs to be marked as RESOLVED */

===Bugs to be marked as RESOLVED===
Bugs filed against Amarok 2.x (ie, only very recent ones) that can no longer be reproduced should be listed here. Bugs filed against earlier versions of Amarok that can no longer be reproduced should be listed in the section above.

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed

2008-06-14T08:43:02Z

Krop: /* Bugs needing version field changed */

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

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs no longer present in 2.x

2008-06-14T08:42:38Z

Krop: /* Bugs no longer present in 4.x */

===Bugs no longer present in 2.x===
If a bug is reported against a version of Amarok before 2.x, but the bug can no longer be reproduced in Amarok 1.x, then it should be listed here. Please '''do not''' close the bug. The Konqueror developers would like to check each one before they are closed.

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing version field changed

2008-06-14T08:41:21Z

Krop: New page: ===Bugs needing version field changed=== Bugs should be listed here if their version field is invalid (i.e. it is listed as "unspecified") and they are still present in KDE 4, so that the ...

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

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing users with particular setups

2008-06-14T08:41:03Z

Krop: New page: ===Bugs needing users with particular setups=== Bugs that require particular software or hardware that you don't have available should be listed here with a description of the non-standard...

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs no longer present in 2.x

2008-06-14T08:40:36Z

Krop: New page: ===Bugs no longer present in 4.x=== If a bug is reported against a version of KDE before 4.0, but the bug can no longer be reproduced in KDE 4.x, then it should be listed here. Please '''d...

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs not related to today

2008-06-14T08:39:51Z

Krop: New page: ===Bugs not related to today=== Bugs that are not related to today's target application should be listed here so they can be reassigned to the correct bugzilla product.

===Bugs not related to today===
Bugs that are not related to today's target application should be listed here so they can be reassigned to the correct bugzilla product.

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs that you cant do

2008-06-14T08:39:24Z

Krop: New page: ===Bugs that you can't do=== If you have bugs in your month that you can't do, and no-one has been able to help you with on IRC, please list them here for someone else to have a look at.

===Bugs that you can't do===
If you have bugs in your month that you can't do, and no-one has been able to help you with on IRC, please list them here for someone else to have a look at.

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs to be marked as DUPLICATE

2008-06-14T08:39:05Z

Krop: New page: ===Bugs to be marked as DUPLICATE=== Duplicates found should be placed here with a link to the bug which you think it is a duplicate of.

===Bugs to be marked as DUPLICATE===
Duplicates found should be placed here with a link to the bug which you think it is a duplicate of.

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs to be marked as INVALID

2008-06-14T08:38:41Z

Krop: New page: ===Bugs to be marked as INVALID=== Bugs which are no longer valid go here. A link to the bug and why it qualifies as invalid should be provided. Some examples of when a bug should be clos...

===Bugs to be marked as INVALID===
Bugs which are no longer valid go here. A link to the bug and why it qualifies as invalid should be provided.

Some examples of when a bug should be closed as INVALID:
*The reported behavior is not a bug
*The bug is completely unrelated to KDE

This list is not exhaustive. If you feel a bug is invalid for any other reason, be sure to list it here, mentioning why you think it is invalid.

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs to be marked as RESOLVED

2008-06-14T08:38:15Z

Krop: New page: ===Bugs to be marked as RESOLVED=== Bugs filed against KDE 4 (ie, only very recent ones) that can no longer be reproduced should be listed here. Bugs filed against earlier versions of KDE ...

===Bugs to be marked as RESOLVED===
Bugs filed against KDE 4 (ie, only very recent ones) that can no longer be reproduced should be listed here. Bugs filed against earlier versions of KDE that can no longer be reproduced should be listed in the section above.

Contribute/Bugsquad/BugDays/AmarokDay1/High profile

2008-06-14T08:37:40Z

Krop: New page: == High Profile ==

== High Profile ==

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs needing attention from Amarok developers

2008-06-14T08:37:07Z

Krop: New page: ===Bugs needing attention from Amarok developers=== Add bugs here if you need to find out whether the observed behavior is intended, or if there's some other reason that it would be useful...

===Bugs needing attention from Amarok developers===
Add bugs here if you need to find out whether the observed behavior is intended, or if there's some other reason that it would be useful for a Amarok developer to take a look. Make sure you indicate ''why'' the bug needs attention from them.

{{Warning|Always defer policy decisions to developers.}}

Contribute/Bugsquad/BugDays/AmarokDay1/Bugs awaiting feedback

2008-06-14T08:35:43Z

Krop: New page: ===Bugs awaiting feedback=== '''NB. Feedback should only be requested for bugs if you have tried and failed to reproduce them or if the report contains insufficient information to try and ...

===Bugs awaiting feedback===
'''NB. Feedback should only be requested for bugs if you have tried and failed to reproduce them or if the report contains insufficient information to try and reproduce the bug. Requesting feedback for a bug should be seen as a ''last resort'' only.'''

Bugs for which feedback has been requested, which should be revisited in 30 days to see if there's any response. Please list all bugs here for which feedback has been requested.