Description of problem: When I walked up to my machine this morning, I found a bug-buddy message saying that gpk-update-icon had crashed. See this bug report on the Gnome bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=551692 Version-Release number of selected component (if applicable): gnome-packagekit-0.2.5-2.fc9.i386 How reproducible: unknown Additional info: See the Gnome bugzilla report for the bug-buddy output. A search on this bugzilla turns up two other gpk-update-icon crash reports: bug 451730, bug 457382. I don't know whether they're related.
Can you install the ggnome-packagekit-debuginfo package please, and then try to reproduce. Without that, the backtrace is nearly useless. Thanks.
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.
I can reproduce this bug reliably on Fedora 9. How to reproduce: 1. Log into GNOME session 2. Lock screen 3. Wait patiently for a few (2-3?) minutes 4. Move the mouse, and a login prompt will not appear 5. Switch to a VT and log in as root 6. ps axf | grep bug to verify bug-buddy is showing a window for gpk-update-icon 7. ps axf | grep screensaver 8. kill (pid of gnome's screensaver) 9. VT switch back to Gnome desktop 10. Cancel the auth prompt window for refreshing package lists 11. Click on button for bug buddy to save report. Details: Original bug buddy reports had a large amount of hexadecimal spew on threads and states. After upgrading to gnome-packagekit-debuginfo bug-buddy report is close to nothing due to a ptrace gripe (see attached bug buddy report). Please advise on further data collection steps. Having the screensaver lock out my GUI because gpk-update-icon has caused a focus grab for auth purposes is a hassle.
Created attachment 330501 [details] bug-buddy report that's useless due to ptrace EPERM,