KDE TechBase - User contributions [en]

Getting Started/Build/Environment

2011-05-06T07:39:05Z

Krf: Fix missing quotes

== Introduction ==

Configuring your build environment is the single most important step in building KDE. A wrong decision or mistake here could at best mean you have to rebuild everything from scratch again, or at worst break your system KDE rendering your system unusable.

A lot of very important concepts will be discussed and it is important that you understand them before proceeding.

A set of configuration scripts and bash commands are provided as a recommended configuration when building KDE manually. If you use these as provided then your KDE build will be a lot easier and it will be easier for you to find support online. The one disadvantage to these scripts is that they hide important details from you which you may want to learn about, but the two methods are completely interchangeable so once you are comfortable building KDE using the scripts you can learn more by doing everything yourself.

It is recommended that you build KDE using your normal user account. In some circumstances you may want to build using a separate user account, such as if you are a KWin or Plasma developer wishing to test a full KDE session with compositing effects, but for most circumstances a simple way can be found for achieving the same aim while still running using your normal user account (e.g. Nested X using xypher).

== Git Configuration ==

KDE uses Git as its main source repository and revision control software which you need to configure before you can use it in KDE. You can find the recommended Git configuration for KDE on the [[Development/Git/Configuration|Git Configuration]] page.

== Path Configuration ==

This section explains the different paths that need to be configured for building KDE. The following section will demonstrate a simple method for setting up the required paths.

=== Source Path ===

The $KDE_SRC path environment variable defines where the KDE Build System can find the source files.

TODO: Decide how to do stable and unstable source branches in parallel. While Git supports having these in a single source clone to save disk space, it is sometimes nice to have separate clones to allow simultaneous parallel builds, and it takes less scripting to achieve. It's also conceptually closer to how svn works so seems preferable during the transition.

=== Build Path ===

The $KDE_BUILD path environment variable defines where the KDE Build System will create the build files.

The KDE build system requires that your source and build files be in different directories (aka out-of-source builds). This keeps your source directories clean and simplifies management of your different build files. :
* It makes it very easy to rebuild from scratch, you just delete the build directory to remove all the generated files - even old ones that "make clean" wouldn't remove.
* It is easier to look at the source files (grep, ls etc.).
* It allows multiple build trees with different settings, e.g. debug and release.

While for some simple build scenarios you could just create a "build" directory inside your 'source' directory (e.g. "kde/src/kdelibs/build"), this negates many of the advantages when used with a full KDE build. Instead clearly separate paths are recommended.

For example if we were building kdelibs we could have the following folders:

/home/myuser/kde/src/kdelibs
/home/myuser/kde/build/kdelibs

If you plan to build multiple branches of KDE such as stable and unstable in parallel then you will need to add an extra level to the directory:

/home/myuser/kde/src/master/kdelibs
/home/myuser/kde/src/4.6/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs

=== Install Path ===
The $KDEDIR path environment variable defines where the KDE Build System will install KDE.

It is strongly recommended for a development build that you do a user based install and not a root install, i.e. install your KDE build into a user-owned directory and not into the system /usr directory. This provides a number of advantages:
* Your root/system installed version of KDE is untouched, meaning your normal desktop and applications remain stable and usable even if your development build breaks
* You can build and run multiple development versions of KDE at the same time, i.e. a stable branch for bug fixes and an unstable branch for new features
* You can use a single alias or bash command to compile/link/install without having to do a su/sudo in the middle
* Doing "make" and "make install" as the same user is a lot quicker as the Makefiles are only parsed once.
* No root owned files in the build directory
* No problems caused by root not having a correctly configured KDE build environment
* It makes it very easy to reinstall from scratch, you just delete the install directory to remove all the installed files and rerun the build.

That said, the build instructions provided are completely generic and will work for building a root system install if you configure your environment to do so, i.e. for Linux from Scratch or doing a root install in a virtual machine for testing or packaging purposes.

For the kdelibs example given above we would then have:

/home/myuser/kde/src/master/kdelibs
/home/myuser/kde/src/4.6/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs
/home/myuser/kde/inst/master/kdelibs
/home/myuser/kde/inst/4.6/kdelibs

=== Home Path ===
The $KDEHOME path environment variable defines wat directory KDE will treat as your home folder, i.e. for stroing data writing config files to.

For the same reason as the Install Path, it is strongly recommended that you set your KDE Home Path to be different from your normal home folder.

For the kdelibs example given above we would then have:

/home/myuser/kde/src/master/kdelibs
/home/myuser/kde/src/4.6/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs
/home/myuser/kde/inst/master/kdelibs
/home/myuser/kde/inst/4.6/kdelibs
/home/myuser/kde/home/master/kdelibs
/home/myuser/kde/home/4.6/kdelibs

=== XDG Paths ===

The Cross Desktop (XDG) Paths XDG_DATA_DIRS and XDG_CONFIG_DIRS are a standard set of paths used to find various shared cross-desktop standard data and config such as mimetypes. If you are building the KDE Development Platform yourself then it is recommended to unset these paths to prevent your build from seeing your system install (usually /usr) as this will cause problems. However, if you do so you must install the shared-mime-info data into your development install path. If you are not building your own KDE Development Platform then you should not unset the XDG Data Paths.

=== Other Paths ===

There are a number of other paths that are required, but these can all be automatically derived and created by the config script given below.

== Environment Configuration ==

The example environment configuration script given below is for building KDE against your system Qt under your normal user account with an out-of-source build and installing into a user directory. By changing just four variables you can use the script to configure any KDE build environment you want.

It is recommended you create a separate script for each build environment you require. If you have separate source directories for each build then save the script into the root source directory with the name ".build-config" to allow the bash scripts in the next section to automatically load the config and create the required directories.

If you don't wish to use the bash scripts then you must manually create the required directories and manually execute the config script.

If you are building KDE using a dedicated user to run a full desktop session, then you should put this config into the users ~/.bashrc file.

