| 1 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| 2 |
<html xmlns="http://www.w3.org/1999/xhtml"> |
| 3 |
<head> |
| 4 |
<title>colord - Reporting Bugs</title> |
| 5 |
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> |
| 6 |
<link rel="stylesheet" href="style.css" type="text/css" media="screen"/> |
| 7 |
<link rel="shortcut icon" href="favicon.ico"/> |
| 8 |
</head> |
| 9 |
<body> |
| 10 |
|
| 11 |
<p>Back to the <a href="index.html">main page</a></p> |
| 12 |
|
| 13 |
<h1>Reporting Bugs</h1> |
| 14 |
|
| 15 |
<p> |
| 16 |
First, please look at the |
| 17 |
<a href="https://bugs.freedesktop.org/buglist.cgi?product=colord"> |
| 18 |
list of bugs</a> so that you are sure the bug you are reporting is not |
| 19 |
a duplicate bug that someone else has fixed or reported. |
| 20 |
If not present, then please create a new bug attaching all the information |
| 21 |
to this new bug. |
| 22 |
</p> |
| 23 |
|
| 24 |
<h2>General Bugs</h2> |
| 25 |
|
| 26 |
<p> |
| 27 |
When colord does not work, there is lots that could be wrong. |
| 28 |
To help us diagnose the problem, please |
| 29 |
<a href="https://bugs.freedesktop.org/enter_bug.cgi?product=colord">open a bug</a> |
| 30 |
and attach the following information: |
| 31 |
</p> |
| 32 |
|
| 33 |
<ul> |
| 34 |
<li>The version of colord installed</li> |
| 35 |
<li>The version of gnome-color-manager installed</li> |
| 36 |
<li>The installation method you used (i.e. distribution RPM, tarball)</li> |
| 37 |
<li>Your distribution and version</li> |
| 38 |
<li>The verbose debugging from colord</li> |
| 39 |
<li>Any other information that may be relevant</li> |
| 40 |
</ul> |
| 41 |
<p> |
| 42 |
Alternatively, you can send an email to the <a href="http://lists.freedesktop.org/mailman/listinfo/colord"> |
| 43 |
mailing list</a>, although you will have to subscribe beforehand. |
| 44 |
</p> |
| 45 |
|
| 46 |
<h2>colord Verbose Trace</h2> |
| 47 |
|
| 48 |
<p> |
| 49 |
This will turn on verbose debugging for the colord daemon that will be |
| 50 |
useful when debugging problems. |
| 51 |
</p> |
| 52 |
|
| 53 |
<pre> |
| 54 |
sudo killall colord |
| 55 |
sudo /usr/libexec/colord --verbose |
| 56 |
</pre> |
| 57 |
|
| 58 |
<h2>Segfaults or random crashes</h2> |
| 59 |
<p> |
| 60 |
We would really appreciate it if you could send us more information about the |
| 61 |
crash, specifically a backtrace with gdb. |
| 62 |
Make sure you have the colord-debuginfo or colord-gdb package installed, |
| 63 |
else the reports from gdb won't mean much to any of us. |
| 64 |
</p> |
| 65 |
|
| 66 |
<pre> |
| 67 |
gdb /usr/libexec/colord |
| 68 |
</pre> |
| 69 |
<p> |
| 70 |
The GNU debugger (gdb) will start and put you at a prompt: |
| 71 |
</p> |
| 72 |
<pre> |
| 73 |
(gdb) _ |
| 74 |
</pre> |
| 75 |
|
| 76 |
<p> |
| 77 |
Then type the following. |
| 78 |
</p> |
| 79 |
|
| 80 |
<pre> |
| 81 |
(gdb) run --verbose |
| 82 |
</pre> |
| 83 |
|
| 84 |
<p> |
| 85 |
In another command window, you may have to exeute the action that is crashing |
| 86 |
the daemon, for instance selecting a profile in the gnome-color-manager profile viewer. |
| 87 |
</p> |
| 88 |
<p> |
| 89 |
You should be back in the gdb shell if the daemon has crashed. |
| 90 |
Then type bt at the prompt and send us all the output that follows. |
| 91 |
This will tell us exactly what the program was doing when it crashed. |
| 92 |
</p> |
| 93 |
<p> |
| 94 |
This <a href="http://sources.redhat.com/gdb/current/onlinedocs/gdb_toc.html">link</a> will |
| 95 |
give you more information. |
| 96 |
</p> |
| 97 |
<p>Back to the <a href="index.html">main page</a></p> |
| 98 |
|
| 99 |
<p class="footer"> |
| 100 |
Copyright <a href="mailto:[email protected]">Richard Hughes 2011 - 2013</a><br/> |
| 101 |
<a href="http://validator.w3.org/check/referer">Optimized</a> |
| 102 |
for <a href="http://www.w3.org/">standards</a>. |
| 103 |
</p> |
| 104 |
|
| 105 |
</body> |
| 106 |
</html> |