colord - Reporting Bugs

Back to the main page

# Reporting Bugs

First, please look at the list of bugs so that you are sure the bug you are reporting is not a duplicate bug that someone else has fixed or reported. If not present, then please create a new bug attaching all the information to this new bug.

## General Bugs

When colord does not work, there is lots that could be wrong. To help us diagnose the problem, please open a bug and attach the following information:

- The version of colord installed
- The version of gnome-color-manager installed
- The installation method you used (i.e. distribution RPM, tarball)
- Your distribution and version
- The verbose debugging from colord
- Any other information that may be relevant

Alternatively, you can send an email to the mailing list, although you will have to subscribe beforehand.

## colord Verbose Trace

This will turn on verbose debugging for the colord daemon that will be useful when debugging problems.

    sudo killall colord
    sudo /usr/libexec/colord --verbose

## Segfaults or random crashes

We would really appreciate it if you could send us more information about the crash, specifically a backtrace with gdb. Make sure you have the colord-debuginfo or colord-gdb package installed, else the reports from gdb won't mean much to any of us.

    gdb /usr/libexec/colord

The GNU debugger (gdb) will start and put you at a prompt:

    (gdb) _

Then type the following.

    (gdb) run --verbose

In another command window, you may have to exeute the action that is crashing the daemon, for instance selecting a profile in the gnome-color-manager profile viewer.

You should be back in the gdb shell if the daemon has crashed. Then type bt at the prompt and send us all the output that follows. This will tell us exactly what the program was doing when it crashed.

This link will give you more information.

Back to the main page