Please see the notes above about the [[Getting_Started/Build/Environment#XDG_Paths|XDG Paths]], the example config script below overrides the XDG Data Paths.

=== Sample .build-config file ===
<code bash>
# KDE4 Build Environment configuration script
#
# To configure your build environment set LIB_SUFFIX, BASEDIR, BUILDNAME and
# QTDIR as appropriate
#
# The default values provided are for a master/trunk/unstable build in your own
# user directory using your system Qt

# Uncomment if building on a 64 bit system
#export LIB_SUFFIX=64

# Set where your base KDE development folder is located, usually ~/kde
export BASEDIR=~/kde

# Give the build a name, e.g. master, 4.6, debug, etc
export BUILDNAME=master

# Set up which Qt to use
# Use the system Qt, adjust path as required
export QTDIR=/usr
# Uncomment to use your own build of qt-kde
#export QTDIR=$BASEDIR/inst/master/qt-kde
#export PATH=$QTDIR/bin:$PATH
#export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
#export PKG_CONFIG_PATH=$QTDIR/lib:$PKG_CONFIG_PATH

# Set up the KDE paths
export KDE_SRC=$BASEDIR/src
export KDE_BUILD=$BASEDIR/build
export KDEDIR=$BASEDIR/inst/$BUILDNAME
export KDEDIRS=$KDEDIR
export KDEHOME=$BASEDIR/home/.$BUILDNAME
export KDETMP=/tmp/$BUILDNAME-$USER
export KDEVARTMP=/var/tmp/$BUILDNAME-$USER
mkdir -p $KDETMP
mkdir -p $KDEVARTMP

# Add the KDE plugins to the Qt plugins path
export QT_PLUGIN_PATH=$KDEDIR/lib/kde4/plugins

# Do we really need these?
export KDE4_DBUS_INTERFACES_DIR=$KDEDIR/share/dbus-1/interfaces
export PYTHON_SITE_PACKAGES_DIR=$KDEDIR/lib/python2.6/site-packages/PyKDE4

# Export the standard paths to include KDE
export PATH=$KDEDIR/bin:$PATH
export LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=$KDEDIR/lib/pkgconfig:$PKG_CONFIG_PATH

# Export the CMake paths so it searches for KDE in the right places
export CMAKE_PREFIX_PATH=$KDEDIR:$CMAKE_PREFIX_PATH
export CMAKE_LIBRARY_PATH=$KDEDIR/lib:$CMAKE_LIBRARY_PATH
export CMAKE_INCLUDE_PATH=$KDEDIR/include:$CMAKE_INCLUDE_PATH

# Unset XDG to avoid seeing KDE files from /usr
# If unset then you must install shared-mime-info
unset XDG_DATA_DIRS
unset XDG_CONFIG_DIRS

# Uncomment if you are using Icecream for distributed compiling
#export PATH=/opt/icecream/bin:$PATH

# Report what the environment is set to
echo
echo "*** Configured KDE Build Environment " $BUILDNAME " ***"
echo
echo "QTDIR=" $QTDIR
echo "KDEDIR=" $KDEDIR
echo "PATH=" $PATH
echo
</code>

== Useful Bash Scripts ==

This section provides a set of bash scripts to simplify setting up your build environment and managing the KDE build process. If you use these scripts, then you can use the 'Easy Recipe' option documented in these pages. If you do not want to use these scripts then you will need to use the 'Full Recipe' option documented in these pages.

You can find further details about using these scripts on the [[../Recipes|Build Recipes]] page.

The main commands provided are:

;''cs''
Change to source directory
;''cb''
Change to build directory
;''cmakekde''
Configure, build and install the current KDE module

=== findup ===
Save this script in an executable file called "findup" somewhere in your path, usually ~/bin/findup.

<code bash>
#!/bin/sh

arg="$1"
if test -z "$arg"; then exit 1; fi

while ! test -f "$arg"; do
cd ..
if test "$PWD" = "/"; then
exit 1
fi
done

echo $PWD/$arg
</code>

=== .bashrc ===
Add the following script to the end of your ~/.bashrc, or save as a separate ~/.kde-bashrc and add ''source .kde-bashrc'' to your ~/.bashrc.

<code bash>
###
## A script to setup some needed variables and functions for KDE 4 development.
## This should normally go in the ~/.bashrc file of your kde development user.

CURRENT_SHELL=$(echo $0)

prepend() { [ -d "$2" ] && eval $1=\"$2\$\{$1:+':'\$$1\}\" && export $1 ; }

# This will make the debug output prettier
export KDE_COLOR_DEBUG=1
export QTEST_COLORED=1

# Make
# Tell many scripts how to switch from source dir to build dir:
export OBJ_REPLACEMENT="s#$KDE_SRC#$KDE_BUILD#"

# Use makeobj instead of make, to automatically switch to the build dir.
# If you don't have makeobj, install the package named kdesdk-scripts or
# kdesdk, or check out kdesdk/scripts from svn, or just don't set the alias
# yet.
alias make=makeobj

##
# A function to easily build the current directory of KDE.
#
# This builds only the sources in the current ~/{src,build}/KDE subdirectory.
# Usage: cs KDE/kdebase && cmakekde
# will build/rebuild the sources in ~/src/KDE/kdebase
#
function cmakekde {
if test -n "$1"; then
# srcFolder is defined via command line argument
srcFolder="$1"
else
# get srcFolder for current dir
srcFolder=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
fi
# we are in the src folder, change to build directory
# Alternatively, we could just use makeobj in the commands below...
current=`pwd`
if [ "$srcFolder" = "$current" ]; then
cb
fi
# To disable tests, remove -DKDE4_BUILD_TESTS=TRUE
# To save disk space change "debugfull" to "debug"
cmake "$srcFolder" \
-DCMAKE_INSTALL_PREFIX=$KDEDIR \
-DKDE4_BUILD_TESTS=TRUE \
-DCMAKE_BUILD_TYPE=debugfull

# Comment out the following two lines to stop builds waiting after
# the configuration step, so that the user can check configure output
echo "Press <ENTER> to continue..."
read userinput

# Note: To speed up compiling, change 'make -j2' to 'make -jx',
# where x is your number of processors +1
nice make -j2 && make install
#Use this line instead if using icecream
#nice make CC=icecc -j6 && make install
RETURN=$?
cs
return ${RETURN}
}

function cd() {
if test -z "$1"; then
builtin cd
elif test -z "$2"; then
builtin cd "$1"
else
builtin cd "$1" "$2"
fi
_f=`findup .build-config`
if test -n "$_f" -a "$_lastf" != "$_f"; then
echo "Loading $_f"
_lastf="$_f"
source "$_f"
fi
}

##
# A function to easily change to the build directory.
# Usage: cb KDE/kdebase
# will change to $KDE_BUILD/KDE/kdebase
# Usage: cb
# will simply go to the build folder if you are currently in a src folder
# Example:
# $ pwd
# /home/user/src/KDE/kdebase
# $ cb && pwd
# /home/user/build/KDE/kdebase
#
function cb {
local dest

# Make sure build directory exists.
mkdir -p "$KDE_BUILD"

# command line argument
if test -n "$1"; then
cd "$KDE_BUILD/$1"
return
fi
# substitute src dir with build dir
dest=`pwd | sed -e s,$KDE_SRC,$KDE_BUILD,`
if test ! -d "$dest"; then
# build directory does not exist, create
mkdir -p "$dest"
fi
cd "$dest"
}

##
# Change to the source directory. Same as cb, except this
# switches to $KDE_SRC instead of $KDE_BUILD.
# Usage: cs KDE/kdebase
# will change to $KDE_SRC/KDE/kdebase
# Usage: cs
# will simply go to the source folder if you are currently in a build folder
# Example:
# $ pwd
# /home/myuser/kde/build/master/KDE/kdebase
# $ cs && pwd
# /home/myuser/kde/src/master/KDE/kdebase
#
function cs {
local dest current

# Make sure source directory exists.
mkdir -p "$KDE_SRC"

# command line argument
if test -n "$1"; then
cd "$KDE_SRC/$1"
else
# substitute build dir with src dir
dest=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
current=`pwd`
if [ "$dest" = "$current" ]; then
cd "$KDE_SRC"
else
cd "$dest"
fi
fi
}

##
# Add autocompletion to cs function
#
function _cs_scandir
{
local base ext

base=$1
ext=$2
if [ -d $base ]; then
for d in `ls $base`; do
if [ -d $base/$d ]; then
dirs="$dirs $ext$d/"
fi
done
fi
}

function _cs()
{
local cur dirs
_cs_scandir "$KDE_SRC"
_cs_scandir "$KDE_SRC/KDE" "KDE/"
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
COMPREPLY=( $(compgen -W "${dirs}" -- ${cur}) )
}

svndiff ()
{
svn diff "$*" | colordiff | less;
}

# Setup shell
if [ "$CURRENT_SHELL" = "bash" ]; then
complete -F _cs cs
fi

</code>

Getting Started/Build/Environment

2011-05-06T07:36:23Z

Krf: Make the bashrc somewhat shell independent ("complete" is bash-only)

== Introduction ==

Configuring your build environment is the single most important step in building KDE. A wrong decision or mistake here could at best mean you have to rebuild everything from scratch again, or at worst break your system KDE rendering your system unusable.

A lot of very important concepts will be discussed and it is important that you understand them before proceeding.

A set of configuration scripts and bash commands are provided as a recommended configuration when building KDE manually. If you use these as provided then your KDE build will be a lot easier and it will be easier for you to find support online. The one disadvantage to these scripts is that they hide important details from you which you may want to learn about, but the two methods are completely interchangeable so once you are comfortable building KDE using the scripts you can learn more by doing everything yourself.

It is recommended that you build KDE using your normal user account. In some circumstances you may want to build using a separate user account, such as if you are a KWin or Plasma developer wishing to test a full KDE session with compositing effects, but for most circumstances a simple way can be found for achieving the same aim while still running using your normal user account (e.g. Nested X using xypher).

== Git Configuration ==

KDE uses Git as its main source repository and revision control software which you need to configure before you can use it in KDE. You can find the recommended Git configuration for KDE on the [[Development/Git/Configuration|Git Configuration]] page.

== Path Configuration ==

This section explains the different paths that need to be configured for building KDE. The following section will demonstrate a simple method for setting up the required paths.

=== Source Path ===

The $KDE_SRC path environment variable defines where the KDE Build System can find the source files.

TODO: Decide how to do stable and unstable source branches in parallel. While Git supports having these in a single source clone to save disk space, it is sometimes nice to have separate clones to allow simultaneous parallel builds, and it takes less scripting to achieve. It's also conceptually closer to how svn works so seems preferable during the transition.

=== Build Path ===

The $KDE_BUILD path environment variable defines where the KDE Build System will create the build files.

The KDE build system requires that your source and build files be in different directories (aka out-of-source builds). This keeps your source directories clean and simplifies management of your different build files. :
* It makes it very easy to rebuild from scratch, you just delete the build directory to remove all the generated files - even old ones that "make clean" wouldn't remove.
* It is easier to look at the source files (grep, ls etc.).
* It allows multiple build trees with different settings, e.g. debug and release.

While for some simple build scenarios you could just create a "build" directory inside your 'source' directory (e.g. "kde/src/kdelibs/build"), this negates many of the advantages when used with a full KDE build. Instead clearly separate paths are recommended.

For example if we were building kdelibs we could have the following folders:

/home/myuser/kde/src/kdelibs
/home/myuser/kde/build/kdelibs

If you plan to build multiple branches of KDE such as stable and unstable in parallel then you will need to add an extra level to the directory:

/home/myuser/kde/src/master/kdelibs
/home/myuser/kde/src/4.6/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs

=== Install Path ===
The $KDEDIR path environment variable defines where the KDE Build System will install KDE.

It is strongly recommended for a development build that you do a user based install and not a root install, i.e. install your KDE build into a user-owned directory and not into the system /usr directory. This provides a number of advantages:
* Your root/system installed version of KDE is untouched, meaning your normal desktop and applications remain stable and usable even if your development build breaks
* You can build and run multiple development versions of KDE at the same time, i.e. a stable branch for bug fixes and an unstable branch for new features
* You can use a single alias or bash command to compile/link/install without having to do a su/sudo in the middle
* Doing "make" and "make install" as the same user is a lot quicker as the Makefiles are only parsed once.
* No root owned files in the build directory
* No problems caused by root not having a correctly configured KDE build environment
* It makes it very easy to reinstall from scratch, you just delete the install directory to remove all the installed files and rerun the build.

That said, the build instructions provided are completely generic and will work for building a root system install if you configure your environment to do so, i.e. for Linux from Scratch or doing a root install in a virtual machine for testing or packaging purposes.

For the kdelibs example given above we would then have:

/home/myuser/kde/src/master/kdelibs
/home/myuser/kde/src/4.6/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs
/home/myuser/kde/inst/master/kdelibs
/home/myuser/kde/inst/4.6/kdelibs

=== Home Path ===
The $KDEHOME path environment variable defines wat directory KDE will treat as your home folder, i.e. for stroing data writing config files to.

For the same reason as the Install Path, it is strongly recommended that you set your KDE Home Path to be different from your normal home folder.

For the kdelibs example given above we would then have:

/home/myuser/kde/src/master/kdelibs
/home/myuser/kde/src/4.6/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs
/home/myuser/kde/inst/master/kdelibs
/home/myuser/kde/inst/4.6/kdelibs
/home/myuser/kde/home/master/kdelibs
/home/myuser/kde/home/4.6/kdelibs

=== XDG Paths ===

The Cross Desktop (XDG) Paths XDG_DATA_DIRS and XDG_CONFIG_DIRS are a standard set of paths used to find various shared cross-desktop standard data and config such as mimetypes. If you are building the KDE Development Platform yourself then it is recommended to unset these paths to prevent your build from seeing your system install (usually /usr) as this will cause problems. However, if you do so you must install the shared-mime-info data into your development install path. If you are not building your own KDE Development Platform then you should not unset the XDG Data Paths.

=== Other Paths ===

There are a number of other paths that are required, but these can all be automatically derived and created by the config script given below.

== Environment Configuration ==

The example environment configuration script given below is for building KDE against your system Qt under your normal user account with an out-of-source build and installing into a user directory. By changing just four variables you can use the script to configure any KDE build environment you want.

It is recommended you create a separate script for each build environment you require. If you have separate source directories for each build then save the script into the root source directory with the name ".build-config" to allow the bash scripts in the next section to automatically load the config and create the required directories.

If you don't wish to use the bash scripts then you must manually create the required directories and manually execute the config script.

If you are building KDE using a dedicated user to run a full desktop session, then you should put this config into the users ~/.bashrc file.

Please see the notes above about the [[Getting_Started/Build/Environment#XDG_Paths|XDG Paths]], the example config script below overrides the XDG Data Paths.

=== Sample .build-config file ===
<code bash>
# KDE4 Build Environment configuration script
#
# To configure your build environment set LIB_SUFFIX, BASEDIR, BUILDNAME and
# QTDIR as appropriate
#
# The default values provided are for a master/trunk/unstable build in your own
# user directory using your system Qt

# Uncomment if building on a 64 bit system
#export LIB_SUFFIX=64

# Set where your base KDE development folder is located, usually ~/kde
export BASEDIR=~/kde

# Give the build a name, e.g. master, 4.6, debug, etc
export BUILDNAME=master

# Set up which Qt to use
# Use the system Qt, adjust path as required
export QTDIR=/usr
# Uncomment to use your own build of qt-kde
#export QTDIR=$BASEDIR/inst/master/qt-kde
#export PATH=$QTDIR/bin:$PATH
#export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
#export PKG_CONFIG_PATH=$QTDIR/lib:$PKG_CONFIG_PATH

# Set up the KDE paths
export KDE_SRC=$BASEDIR/src
export KDE_BUILD=$BASEDIR/build
export KDEDIR=$BASEDIR/inst/$BUILDNAME
export KDEDIRS=$KDEDIR
export KDEHOME=$BASEDIR/home/.$BUILDNAME
export KDETMP=/tmp/$BUILDNAME-$USER
export KDEVARTMP=/var/tmp/$BUILDNAME-$USER
mkdir -p $KDETMP
mkdir -p $KDEVARTMP

# Add the KDE plugins to the Qt plugins path
export QT_PLUGIN_PATH=$KDEDIR/lib/kde4/plugins

# Do we really need these?
export KDE4_DBUS_INTERFACES_DIR=$KDEDIR/share/dbus-1/interfaces
export PYTHON_SITE_PACKAGES_DIR=$KDEDIR/lib/python2.6/site-packages/PyKDE4

# Export the standard paths to include KDE
export PATH=$KDEDIR/bin:$PATH
export LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=$KDEDIR/lib/pkgconfig:$PKG_CONFIG_PATH

# Export the CMake paths so it searches for KDE in the right places
export CMAKE_PREFIX_PATH=$KDEDIR:$CMAKE_PREFIX_PATH
export CMAKE_LIBRARY_PATH=$KDEDIR/lib:$CMAKE_LIBRARY_PATH
export CMAKE_INCLUDE_PATH=$KDEDIR/include:$CMAKE_INCLUDE_PATH

# Unset XDG to avoid seeing KDE files from /usr
# If unset then you must install shared-mime-info
unset XDG_DATA_DIRS
unset XDG_CONFIG_DIRS

# Uncomment if you are using Icecream for distributed compiling
#export PATH=/opt/icecream/bin:$PATH

# Report what the environment is set to
echo
echo "*** Configured KDE Build Environment " $BUILDNAME " ***"
echo
echo "QTDIR=" $QTDIR
echo "KDEDIR=" $KDEDIR
echo "PATH=" $PATH
echo
</code>

== Useful Bash Scripts ==

This section provides a set of bash scripts to simplify setting up your build environment and managing the KDE build process. If you use these scripts, then you can use the 'Easy Recipe' option documented in these pages. If you do not want to use these scripts then you will need to use the 'Full Recipe' option documented in these pages.

You can find further details about using these scripts on the [[../Recipes|Build Recipes]] page.

The main commands provided are:

;''cs''
Change to source directory
;''cb''
Change to build directory
;''cmakekde''
Configure, build and install the current KDE module

=== findup ===
Save this script in an executable file called "findup" somewhere in your path, usually ~/bin/findup.

<code bash>
#!/bin/sh

arg="$1"
if test -z "$arg"; then exit 1; fi

while ! test -f "$arg"; do
cd ..
if test "$PWD" = "/"; then
exit 1
fi
done

echo $PWD/$arg
</code>

=== .bashrc ===
Add the following script to the end of your ~/.bashrc, or save as a separate ~/.kde-bashrc and add ''source .kde-bashrc'' to your ~/.bashrc.

<code bash>
###
## A script to setup some needed variables and functions for KDE 4 development.
## This should normally go in the ~/.bashrc file of your kde development user.

CURRENT_SHELL=$(echo $0)

prepend() { [ -d "$2" ] && eval $1=\"$2\$\{$1:+':'\$$1\}\" && export $1 ; }

# This will make the debug output prettier
export KDE_COLOR_DEBUG=1
export QTEST_COLORED=1

# Make
# Tell many scripts how to switch from source dir to build dir:
export OBJ_REPLACEMENT="s#$KDE_SRC#$KDE_BUILD#"

# Use makeobj instead of make, to automatically switch to the build dir.
# If you don't have makeobj, install the package named kdesdk-scripts or
# kdesdk, or check out kdesdk/scripts from svn, or just don't set the alias
# yet.
alias make=makeobj

##
# A function to easily build the current directory of KDE.
#
# This builds only the sources in the current ~/{src,build}/KDE subdirectory.
# Usage: cs KDE/kdebase && cmakekde
# will build/rebuild the sources in ~/src/KDE/kdebase
#
function cmakekde {
if test -n "$1"; then
# srcFolder is defined via command line argument
srcFolder="$1"
else
# get srcFolder for current dir
srcFolder=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
fi
# we are in the src folder, change to build directory
# Alternatively, we could just use makeobj in the commands below...
current=`pwd`
if [ "$srcFolder" = "$current" ]; then
cb
fi
# To disable tests, remove -DKDE4_BUILD_TESTS=TRUE
# To save disk space change "debugfull" to "debug"
cmake "$srcFolder" \
-DCMAKE_INSTALL_PREFIX=$KDEDIR \
-DKDE4_BUILD_TESTS=TRUE \
-DCMAKE_BUILD_TYPE=debugfull

# Comment out the following two lines to stop builds waiting after
# the configuration step, so that the user can check configure output
echo "Press <ENTER> to continue..."
read userinput

# Note: To speed up compiling, change 'make -j2' to 'make -jx',
# where x is your number of processors +1
nice make -j2 && make install
#Use this line instead if using icecream
#nice make CC=icecc -j6 && make install
RETURN=$?
cs
return ${RETURN}
}

function cd() {
if test -z "$1"; then
builtin cd
elif test -z "$2"; then
builtin cd "$1"
else
builtin cd "$1" "$2"
fi
_f=`findup .build-config`
if test -n "$_f" -a "$_lastf" != "$_f"; then
echo "Loading $_f"
_lastf="$_f"
source "$_f"
fi
}

##
# A function to easily change to the build directory.
# Usage: cb KDE/kdebase
# will change to $KDE_BUILD/KDE/kdebase
# Usage: cb
# will simply go to the build folder if you are currently in a src folder
# Example:
# $ pwd
# /home/user/src/KDE/kdebase
# $ cb && pwd
# /home/user/build/KDE/kdebase
#
function cb {
local dest

# Make sure build directory exists.
mkdir -p "$KDE_BUILD"

# command line argument
if test -n "$1"; then
cd "$KDE_BUILD/$1"
return
fi
# substitute src dir with build dir
dest=`pwd | sed -e s,$KDE_SRC,$KDE_BUILD,`
if test ! -d "$dest"; then
# build directory does not exist, create
mkdir -p "$dest"
fi
cd "$dest"
}

##
# Change to the source directory. Same as cb, except this
# switches to $KDE_SRC instead of $KDE_BUILD.
# Usage: cs KDE/kdebase
# will change to $KDE_SRC/KDE/kdebase
# Usage: cs
# will simply go to the source folder if you are currently in a build folder
# Example:
# $ pwd
# /home/myuser/kde/build/master/KDE/kdebase
# $ cs && pwd
# /home/myuser/kde/src/master/KDE/kdebase
#
function cs {
local dest current

# Make sure source directory exists.
mkdir -p "$KDE_SRC"

# command line argument
if test -n "$1"; then
cd "$KDE_SRC/$1"
else
# substitute build dir with src dir
dest=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
current=`pwd`
if [ "$dest" = "$current" ]; then
cd "$KDE_SRC"
else
cd "$dest"
fi
fi
}

##
# Add autocompletion to cs function
#
function _cs_scandir
{
local base ext

base=$1
ext=$2
if [ -d $base ]; then
for d in `ls $base`; do
if [ -d $base/$d ]; then
dirs="$dirs $ext$d/"
fi
done
fi
}

function _cs()
{
local cur dirs
_cs_scandir "$KDE_SRC"
_cs_scandir "$KDE_SRC/KDE" "KDE/"
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
COMPREPLY=( $(compgen -W "${dirs}" -- ${cur}) )
}

svndiff ()
{
svn diff "$*" | colordiff | less;
}

# Setup shell
if [ $CURRENT_SHELL = "bash" ]; then
complete -F _cs cs
fi

</code>

User:Krf

2011-05-06T07:33:17Z

Krf:

Real name: Kevin Funk

Nick name: KRF (IRC, Jabber, etc.)

Homepage: http://electrostorm.net

User:Krf

2011-05-06T07:32:57Z

Krf:

Real name: Kevin Funk
Nick name: KRF (IRC, Jabber, etc.)
Homepage: http://electrostorm.net

User talk:Danimo

2008-04-29T13:10:06Z

Krf:

==CAPTCHAs that won't go away==
Aseigo [[Talk:Main_Page#Something_wrong_with_the_CAPTCHAs|suggested]] that I ask you about this. Everytime I make an edit, it claims that I am adding a URL, and wants me to do some math. Is it even supposed to do this to registered users? In any case, ''most'' times I am not adding a url at all, and I tire of the systems inordinate appetite for elementary arithmetic. Can this be fixed? Thanks. --[[User:Axiom|Axiom]] 20:27, 28 March 2007 (CEST)

== <nowiki>{{file}}</nowiki> ==

As you asked me, I removed all the occurrences of <nowiki>{{file}}</nowiki> with <nowiki>{{path}}</nowiki>, and removed the obsolete template <nowiki>{{file}}</nowiki>. -- [[user:Pino|pino]] 02:16, 29 May 2007 (CEST)

:There is also a template called <nowiki>{{module}}</nowiki> for KDE modules (kdelibs, kdebase), etc. I initially used path here, too, and thought that's enough. It's not widely used, only by 2 articles. Maybe we should replace it by path again? What do you think? --[[User:Dhaumann|Dhaumann]] 09:14, 29 May 2007 (CEST)

::I agree. --[[User:Danimo|Danimo]] 09:28, 29 May 2007 (CEST)

::Or maybe link it to the module page in the apidocs (e.g [http://api.kde.org/4.0-api/kdelibs-apidocs/ kdelibs])? --[[User:Milliams|milliams]] 14:47, 29 May 2007 (CEST)

:::Good idea, <nowiki>{{kdelibs}}, {{kdebase}}</nowiki> etc... +1 from my side :) --[[User:Dhaumann|Dhaumann]] 15:11, 29 May 2007 (CEST)

::::Sounds good. Or how about <nowiki>{{module|foo}}</nowiki> linking to http://api.kde.org/4.0-api/foo-apidocs/? I don't know how flexible this method is though? --[[User:Milliams|milliams]] 19:41, 29 May 2007 (CEST)

:::::+1 on [[User:Milliams|milliams]]' idea --[[user:Pino|pino]] 21:35, 29 May 2007 (CEST)

==Assistance needed for new contributor to Techbase==
Hi. My name is Thor, I am a new contributor to KDE and I am looking to provide some help with regard to one of the KDE Games, KTuberling (The Potato dude). I am a Polyglot, and work in many different languages, and I have noticed on issues of KTuberling that even with correct software in place, certain speech selections do not function (Notably; Serbian and Danish). I have been working on these for a while and would like to obtain source code for the Tuberling to try and correct the error. Could you tell me please how I find out who is working on what, and what they are doing to it? Thanks and Regards. [[User:ThunderGod|ThunderGod]] 15:40, 30 December 2007 (CET)
:The best place to find assistance with this is by visiting the #kdegames or #kde-edu channels on irc.freenode.org or by sending an joining the KDE Games mailing list at [https://mail.kde.org/mailman/listinfo/kde-games-devel https://mail.kde.org/mailman/listinfo/kde-games-devel]. I believe tsdgeos (Albert Astals Cid) is the best person to speak to. --[[User:Milliams|milliams]] 17:13, 30 December 2007 (CET)

== More readable URLs ==

At the moment all links on this site are in the form [http://techbase.kde.org/index.php?title=Development/Tutorials http://techbase.kde.org/index.php?title=Development/Tutorials]. I think it would make the site much more readable to convert these links into something like [http://techbase.kde.org/Development/Tutorials http://techbase.kde.org/Development/Tutorials]. Now, as you can see, if you click on that link it does indeed work and takes you to the same page (so you've obviously got mod_rewrite working correctly) so the problem is that mediawiki itself isn't formatting it's links to take advantage of this. I think you basically need to do step 2 from [http://www.mediawiki.org/wiki/Manual:Short_URL#Setup_steps here]. --[[User:Milliams|milliams]] 14:53, 18 April 2008 (CEST)
:It seems this is working now. Thanks a lot :) --[[User:Milliams|milliams]] 14:34, 28 April 2008 (CEST)

== Remove my account ==

Please remove my account; i'd like to choose another username. Thank you. [[User:Krf|KRF]]

:Mediawiki has no concept of user account deletion, since that would mess up the history. Just create a new user and add redirects from your current user accounts user page. --[[User:Danimo|Danimo]] 17:55, 20 April 2008 (CEST)

Okay, would be nice if you could make my username uppercase then... Some database tweaking maybe? ;). No need to answer this, you can remove my entry when you've read it. Thank you anyway. [[User:Krf|KRF]]

== Hidden search button text in french localized ktechbase==

When switching ktechbase language to french the button search text is really too small. I have read somewhere that the css file will use fixed width for a while so changing the search button width from 4em to 6em will fix that small issue.

User talk:Danimo

2008-04-20T15:49:29Z

Krf: /* Remove my account */ new section

==CAPTCHAs that won't go away==
Aseigo [[Talk:Main_Page#Something_wrong_with_the_CAPTCHAs|suggested]] that I ask you about this. Everytime I make an edit, it claims that I am adding a URL, and wants me to do some math. Is it even supposed to do this to registered users? In any case, ''most'' times I am not adding a url at all, and I tire of the systems inordinate appetite for elementary arithmetic. Can this be fixed? Thanks. --[[User:Axiom|Axiom]] 20:27, 28 March 2007 (CEST)

== <nowiki>{{file}}</nowiki> ==

As you asked me, I removed all the occurrences of <nowiki>{{file}}</nowiki> with <nowiki>{{path}}</nowiki>, and removed the obsolete template <nowiki>{{file}}</nowiki>. -- [[user:Pino|pino]] 02:16, 29 May 2007 (CEST)

:There is also a template called <nowiki>{{module}}</nowiki> for KDE modules (kdelibs, kdebase), etc. I initially used path here, too, and thought that's enough. It's not widely used, only by 2 articles. Maybe we should replace it by path again? What do you think? --[[User:Dhaumann|Dhaumann]] 09:14, 29 May 2007 (CEST)

::I agree. --[[User:Danimo|Danimo]] 09:28, 29 May 2007 (CEST)

::Or maybe link it to the module page in the apidocs (e.g [http://api.kde.org/4.0-api/kdelibs-apidocs/ kdelibs])? --[[User:Milliams|milliams]] 14:47, 29 May 2007 (CEST)

:::Good idea, <nowiki>{{kdelibs}}, {{kdebase}}</nowiki> etc... +1 from my side :) --[[User:Dhaumann|Dhaumann]] 15:11, 29 May 2007 (CEST)

::::Sounds good. Or how about <nowiki>{{module|foo}}</nowiki> linking to http://api.kde.org/4.0-api/foo-apidocs/? I don't know how flexible this method is though? --[[User:Milliams|milliams]] 19:41, 29 May 2007 (CEST)

:::::+1 on [[User:Milliams|milliams]]' idea --[[user:Pino|pino]] 21:35, 29 May 2007 (CEST)

==Assistance needed for new contributor to Techbase==
Hi. My name is Thor, I am a new contributor to KDE and I am looking to provide some help with regard to one of the KDE Games, KTuberling (The Potato dude). I am a Polyglot, and work in many different languages, and I have noticed on issues of KTuberling that even with correct software in place, certain speech selections do not function (Notably; Serbian and Danish). I have been working on these for a while and would like to obtain source code for the Tuberling to try and correct the error. Could you tell me please how I find out who is working on what, and what they are doing to it? Thanks and Regards. [[User:ThunderGod|ThunderGod]] 15:40, 30 December 2007 (CET)
:The best place to find assistance with this is by visiting the #kdegames or #kde-edu channels on irc.freenode.org or by sending an joining the KDE Games mailing list at [https://mail.kde.org/mailman/listinfo/kde-games-devel https://mail.kde.org/mailman/listinfo/kde-games-devel]. I believe tsdgeos (Albert Astals Cid) is the best person to speak to. --[[User:Milliams|milliams]] 17:13, 30 December 2007 (CET)

== More readable URLs ==

At the moment all links on this site are in the form [http://techbase.kde.org/index.php?title=Development/Tutorials http://techbase.kde.org/index.php?title=Development/Tutorials]. I think it would make the site much more readable to convert these links into something like [http://techbase.kde.org/Development/Tutorials http://techbase.kde.org/Development/Tutorials]. Now, as you can see, if you click on that link it does indeed work and takes you to the same page (so you've obviously got mod_rewrite working correctly) so the problem is that mediawiki itself isn't formatting it's links to take advantage of this. I think you basically need to do step 2 from [http://www.mediawiki.org/wiki/Manual:Short_URL#Setup_steps here]. --[[User:Milliams|milliams]] 14:53, 18 April 2008 (CEST)

== Remove my account ==

Please remove my account; i'd like to choose another username. Thank you. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2

2008-04-20T14:35:50Z

Krf: done

==Introduction==
This day will happen in the future at some point, but feel free to start now. The aim is to carry on from where we left off on [[Contribute/Bugsquad/BugDays/06APR08|6th April Bug Day]]. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Konqueror.

'''The goal of this bug-day is to check for: simple step-by-step instructions, reproducibility, and most of all, come up with test-cases for reproducing the bugs. This will enable the Konqueror developers to deal with bugs more easily, and so have more time left to actually fix them.''' When you have added either a test-case or step-by-step instructions for the reproduction of a bug, please list it in the appropriate section below, so that a second triager can see if they can get your instructions/test-case to work correctly. [http://konqueror.kde.org/investigatebug/ This page] provides an excellent explanation of how to create a test-case. [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page] also has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Konqueror doesn't have as many duplicates as some applications, and we don't want to claim things are duplicates when they aren't. So do not look too hard for them, and '''make sure''' to double check them with someone else, preferably one of the developers before marking/closing.'''We especially don't want to create more work for developers!'''

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

You should either be working with Konqueror from KDE 4 (either 4.0.2 or newer is best or SVN trunk) for testing these bugs. In this case, it probably won't matter which one, because KHTML/KJS are aggressively forward-ported and back-ported, and you might find 4.0.x easier to compile.

You may need another browser to test things in.

===Testcases===
If you come across a bug with a testcase in the text, put it under the testcase section. If it isn't marked "testcase" in the title, make a note of that. Check that the testcase works! (And doesn't work!)

Most importantly, we need to [http://konqueror.kde.org/investigatebug/ create testcases]. These are time-consuming, but extremely useful and really help out developers. These are especially important if it is a site that is either a non-Western language or a site you need some sort of account for.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a major website doesn't work, that is important.
Let's keep track of them.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", it won't show up in developer's searches for 4.0 bugs! Change the version field to match what the other one says, i.e. to match version the bug was first reported in, or mark it below if you don't have bugzilla permissions. Do not update or change the version number (ex. from 3.5.2 to 4.0.2) if it is currently set as a number! Just make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build or which distro the packages come from).

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Add your comments even on bugzilla for a more complete feedback by users and developers.

==Details==

Please select a period of bugs from the [[#Division_of_Labour|Division of Labour]] section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. '''If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r795406||
|-
|[[User:krop|krop]]||svn trunk <s>r797569</s> <s>r.798035</s> r. 799086||
|-
|[[User:finex|FiNeX]]||svn trunk r797319 ||
|-
|[[User:Nixeagle|Nixeagle]] || KDE 4.0.3 Gentoo Linux ||
|-
|[[User:Frank78ac|frank78ac]] || svn trunk r798811 ||
|-
|[[User:Talavis|Talavis]] || svn trunk r798735 and 3.5.9 ||
|-
|[[User:lemma|lemma]] || svn trunk r798768 and 3.5.9 ||
|-
|[[User:Batika|Batika]] || KDE 4.0.3 Gentoo Linux ||
|-
|[[User:Njg234908|Njg234908]] || KDE 4.0.3 openSUSE ||
|-
|[[User:KRF|KRF]] || KDE 4.0.3 Kubuntu ||
|-
|[[User:Crvena_Zvezda|Crvena_Zvezda]] || KDE 4.0.3 Kubuntu 8.04 ||
|-
|[[User:katastrophe|katastrophe]] || KDE 4.0.3 gentoo ||
|-
|[[User:mzanetti|mzanetti]] || svn trunk r798527 and 3.5.9 on Gentoo ||
|}

{{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 and then query bugs.kde.org for all bugs in that month. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.

The bugzilla query to use for this triage day can be [http://bugs.kde.org/query.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=konqueror&component=khtml&component=khtml+adblock&component=khtml+ecma&component=khtml+event&component=khtml+forms&component=khtml+image+part&component=khtml+parsing&component=khtml+part&component=khtml+printing&component=khtml+renderer&component=khtml+xml&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_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=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2003-01-01&chfieldto=2003-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&newqueryname=konq-triage-2003-01&namedcmd=2003-onwards found here]. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month !! No of bugs !! IRC Nickname !! Status
|-
|2005-02 || 14 ||[[User:finex|FiNeX]]|| working ||
|-
|2005-03 || 20 || [[User:Batika|Batika]] || in progress... ||
|-
|2005-04 || 16 || [[User:Grundleborg|Grundleborg]] || in progress ||
|-
|2005-07 || 10 ||[[User:krop|krop]]|| Done. {{Bug|109218}} left (kwallet is buggy atm) ||
|-
|2005-08 || 10 ||[[User:krop|krop]]|| Done. ||
|-
|2005-09 || 16 || [[User:Nixeagle|Nixeagle]] || done. Bugs I had issues with are at [[User:Nixeagle/konquerorbugs]]. I'd appreciate it if that page were updated as folks look at the bugs.||
|-
|2005-11 || 16 || [[User:Nixeagle|Nixeagle]] || done - any I did not finish are at [[User:Nixeagle/konquerorbugs]]
|-
|2006-03 || 17 || [[User:Nixeagle|Nixeagle]] || done - incomplete at [[User:Nixeagle/konquerorbugs]]
|-
|2006-04 || 19 || [[User:Nixeagle|Nixeagle]] || working
|-
|2006-05 || 20 || [[User:Njg234908|Njg234908]] || 10 down back later to complete :)
|-
|2006-06 || 21 || [[User:Crvena_Zvezda|Crvena_Zvezda]] || just starting
|-
|2006-07 || 16 || [[User:katastrophe|katastrophe]] || in progress
|-
|2006-08 || 19 || [[User:mzanetti|mzanetti]] || in progress
|-
|2006-09 || 23
|-
|2006-10 || 27
|-
|2006-11 || 25
|-
|2006-12 || 17
|-
|2007-01 || 26
|-
|2007-02 || 26 || [[User:lemma|lemma]] || starting out...
|-
|2007-03 || 25 ||[[User:krop|krop]]|| in progress... ||
|-
|2007-04 || 11
|-
|2007-05 || 20
|-
|2007-06 || 21
|-
|2007-07 || 16 || [[User:KRF|KRF]] || done
|-
|2007-08 || 12 || [[User:Talavis|Talavis]] || in progress
|-
|2007-09 || 9 || [[User:Talavis|Talavis]] || Done, unable to test: [[User:Talavis/konqbugs]]
|-
|2007-10 || 16
|-
|2007-11 || 21 || [[User:KRF|KRF]] || done
|-
|2007-12 || 23
|-
|2008-01 || 32
|-
|2008-02 || 28
|-
|2008-03 || 22
|-
|2008-04 || 2
|}

(Total bugs 615)

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.
:For those interested, this was implemented after a short discussion on IRC between grundleborg, blauzahl, _lemma, and myself (nixeagle).

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with test-cases Added}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with step-by-step instructions}}

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

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

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

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Non english locales}}

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/High Profile}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Needs more information}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs not related to today}}

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing attention from Konqueror developers

2008-04-20T14:26:19Z

Krf:

===Bugs needing attention from Konqueror developers===
Add bugs here if you need to find out whether the observed behavior is intended, or if there's some other reason that it would be useful for a Konqueror developer to take a look. Make sure you indicate ''why'' the bug needs attention from them.

*{{Bug|108634}} - The bug reporter complains about the style Konqueror uses for <abbr> & <acronym>. Konqueror just uses the "typical style" suggested here : http://www.w3.org/TR/REC-CSS2/sample.html [[User:krop|krop]]
*<s>{{Bug|124193}} - Report has a problem with XLST, the only response to this bug is that XLST is not supported.</s> [[User:Nixeagle|Nixeagle]]
** Maksim has had a look, stated it was low priority but not a WONTFIX. [[User:Nixeagle|Nixeagle]]
*<s>{{Bug|124843}}</s> - Report appears as if it may have a fix on the page. However I can't confirm as there is no way to get a working demo up. If you guys happen to know if this is resolved, please close it. Otherwise we have to wait until we can get a working demo going again. [[User:Nixeagle|Nixeagle]]
**Closed after speaking to harri on IRC. [[User:Nixeagle|Nixeagle]]
*{{Bug|103468}} - not sure what can really be done about this. Should it be closed? [[User:Grundleborg|Grundleborg]]
*{{Bug|124910}} - Is this fixed? For all appearances it is in kde 4.0.3. [[User:Nixeagle|Nixeagle]]
**Dev responded, looks like that one is staying open. We probably will need to create a test case of some sort to be sure that it really is fixed or not. Sadly I'm not able to do this. [[User:Nixeagle|Nixeagle]]
*{{Bug|102198}} - Given comment #5, should it be marked as INVALID? [[User:Batika|Batika]]
*{{Bug|147408}} - The testcase site provided by the reporter is a mess (php code in html and so on). Should it work at all?
*{{Bug|126941}} - Error compiling konq using icpc - is this supported? [[User:Njg234908|Njg234908]]
*{{Bug|149366}} - text-transform:lowercase not affecting input fields. This seems not to be working in other browsers (Firefox) [[Talavis|Talavis]]
*{{Bug|104656}} - the HTML is buggy, but should konqueror emulate firefox and other browsers here? [[User:Grundleborg|Grundleborg]]
*{{Bug|152285}} - there are some serious troubles regarding js with krugle.org in 4.0.3. Seems to work in 3.5.9, though. [[User:Krf|KRF]]
*{{Bug|115913}} - should be ok to close. feature doesnt exist in kde4 anymore but works ok for me in 3.5.9. Reporter complains about intented behaviour i think. [[User:Krf|KRF]]
*{{Bug|152860}} - Regression in KDE 4.x. [[User:Krf|KRF]]
*{{Bug|153041}} - Patch included.

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs no longer present in 4.x

2008-04-20T14:16:32Z

Krf:

===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|109907}} - Resolved in trunk [[User:krop|krop]]</s>
**Resolved in 3.5.9 as well, closing the bug. [[User:Nixeagle|Nixeagle]]
*{{Bug|109860}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|109694}} - Resolved in trunk [[User:krop|krop]]
*<s>{{Bug|109046}} - Resolved in trunk [[User:krop|krop]]</s>
**This works in konq 3.5.9, so I closed it. [[User:Nixeagle|Nixeagle]]
*{{Bug|108596}} - The original website doesn't exist anymore. [[User:krop|krop]]
*<s>{{Bug|110251}} - Resolved in trunk</s> [[User:krop|krop]]
*{{Bug|111585}} - Resolved in trunk [[User:krop|krop]]
**Confirmation that the bug was fixed in 3.5.9 is wanted [[User:Nixeagle|Nixeagle]]
***It's still there [[User:Talavis|Talavis]]
*{{Bug|111336}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|111125}} - Resolved in trunk [[User:krop|krop]]
*<s>{{Bug|110284}} - Resolved in trunk</s> [[User:krop|krop]]
**Works for me in 3.5.9 as well as 4.0.3. Closing. [[User:Nixeagle|Nixeagle]]
*<s>{{Bug|110225}} - Resolved in trunk</s> [[User:krop|krop]]
*{{Bug|112686}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
**lemma says it also works in 3.5.9 [[User:Nixeagle|Nixeagle]]
*{{Bug|112541}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|113507}} - Resolved in 4.0.3 - There is also a comment noting it works in 3.5.7. This should likely be closed. [[User:Nixeagle|Nixeagle]]
*{{Bug|115909}} - Resolved in trunk (r796129) [[User:Philrod|Philrod]]
*{{Bug|116804}} - Resolved in 4.0.3 - I personally can't reproduce it. However flash *may* be required to produce this. I don't have that installed at this time. (If this is the wrong section, please move this) [[User:Nixeagle|Nixeagle]]
*{{Bug|117245}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|116124}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|123490}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|123378}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|149466}} - Resolved in trunk and 3.5.9 [[User:Talavis|Talavis]]
*{{Bug|150294}} - Resolved in trunk and 3.5.9? [[User:Talavis|Talavis]]
*{{Bug|129631}} - Resolved in trunk and 3.5.9 [[User:Talavis|Talavis]]
*{{Bug|124422}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|124407}} - Resolved in 4.0.3, by comments on the bug, I infer its resolved in 3.5.x as well. [[User:Nixeagle|Nixeagle]]
*{{Bug|123278}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|124312}} - Resolved in 4.0.3 - Please note the bug is unconfirmed, but was confirmad at one time (A dev unconfirmed it again noting similar behavior to firefox). However the report is resolved so that it works as the filer wanted. [[User:Nixeagle|Nixeagle]]
*{{Bug|126416}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|149709}} - Resolved in trunk [[User:Talavis|Talavis]]
*{{Bug|125567}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|126285}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|101579}} - Resolved in 4.0.3 [[User:Batika|Batika]]
*{{Bug|104297}} - I think its resolved in trunk and 3.5.9, but someone needs to check my testcase is correct. [[User:Grundleborg|Grundleborg]]
*{{Bug|102795}} - Resolved in 4.0.3. [[User:Batika|Batika]]
*{{Bug|98542}} - CSS3 :first-line property work as expected. The bug seems fixed on trunk. [[User:finex|FiNeX]]
*{{Bug|104317}} - Resolved in trunk, still present in 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|104358}} - fixed in trunk but still present in 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|126785}} - not present in 4.0.3 [[User:Njg234908|Njg234908]]
*{{Bug|127344}} - not present in 4.0.3 [[User:Njg234908|Njg234908]]
*{{Bug|127345}} - not present in 4.0.3 [[User:Njg234908|Njg234908]]
*{{Bug|127152}} - not present in 4.0.3, or 3.5.7 - can be closed [[User:Njg234908|Njg234908]]
*{{Bug|152008}} - resolved in 4.0.3. [[User:Krf|KRF]]
*{{Bug|143641}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|142518}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|104438}} - Resolved in trunk and 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|113260}} - Resolved in 4.0.3 and 3.5.9. [[User:Krf|KRF]]
*{{Bug|152470}} - Resolved in 4.0.3 and 3.5.9. [[User:Krf|KRF]]
*{{Bug|153033}} - Resolved in 4.0.3. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing users with particular setups

