|
Reporting Bugs |
|
Back to the main page
First, please look at the list of PackageKit bugs and to that of gnome-PackageKit bugs ,so that you are sure the bug you are reporting isn't a duplicate bug thatsomeone else has fixed or reported.If not present, then please create a new bug attaching all the informationto this new bug:
Please do not email individual developers with bug reports, as the volume ofemail we get is already huge.Bugzilla lets us keep it all the information in one place, so we don't loose track!
When PackageKit doesn't work, there is lots that could be wrong.To help us diagnose the problem, please supply the following information:
This will turn on verbose debugging for the PackageKit daemon that will beuseful when debugging problems.
sudo killall packagekitdsudo /usr/libexec/packagekitd --verbose
This will display your session user settings for the GNOME PackageKit Tools.
gconftool-2 -R /apps/gnome-packagekit
We would really appreciate it if you could send us more information about thecrash, specifically a backtrace with gdb.Make sure you have the packagekit-debuginfo or packagekit-gdb package installed,else the reports from gdb won't mean much to any of us.
gdb /usr/libexec/packagekitd
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 crashingthe daemon, for instance:
pkcon get updates
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 willgive you more information.
Back to the main page