Report a Bug

From Chakra | Wiki
Jump to: navigation, search
Tools-report-bug.pngReport a Bug
Have you found something that's not okay and should be fixed? Report it. We can't fix bugs we don't know. Here you'll find out where you should report bugs.

General Rules

  • If you experience crashes or general bugs, they are probably not Chakra-specific, so you should look for the upstream bug-tracker. For KDE Software Compilation applications you can use the KDE Bug Tracking System. You can look for the application in this wiki to find out its upstream source.
  • Don't just post your problems in the forum but create a bug report, it's easier for us to deal with that. Most packagers and developers don't read the forum so the chances of them spotting the issue is already slim.
  • If you experience a packaging bug, like file conflicts or a missing dependency or feature, use our Bug Tracker.
  • If you see anything in the Chakra website (wiki, CCR, etc.) that you think is not OK or could be improved, you can also report it in our Bug Tracker.

What to do

When an application crashes



In order to generate useful backtraces for some applications like Qt or Tribe, you will need their debugging symbols, which are in the repositories. Just append -debug to the package name.

For a developer, proper debug info is absolutely necessary to fix stuff, so you will need to provide them with a backtrace. By default, KDE Software Compilation applications should show the crash manager after a crash. If it's not such a application or the crash wizard is not working for you, you can run the following commands to generate a backtrace manually:

gdb <program executable>

In some cases, like Tribe's, you'll have to run gdb with sudo in front of it. After those commands make the program crash. Then run:

bt full

And attach the output of that command to the bug report.

See also

Ksnapshot.pngHow to take screenshots
Find out the best ways there are to take screenshots, useful when you want to report a bug or anything else.