2008-04-20T14:12:42Z

Krf:

===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|112476}} - Site problem - Someone with an older CPU should check this. It appears fixed using a newer CPU. [[User:Nixeagle|Nixeagle]]
*{{bug|124937}} - Looks like we need someone with "Microsoft Outlook Web Access" to even have a chance at reproducing this. [[User:Nixeagle|Nixeagle]]
*{{Bug|100604}} - needs a printer to test. [[User:Grundleborg|Grundleborg]]
*{{Bug|125613}} - needs a printer [[User:Nixeagle|Nixeagle]] - works for me on kde3 and kde4. [[User:Krf|KRF]]
*{{Bug|152624}} - What are orkuts? [[User:Krf|KRF]]
*{{Bug| 153017}} - Blogger account needed. [[User:Krf|KRF]]

User:Krf

2008-04-20T14:11:14Z

Krf: User:KRF moved to User:Krf

Homepage: http://electrostorm.net

User:KRF

2008-04-20T14:11:14Z

Krf: User:KRF moved to User:Krf

#REDIRECT [[User:Krf]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing users with particular setups

2008-04-20T14:10:43Z

Krf:

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing attention from Konqueror developers

2008-04-20T14:09:23Z

Krf:

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs no longer present in 4.x

2008-04-20T14:05:19Z

