Bug 662278

Summary: [abrt] gnome-packagekit-2.91.3-2.fc15: Process /usr/bin/gpk-distro-upgrade was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Iván Jiménez <icj>
Component: gnome-packagekitAssignee: Richard Hughes <richard>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: bigslowfat, matthew.hooper, rhughes, richard
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:a951ff42f6c46c75bfd22a2dc897a5bc0482a356
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-26 10:29:01 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 Iván Jiménez 2010-12-11 05:45:32 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: gpk-distro-upgrade
component: gnome-packagekit
executable: /usr/bin/gpk-distro-upgrade
kernel: 2.6.37-0.rc5.git2.1.fc15.i686
package: gnome-packagekit-2.91.3-2.fc15
reason: Process /usr/bin/gpk-distro-upgrade was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1292078672
uid: 500

How to reproduce
-----
1.
2.
3.
just clicked on icon to run it
Comment 1 Iván Jiménez 2010-12-11 05:45:34 UTC 
Created attachment 468115 [details]
File: backtrace
Comment 2 Matt Hooper 2010-12-19 23:01:04 UTC 
Package: gnome-packagekit-2.91.3-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Rawhide)


How to reproduce
-----
1. Ran the operating system upgrade program and received a "Unsupported daemon version message"
2. I clicked Next anyway and the application crashed
3.
Comment 3 bsfmig 2011-01-07 12:18:44 UTC 
Package: gnome-packagekit-2.91.3-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Rawhide)


How to reproduce
-----
It seems to be related to preupgrade...
Comment 4 Richard Hughes 2011-04-26 10:29:01 UTC 

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