Bugs:KDE

From openSUSE

KDE Bugreports

General

For reporting bugs in KDE against opensuse.org, it is helpful to know which packages are installed. Some people have only the plain openSUSE release packages installed (sometimes with and sometimes without online updates) and others have upgraded from the KDE:KDE3 repository at opensuse.org. Some even run some experimental packages that might induce further bugs.

More information: Debugging KDE

Please make sure to include relevant information (your sources list if in doubt). You may first want to check for an existing bug report at bugs.kde.org to see if this is a non-opensuse specific bugreport. You can still report it to opensuse, though it might get delayed until a fix from upstream is available.

Useful Crash Reports

Crash backtraces should always get reported with installed -debuginfo packages. If the backtrace contains a text like " This backtrace appears to be of no use.", then you're either missing the debuginfo package or don't have the correct version installed. You can install them the moment you see dr. konqi come up - before you click in the "backtrace" tab, but you have to install them from the same installation medium you use (beta2 debuginfos do not fit to beta1 executables). Usually kdepim3-debuginfo, kdelibs3-debuginfo, kdebase3-debuginfo and qt3-debuginfo is all that is required though.

To report bugs against Factory or openSUSE beta versions you will need both the factory repo and its debuginfo repo configured - Betas don't have debuginfo packages. Install the corresponding package from Factory and its debuginfo and debugsource sub-packages and get a good backtrace with line numbers.

More information: KDE Crash Reporting Guide

Specific Hints and tricks

About the only useful logfile is $HOME/.xsession-errors - only for kdm/login issues there are some more, namely /var/log/messages, /var/log/kdm.log, /var/log/XFree86.0.log.

Debugging of kio_slaves (any problem with a protocol within konqueror for instance) is a bit more tricky. A description for this can be found here.

If you attach a gdb to a running process, remember that if the process has "[kdeinit]" in the name, the right executable is not e.g. dcopserver but kdeinit.