Krf:

===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|109907}} - Resolved in trunk [[User:krop|krop]]</s>
**Resolved in 3.5.9 as well, closing the bug. [[User:Nixeagle|Nixeagle]]
*{{Bug|109860}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|109694}} - Resolved in trunk [[User:krop|krop]]
*<s>{{Bug|109046}} - Resolved in trunk [[User:krop|krop]]</s>
**This works in konq 3.5.9, so I closed it. [[User:Nixeagle|Nixeagle]]
*{{Bug|108596}} - The original website doesn't exist anymore. [[User:krop|krop]]
*<s>{{Bug|110251}} - Resolved in trunk</s> [[User:krop|krop]]
*{{Bug|111585}} - Resolved in trunk [[User:krop|krop]]
**Confirmation that the bug was fixed in 3.5.9 is wanted [[User:Nixeagle|Nixeagle]]
***It's still there [[User:Talavis|Talavis]]
*{{Bug|111336}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|111125}} - Resolved in trunk [[User:krop|krop]]
*<s>{{Bug|110284}} - Resolved in trunk</s> [[User:krop|krop]]
**Works for me in 3.5.9 as well as 4.0.3. Closing. [[User:Nixeagle|Nixeagle]]
*<s>{{Bug|110225}} - Resolved in trunk</s> [[User:krop|krop]]
*{{Bug|112686}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
**lemma says it also works in 3.5.9 [[User:Nixeagle|Nixeagle]]
*{{Bug|112541}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|113507}} - Resolved in 4.0.3 - There is also a comment noting it works in 3.5.7. This should likely be closed. [[User:Nixeagle|Nixeagle]]
*{{Bug|115909}} - Resolved in trunk (r796129) [[User:Philrod|Philrod]]
*{{Bug|116804}} - Resolved in 4.0.3 - I personally can't reproduce it. However flash *may* be required to produce this. I don't have that installed at this time. (If this is the wrong section, please move this) [[User:Nixeagle|Nixeagle]]
*{{Bug|117245}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|116124}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|123490}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|123378}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|149466}} - Resolved in trunk and 3.5.9 [[User:Talavis|Talavis]]
*{{Bug|150294}} - Resolved in trunk and 3.5.9? [[User:Talavis|Talavis]]
*{{Bug|129631}} - Resolved in trunk and 3.5.9 [[User:Talavis|Talavis]]
*{{Bug|124422}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|124407}} - Resolved in 4.0.3, by comments on the bug, I infer its resolved in 3.5.x as well. [[User:Nixeagle|Nixeagle]]
*{{Bug|123278}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|124312}} - Resolved in 4.0.3 - Please note the bug is unconfirmed, but was confirmad at one time (A dev unconfirmed it again noting similar behavior to firefox). However the report is resolved so that it works as the filer wanted. [[User:Nixeagle|Nixeagle]]
*{{Bug|126416}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|149709}} - Resolved in trunk [[User:Talavis|Talavis]]
*{{Bug|125567}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|126285}} - Resolved in 4.0.3 [[User:Nixeagle|Nixeagle]]
*{{Bug|101579}} - Resolved in 4.0.3 [[User:Batika|Batika]]
*{{Bug|104297}} - I think its resolved in trunk and 3.5.9, but someone needs to check my testcase is correct. [[User:Grundleborg|Grundleborg]]
*{{Bug|102795}} - Resolved in 4.0.3. [[User:Batika|Batika]]
*{{Bug|98542}} - CSS3 :first-line property work as expected. The bug seems fixed on trunk. [[User:finex|FiNeX]]
*{{Bug|104317}} - Resolved in trunk, still present in 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|104358}} - fixed in trunk but still present in 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|126785}} - not present in 4.0.3 [[User:Njg234908|Njg234908]]
*{{Bug|127344}} - not present in 4.0.3 [[User:Njg234908|Njg234908]]
*{{Bug|127345}} - not present in 4.0.3 [[User:Njg234908|Njg234908]]
*{{Bug|127152}} - not present in 4.0.3, or 3.5.7 - can be closed [[User:Njg234908|Njg234908]]
*{{Bug|152008}} - resolved in 4.0.3. [[User:Krf|KRF]]
*{{Bug|143641}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|142518}} - Resolved in trunk [[User:krop|krop]]
*{{Bug|104438}} - Resolved in trunk and 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|113260}} - Resolved in trunk and 3.5.9. [[User:Krf|KRF]]
*{{Bug|152470}} - Resolved in trunk and 3.5.9. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing users with particular setups

