Bug 600417 - [abrt] crash in gnome-packagekit-2.30.1-1.fc13: Process /usr/bin/gpk-update-viewer was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-packagekit-2.30.1-1.fc13: Process /usr/bin/gpk-update-v...
Keywords:
Status: CLOSED DUPLICATE of bug 642506
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-packagekit
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:756565f393984560f4e001e728e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-04 16:34 UTC by fred
Modified: 2010-11-09 14:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:38:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.19 KB, text/plain)
2010-06-04 16:34 UTC, fred
no flags Details

Description fred 2010-06-04 16:34:41 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gpk-update-viewer
component: gnome-packagekit
crash_function: gpk_update_viewer_get_details_cb
executable: /usr/bin/gpk-update-viewer
global_uuid: 756565f393984560f4e001e728e0c94d95a80df7
kernel: 2.6.33.3-85.fc13.i686
package: gnome-packagekit-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/gpk-update-viewer was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Started 'Software Update' in the Control Centre
2. Updates were available and proceeded to update
3. Update manager crashed upon nearing completion

Comment 1 fred 2010-06-04 16:34:44 UTC
Created attachment 421288 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:38:08 UTC

*** This bug has been marked as a duplicate of bug 642506 ***

Comment 3 Karel Klíč 2010-11-09 14:38:08 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #642506.

Sorry for the inconvenience.


Note You need to log in before you can comment on or make changes to this bug.