Report a Bug
From The Chakra Project - Wiki
Contents |
Some general advices/rules
- If you experience a packaging bug, like file conflicts or a missing dependency or feature, use our bugtracker
- Dont just post your problems in the forums but create a bugreport, its much easier for us to deal with that
- If you experience crashes or general bugs, use the KDE Bug Tracking System (our KDE 4 packages are 100% vanilla, so its no problem at all)
What to do when something crashes?
- Install the -debug packages and create a backtrace. More about that below.
How to generate proper backtraces?
For a developer, proper debug info is absolutely necessary to fix stuff... And we are making it easy for you If you want to create proper backtraces, install the minimum amount of debug symbols at first:
pacman -S kdemod-kdelibs-debug kdemod-kdebase-debug kdemod-kdebase-runtime-debug kdemod-kdebase-workspace-debug
Now, lets say you have found out that marble crashes under certain circumstances and you want to report a bug. Then you just need to install the debugging symbols for marble and the common kdeedu package:
pacman -S kdemod-kdeedu-marble-debug kdemod-kdeedu-common-debug
After installing the debug symbols you should get a proper backtrace...
This applies to all other KDE packages, just add the "-debug" suffix to the package name to get the debug symbols. And dont forget to install the common debug packages too...
If the program is not automatically showing the KDE-Debug-Dialog, you can run the following commands to generate a backtrace manually:
gdb <programname> (in case of tribe you need to run it with sudo infront)
run
Then make the program crash...
bt full
Attach the output of that command to the bugreport...