2008-04-20T13:55:58Z

Krf:

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing users with particular setups

2008-04-20T13:52:25Z

Krf:

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing attention from Konqueror developers

2008-04-20T13:51:53Z

Krf:

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs awaiting feedback

2008-04-20T13:42:28Z

Krf:

===Bugs awaiting feedback===
'''NB. Feedback should only be requested for bugs if you have tried and failed to reproduce them or if the report contains insufficient information to try and reproduce the bug. Requesting feedback for a bug should be seen as a ''last resort'' only.'''

Bugs for which feedback has been requested, which should be revisited in 30 days to see if there's any response. Please list all bugs here for which feedback has been requested.
*{{Bug|122883}} - No way to reproduce this as the links for the testcase give 403 forbidden. I've asked for updated links if there are still some available. [[User:Nixeagle|Nixeagle]]
*{{Bug|103631}} - page no longer exists. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing users with particular setups

2008-04-20T13:41:09Z

Krf:

===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|112476}} - Site problem - Someone with an older CPU should check this. It appears fixed using a newer CPU. [[User:Nixeagle|Nixeagle]]
*{{bug|115913}} - Need a mouse with a middle mouse button. [[User:Nixeagle|Nixeagle]]
*{{bug|124937}} - Looks like we need someone with "Microsoft Outlook Web Access" to even have a chance at reproducing this. [[User:Nixeagle|Nixeagle]]
*{{Bug|100604}} - needs a printer to test. [[User:Grundleborg|Grundleborg]]
*{{Bug|125613}} - needs a printer [[User:Nixeagle|Nixeagle]]
*{{Bug|152287}} - needs someone with w32codecs and kaffeine installed. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs no longer present in 4.x

