Debian Codegraph @

docs/html/pk-bugs.html

raw
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>PackageKit - 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 </head>
8 <body>
9
10 <table align="center" class="title">
11 <tr>
12 <td><img src="img/packagekit.png" alt=""/></td>
13 <td width="95%" valign="middle"><p class="title">Reporting Bugs</p></td>
14 <td><img src="img/packagekit.png" alt=""/></td>
15 </tr>
16 </table>
17
18 <p>Back to the <a href="index.html">main page</a></p>
19
20 <h1>Reporting Bugs</h1>
21
22 <p>
23 First, please look at the <a href="https://github.com/PackageKit/PackageKit/issues">list of PackageKit bugs</a>,
24 so that you are sure the bug you are reporting isn't a duplicate bug that
25 someone else has fixed or reported.
26 If not present, then please create a new bug attaching all the information
27 to this <a href="https://github.com/PackageKit/PackageKit/issues/new">new bug</a>.
28 </p>
29
30 <h2>General Bugs</h2>
31
32 <p>
33 When PackageKit doesn't work, there is lots that could be wrong.
34 To help us diagnose the problem, please supply the following information:
35 </p>
36
37 <ul>
38 <li>The version of packagekit installed</li>
39 <li>The installation method you used (i.e. f19 RPM, tarball)</li>
40 <li>Your distribution and version</li>
41 <li>The verbose trace from packagekitd</li>
42 <li>Any other information that may be relevant</li>
43 </ul>
44
45 <h2>packagekitd Verbose Trace</h2>
46
47 <p>
48 This will turn on verbose debugging for the PackageKit daemon that will be
49 useful when debugging problems.
50 </p>
51
52 <pre>
53 sudo killall packagekitd
54 sudo /usr/libexec/packagekitd --verbose
55 </pre>
56
57 <h2>Segfaults or random crashes</h2>
58 <p>
59 We would really appreciate it if you could send us more information about the
60 crash, specifically a backtrace with gdb.
61 Make sure you have the packagekit-debuginfo or packagekit-gdb package installed,
62 else the reports from gdb won't mean much to any of us.
63 </p>
64
65 <pre>
66 gdb /usr/libexec/packagekitd
67 </pre>
68 <p>
69 The GNU debugger (gdb) will start and put you at a prompt:
70 </p>
71 <pre>
72 (gdb) _
73 </pre>
74
75 <p>
76 Then type the following.
77 </p>
78
79 <pre>
80 (gdb) run --verbose
81 </pre>
82
83 <p>
84 In another command window, you may have to exeute the action that is crashing
85 the daemon, for instance:
86 </p>
87 <pre>
88 pkgcli list-updates
89 </pre>
90 <p>
91 You should be back in the gdb shell if the daemon has crashed.
92 Then type bt at the prompt and send us all the output that follows.
93 This will tell us exactly what the program was doing when it crashed.
94 </p>
95 <p>
96 This <a href="http://www.delorie.com/gnu/docs/gdb/gdb_toc.html">link</a> will
97 give you more information.
98 </p>
99
100 <h2>Enabling verbose logging by default</h2>
101 <p>
102 If you want verbose logging to be enabled by default, you can override the
103 systemd service like this:
104 </p>
105 <pre>
106 sudo systemctl stop packagekit.service
107 sudo cp /usr/lib/systemd/system/packagekit.service /etc/systemd/system
108 sudo vim /etc/systemd/system/packagekit.service # add --verbose
109 sudo systemctl daemon-reload
110 sudo systemctl restart packagekit.service
111 </pre>
112 <p>
113 <b>PLEASE NOTE:</b> Due to a bug you'll need to be using PackageKit >= 1.0.6
114 for this to work correctly.
115 </p>
116
117 <p>Back to the <a href="index.html">main page</a></p>
118
119 <p class="footer">
120 Copyright <a href="mailto:[email protected]">Richard Hughes 2007-2013</a><br/>
121 <a href="http://validator.w3.org/check/referer">Optimized</a>
122 for <a href="http://www.w3.org/">standards</a>.
123 </p>
124
125 </body>
126 </html>