Bug 663924

Summary: [abrt] gnome-packagekit-2.32.0-2.fc14: gpk_task_button_decline_cb: Process /usr/bin/gpk-update-viewer was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: halb_b
Component: gnome-packagekitAssignee: Richard Hughes <richard>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: richard
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7b610af67361dbfef2bcbc043860a6fe95367f92
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 15:09:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description halb_b 2010-12-17 11:21:37 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: gpk-update-viewer
comment: This happened as I was looking at software source/packages, etc. I think the Update Manager started on it's own right after networking was enabled. It's supposed to do that, right? I know it's not supposed to crash. But it's supposed to keep it's self up to date? I was planning a different set of packages. 
component: gnome-packagekit
crash_function: gpk_task_button_decline_cb
executable: /usr/bin/gpk-update-viewer
kernel: 2.6.35.6-45.fc14.i686
package: gnome-packagekit-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/gpk-update-viewer was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1292548882
uid: 500

How to reproduce
-----
1.Full install from 32bit Fedora DVD
2.Set up user/account details
3.System, Administration, Software Sources/Update Manager(started by it's self)
Comment 1 halb_b 2010-12-17 11:21:40 UTC 
Created attachment 469335 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 15:09:54 UTC 
Backtrace analysis found this bug to be similar to bug #710896, closing as duplicate.

Bugs which were found to be similar to this bug: bug #597337, bug #618464, bug #626019, bug #628251, bug #636430, bug #640508, bug #663332, bug #672042, bug #710896

This comment is automatically generated.

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