2008-04-20T13:33:12Z

Krf:

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing users with particular setups

2008-04-20T13:27:14Z

Krf:

===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|113260}} - google maps has problems printing. - requires a printer, which I don't have on my test setup. [[User:Nixeagle|Nixeagle]]
*{{bug|112476}} - Site problem - Someone with an older CPU should check this. It appears fixed using a newer CPU. [[User:Nixeagle|Nixeagle]]
*{{bug|115913}} - Need a mouse with a middle mouse button. [[User:Nixeagle|Nixeagle]]
*{{bug|124937}} - Looks like we need someone with "Microsoft Outlook Web Access" to even have a chance at reproducing this. [[User:Nixeagle|Nixeagle]]
*{{Bug|100604}} - needs a printer to test. [[User:Grundleborg|Grundleborg]]
*{{Bug|103631}} - needs working java in konqueror. [[User:Grundleborg|Grundleborg]]
*{{Bug|125613}} - needs a printer [[User:Nixeagle|Nixeagle]]
*{{Bug|152287}} - needs someone with w32codecs and kaffeine installed. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing attention from Konqueror developers

2008-04-20T13:21:44Z

Krf:

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs no longer present in 4.x

2008-04-20T12:54:22Z

Krf: add bug

Contribute/Bugsquad/BugDays/KonquerorDay2

2008-04-20T12:40:59Z

Krf: readd myself

==Introduction==
This day will happen in the future at some point, but feel free to start now. The aim is to carry on from where we left off on [[Contribute/Bugsquad/BugDays/06APR08|6th April Bug Day]]. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Konqueror.

'''The goal of this bug-day is to check for: simple step-by-step instructions, reproducibility, and most of all, come up with test-cases for reproducing the bugs. This will enable the Konqueror developers to deal with bugs more easily, and so have more time left to actually fix them.''' When you have added either a test-case or step-by-step instructions for the reproduction of a bug, please list it in the appropriate section below, so that a second triager can see if they can get your instructions/test-case to work correctly. [http://konqueror.kde.org/investigatebug/ This page] provides an excellent explanation of how to create a test-case. [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page] also has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Konqueror doesn't have as many duplicates as some applications, and we don't want to claim things are duplicates when they aren't. So do not look too hard for them, and '''make sure''' to double check them with someone else, preferably one of the developers before marking/closing.'''We especially don't want to create more work for developers!'''

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

You should either be working with Konqueror from KDE 4 (either 4.0.2 or newer is best or SVN trunk) for testing these bugs. In this case, it probably won't matter which one, because KHTML/KJS are aggressively forward-ported and back-ported, and you might find 4.0.x easier to compile.

You may need another browser to test things in.

===Testcases===
If you come across a bug with a testcase in the text, put it under the testcase section. If it isn't marked "testcase" in the title, make a note of that. Check that the testcase works! (And doesn't work!)

Most importantly, we need to [http://konqueror.kde.org/investigatebug/ create testcases]. These are time-consuming, but extremely useful and really help out developers. These are especially important if it is a site that is either a non-Western language or a site you need some sort of account for.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a major website doesn't work, that is important.
Let's keep track of them.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", it won't show up in developer's searches for 4.0 bugs! Change the version field to match what the other one says, i.e. to match version the bug was first reported in, or mark it below if you don't have bugzilla permissions. Do not update or change the version number (ex. from 3.5.2 to 4.0.2) if it is currently set as a number! Just make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build or which distro the packages come from).

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Add your comments even on bugzilla for a more complete feedback by users and developers.

==Details==

Please select a period of bugs from the [[#Division_of_Labour|Division of Labour]] section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. '''If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r795406||
|-
|[[User:krop|krop]]||svn trunk <s>r797569</s> <s>r.798035</s> r. 799086||
|-
|[[User:finex|FiNeX]]||svn trunk r797319 ||
|-
|[[User:Nixeagle|Nixeagle]] || KDE 4.0.3 Gentoo Linux ||
|-
|[[User:Frank78ac|frank78ac]] || svn trunk r798811 ||
|-
|[[User:Talavis|Talavis]] || svn trunk r798735 and 3.5.9 ||
|-
|[[User:lemma|lemma]] || svn trunk r798768 and 3.5.9 ||
|-
|[[User:Batika|Batika]] || KDE 4.0.3 Gentoo Linux ||
|-
|[[User:Njg234908|Njg234908]] || KDE 4.0.3 openSUSE ||
|-
|[[User:KRF|KRF]] || KDE 4.0.3 Kubuntu ||
|-
|[[User:Crvena_Zvezda|Crvena_Zvezda]] || KDE 4.0.3 Kubuntu 8.04 ||
|}

{{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 and then query bugs.kde.org for all bugs in that month. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.

The bugzilla query to use for this triage day can be [http://bugs.kde.org/query.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=konqueror&component=khtml&component=khtml+adblock&component=khtml+ecma&component=khtml+event&component=khtml+forms&component=khtml+image+part&component=khtml+parsing&component=khtml+part&component=khtml+printing&component=khtml+renderer&component=khtml+xml&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_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=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2003-01-01&chfieldto=2003-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&newqueryname=konq-triage-2003-01&namedcmd=2003-onwards found here]. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month !! No of bugs !! IRC Nickname !! Status
|-
|2005-02 || 14 ||[[User:finex|FiNeX]]|| working ||
|-
|2005-03 || 20 || [[User:Batika|Batika]] || in progress... ||
|-
|2005-04 || 16 || [[User:Grundleborg|Grundleborg]] || in progress ||
|-
|2005-07 || 10 ||[[User:krop|krop]]|| Done. {{Bug|109218}} left (kwallet is buggy atm) ||
|-
|2005-08 || 10 ||[[User:krop|krop]]|| Done. ||
|-
|2005-09 || 16 || [[User:Nixeagle|Nixeagle]] || done. Bugs I had issues with are at [[User:Nixeagle/konquerorbugs]]. I'd appreciate it if that page were updated as folks look at the bugs.||
|-
|2005-11 || 16 || [[User:Nixeagle|Nixeagle]] || done - any I did not finish are at [[User:Nixeagle/konquerorbugs]]
|-
|2006-03 || 17 || [[User:Nixeagle|Nixeagle]] || done - incomplete at [[User:Nixeagle/konquerorbugs]]
|-
|2006-04 || 19 || [[User:Nixeagle|Nixeagle]] || working
|-
|2006-05 || 20 || [[User:Njg234908|Njg234908]] || just starting
|-
|2006-06 || 21 || [[User:Crvena_Zvezda|Crvena_Zvezda]] || just starting
|-
|2006-07 || 16
|-
|2006-08 || 18
|-
|2006-09 || 23
|-
|2006-10 || 27
|-
|2006-11 || 25
|-
|2006-12 || 17
|-
|2007-01 || 26
|-
|2007-02 || 26 || [[User:lemma|lemma]] || starting out...
|-
|2007-03 || 25 ||[[User:krop|krop]]|| in progress... ||
|-
|2007-04 || 11
|-
|2007-05 || 20
|-
|2007-06 || 21
|-
|2007-07 || 16 || [[User:KRF|KRF]] || done
|-
|2007-08 || 12 || [[User:Talavis|Talavis]] || in progress
|-
|2007-09 || 9 || [[User:Talavis|Talavis]] || Done, unable to test: [[User:Talavis/konqbugs]]
|-
|2007-10 || 16
|-
|2007-11 || 21 || [[User:KRF|KRF]] || in progress
|-
|2007-12 || 23
|-
|2008-01 || 32
|-
|2008-02 || 28
|-
|2008-03 || 22
|-
|2008-04 || 2
|}

(Total bugs 615)

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.
:For those interested, this was implemented after a short discussion on IRC between grundleborg, blauzahl, _lemma, and myself (nixeagle).

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with test-cases Added}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with step-by-step instructions}}

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

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

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

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Non english locales}}

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/High Profile}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Needs more information}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs not related to today}}

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with test-cases Added

2008-04-20T12:37:51Z

Krf: add bug headers

===Bugs with test-cases Added===
Bugs that have had a test case (an example of how to reproduce the bug) added should be entered below.

*{{Bug|108442}} - Testcase added - Confirmed in trunk. Seems unrelated to Konqueror [[User:krop|krop]]
*{{Bug|109070}} - Testcase added - Confirmed in trunk. [[User:krop|krop]]
*{{Bug|112756}} - Test case was already there, however someone with the correct permissions needs to add [testcase] to the summary. [[User:Nixeagle|Nixeagle]]
**Added [testcase] [[User:Nixeagle|Nixeagle]]
*{{Bug|150165}} - Testcase already there, need [testcase] added to summary. Confirmed in trunk.[[User:Talavis|Talavis]]
**Added [testcase] [[User:Nixeagle|Nixeagle]]
*{{Bug|103250}} Testcase added - Confirmed in trunk. [[User:Grundleborg|Grundleborg]]
*{{Bug|103846}} - Testcase tag added - confirmed in trunk and 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|100647}} - Test case already present, need [testcase] added to summary [[User:Batika|Batika]]
**testcase tag added. [[User:Grundleborg|Grundleborg]]
*{{Bug|100805}} - Test case added, confirmed in 4.0.3. Modify summary [[User:Batika|Batika]]
*{{Bug|104259}} - Test case tag added. confirmed in trunk and 3.5.9 [[User:Grundleborg|Grundleborg]]
*{{Bug|128714}} - Test case. Confirmed in 4.0.3 [[User:Crvena_Zvezda|Crvena_Zvezda]]
*{{Bug|147960}} - Test case already present. [[User:Krf|KRF]]
*{{Bug|147789}} - Very detailed test case present. [[User:Krf|KRF]]
*{{Bug|147935}} - Test case present. [[User:Krf|KRF]]
*{{Bug|104396}} - Testcase tag added. Still present in trunk and 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|126778}} - still present in 4.0.3, testcase added - needs marking as [testcase] [[User:Njg234908|Njg234908]] - done. [[User:Krf|KRF]]
*{{Bug|127174}} - still present in 4.0.3, testcase added - needs marking as [testcase] [[User:Njg234908|Njg234908]] - done. [[User:Krf|KRF]]
*{{Bug|127027}} - still present in 4.0.3, has testcase but needs marking [testcase] [[User:Njg234908|Njg234908]] - done. [[User:Krf|KRF]]
*{{Bug|148343}} - Testcase tag added. Cant test though. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with test-cases Added

2008-04-20T12:34:05Z

Krf: add bug

===Bugs with test-cases Added===
Bugs that have had a test case (an example of how to reproduce the bug) added should be entered below.

*{{Bug|108442}} - Testcase added - Confirmed in trunk. Seems unrelated to Konqueror [[User:krop|krop]]
*{{Bug|109070}} - Testcase added - Confirmed in trunk. [[User:krop|krop]]
*{{Bug|112756}} - Test case was already there, however someone with the correct permissions needs to add [testcase] to the summary. [[User:Nixeagle|Nixeagle]]
**Added [testcase] [[User:Nixeagle|Nixeagle]]
*{{Bug|150165}} - Testcase already there, need [testcase] added to summary. Confirmed in trunk.[[User:Talavis|Talavis]]
**Added [testcase] [[User:Nixeagle|Nixeagle]]
*{{Bug|103250}} Testcase added - Confirmed in trunk. [[User:Grundleborg|Grundleborg]]
*{{Bug|103846}} - Testcase tag added - confirmed in trunk and 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|100647}} - Test case already present, need [testcase] added to summary [[User:Batika|Batika]]
**testcase tag added. [[User:Grundleborg|Grundleborg]]
*{{Bug|100805}} - Test case added, confirmed in 4.0.3. Modify summary [[User:Batika|Batika]]
*{{Bug|104259}} - Test case tag added. confirmed in trunk and 3.5.9 [[User:Grundleborg|Grundleborg]]
*{{Bug|128714}} - Test case. Confirmed in 4.0.3 [[User:Crvena_Zvezda|Crvena_Zvezda]]
*{{Bug|147960}} - Test case already present. [[User:Krf|KRF]]
*{{Bug|147789}} - Very detailed test case present. [[User:Krf|KRF]]
*{{Bug|147935}} - Test case present. [[User:Krf|KRF]]
*{{Bug|104396}} - Testcase tag added. Still present in trunk and 3.5.9. [[User:Grundleborg|Grundleborg]]
*{{Bug|126778}} - still present in 4.0.3, testcase added - needs marking as [testcase] [[User:Njg234908|Njg234908]]
*{{Bug|127174}} - still present in 4.0.3, testcase added - needs marking as [testcase] [[User:Njg234908|Njg234908]]
*{{Bug|127027}} - still present in 4.0.3, has testcase but needs marking [testcase] [[User:Njg234908|Njg234908]]
*{{Bug|148343}} - Testcase tag added. Cant test though. [[User:Krf|KRF]]

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with test-cases Added

2008-04-20T11:43:58Z

Krf: add bugs

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing attention from Konqueror developers

2008-04-20T11:00:46Z

Krf: add bug

Contribute/Bugsquad/BugDays/KonquerorDay2

2008-04-20T10:45:07Z

Krf: add myself

==Introduction==
This day will happen in the future at some point, but feel free to start now. The aim is to carry on from where we left off on [[Contribute/Bugsquad/BugDays/06APR08|6th April Bug Day]]. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Konqueror.

'''The goal of this bug-day is to check for: simple step-by-step instructions, reproducibility, and most of all, come up with test-cases for reproducing the bugs. This will enable the Konqueror developers to deal with bugs more easily, and so have more time left to actually fix them.''' When you have added either a test-case or step-by-step instructions for the reproduction of a bug, please list it in the appropriate section below, so that a second triager can see if they can get your instructions/test-case to work correctly. [http://konqueror.kde.org/investigatebug/ This page] provides an excellent explanation of how to create a test-case. [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page] also has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Konqueror doesn't have as many duplicates as some applications, and we don't want to claim things are duplicates when they aren't. So do not look too hard for them, and '''make sure''' to double check them with someone else, preferably one of the developers before marking/closing.'''We especially don't want to create more work for developers!'''

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

You should either be working with Konqueror from KDE 4 (either 4.0.2 or newer is best or SVN trunk) for testing these bugs. In this case, it probably won't matter which one, because KHTML/KJS are aggressively forward-ported and back-ported, and you might find 4.0.x easier to compile.

You may need another browser to test things in.

===Testcases===
If you come across a bug with a testcase in the text, put it under the testcase section. If it isn't marked "testcase" in the title, make a note of that. Check that the testcase works! (And doesn't work!)

Most importantly, we need to [http://konqueror.kde.org/investigatebug/ create testcases]. These are time-consuming, but extremely useful and really help out developers. These are especially important if it is a site that is either a non-Western language or a site you need some sort of account for.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. If a major website doesn't work, that is important.
Let's keep track of them.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", it won't show up in developer's searches for 4.0 bugs! Change the version field to match what the other one says, i.e. to match version the bug was first reported in, or mark it below if you don't have bugzilla permissions. Do not update or change the version number (ex. from 3.5.2 to 4.0.2) if it is currently set as a number! Just make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build or which distro the packages come from).

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

===Update bugzilla===
Add your comments even on bugzilla for a more complete feedback by users and developers.

==Details==

Please select a period of bugs from the [[#Division_of_Labour|Division of Labour]] section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. '''If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r795406||
|-
|[[User:krop|krop]]||svn trunk <s>r797569</s> r.798035||
|-
|[[User:finex|FiNeX]]||svn trunk r797319 ||
|-
|[[User:Nixeagle|Nixeagle]] || KDE 4.0.3 Gentoo Linux ||
|-
|[[User:Frank78ac|frank78ac]] || svn trunk r798811 ||
|-
|[[User:Talavis|Talavis]] || svn trunk r798735 and 3.5.9 ||
|-
|[[User:lemma|lemma]] || svn trunk r798768 and 3.5.9 ||
|-
|[[User:Batika|Batika]] || KDE 4.0.3 Gentoo Linux ||
|-
|[[User:Njg234908|Njg234908]] || KDE 4.0.3 openSUSE ||
|-
|[[User:KRF|KRF]] || KDE 4.0.3 Kubuntu ||
|}

{{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 and then query bugs.kde.org for all bugs in that month. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.

The bugzilla query to use for this triage day can be [http://bugs.kde.org/query.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=konqueror&component=khtml&component=khtml+adblock&component=khtml+ecma&component=khtml+event&component=khtml+forms&component=khtml+image+part&component=khtml+parsing&component=khtml+part&component=khtml+printing&component=khtml+renderer&component=khtml+xml&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_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=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2003-01-01&chfieldto=2003-01-31&chfieldvalue=&order=Reuse+same+sort+as+last+time&newqueryname=konq-triage-2003-01&namedcmd=2003-onwards found here]. Be sure to correct the dates to the month which you will triage before running the query.

{|
|-
!Month !! No of bugs !! IRC Nickname !! Status
|-
|2005-02 || 14 ||[[User:finex|FiNeX]]|| working ||
|-
|2005-03 || 20 || [[User:Batika|Batika]] || in progress... ||
|-
|2005-04 || 16 || [[User:Grundleborg|Grundleborg]] || in progress ||
|-
|2005-07 || 10 ||[[User:krop|krop]]|| Done. {{Bug|109218}} left (kwallet is buggy atm) ||
|-
|2005-08 || 10 ||[[User:krop|krop]]|| Done. ||
|-
|2005-09 || 16 || [[User:Nixeagle|Nixeagle]] || done. Bugs I had issues with are at [[User:Nixeagle/konquerorbugs]]. I'd appreciate it if that page were updated as folks look at the bugs.||
|-
|2005-11 || 16 || [[User:Nixeagle|Nixeagle]] || done - any I did not finish are at [[User:Nixeagle/konquerorbugs]]
|-
|2006-03 || 17 || [[User:Nixeagle|Nixeagle]] || done - incomplete at [[User:Nixeagle/konquerorbugs]]
|-
|2006-04 || 19 || [[User:Nixeagle|Nixeagle]] || working
|-
|2006-05 || 20 || [[User:Njg234908|Njg234908]] || just starting
|-
|2006-06 || 21
|-
|2006-07 || 16
|-
|2006-08 || 18
|-
|2006-09 || 23
|-
|2006-10 || 27
|-
|2006-11 || 25
|-
|2006-12 || 17
|-
|2007-01 || 26
|-
|2007-02 || 26 || [[User:lemma|lemma]] || starting out...
|-
|2007-03 || 25
|-
|2007-04 || 11
|-
|2007-05 || 20
|-
|2007-06 || 21
|-
|2007-07 || 16 || [[User:KRF|KRF]] || in progress
|-
|2007-08 || 12
|-
|2007-09 || 9 || [[User:Talavis|Talavis]] || working
|-
|2007-10 || 16
|-
|2007-11 || 21
|-
|2007-12 || 23
|-
|2008-01 || 32
|-
|2008-02 || 28
|-
|2008-03 || 22
|-
|2008-04 || 2
|}

(Total bugs 615)

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.
:For those interested, this was implemented after a short discussion on IRC between grundleborg, blauzahl, _lemma, and myself (nixeagle).

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with test-cases Added}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs with step-by-step instructions}}

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

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

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

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Non english locales}}

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

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/High Profile}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Needs more information}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs not related to today}}

User:Krf

2008-04-20T10:22:49Z

Krf: New page: Homepage: http://electrostorm.net

Homepage: http://electrostorm.net

Contribute/Bugsquad/BugDays/KonquerorDay2/Bugs needing version field changed

2008-04-20T10:18:57Z

Krf: resolved

===Bugs needing version field changed===
Bugs should be listed here if their version field is invalid and they are still present in KDE 4, so that the version field can be corrected.

*{{Bug|109497}} - Confirmed in trunk - No version specified [[User:krop|krop]] - done. [[User:KRF|KRF]]
*{{Bug|110947}} - Confirmed in trunk [[User:krop|krop]] - done. [[User:KRF|KRF]]
*{{Bug|111113}} - Confirmed in trunk [[User:krop|krop]] - done. [[User:KRF|KRF]]
*{{Bug|110513}} - Confirmed in trunk [[User:krop|krop]] - done. [[User:KRF|KRF]]
*{{Bug|100647}} - Confirmed in 4.0.3 [[User:Batika|Batika]] - done. [[User:KRF|KRF]]
*{{Bug|101279}} - Confirmed in 4.0.3. Probably the component should be also changed to Parsing. [[User:Batika|Batika]] - done. [[User:KRF|KRF]]