Bug 696016

Summary: [abrt] kpackagekit-0.6.3.3-1.fc14: _int_malloc: Process /usr/bin/kpackagekit was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kushagra Malviya <kushagra1276>
Component: PackageKitAssignee: Richard Hughes <richard>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jonathan, kevin, ltinkl, rdieter, richard, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:0a48d843d07ff2f5ff433d1257aceeef4fbf1c18
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-13 15:35:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Kushagra Malviya 2011-04-13 05:02:51 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 164156 bytes
cmdline: /usr/bin/kpackagekit -caption KPackageKit -icon applications-other
comment: Smart packagekit backend is not functioning with kpackagekit.
component: kpackagekit
Attached file: coredump, 20242432 bytes
crash_function: _int_malloc
executable: /usr/bin/kpackagekit
kernel: 2.6.35.12-88.fc14.i686
package: kpackagekit-0.6.3.3-1.fc14
rating: 4
reason: Process /usr/bin/kpackagekit was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302670855
uid: 500

How to reproduce
-----
1.I changed th default backend to smart.
2.opened kpackagekit.
3.I click on any icon the application closes automatically.
Comment 1 Kushagra Malviya 2011-04-13 05:02:59 UTC 
Created attachment 491635 [details]
File: backtrace
Comment 2 Kevin Kofler 2011-04-13 15:35:17 UTC 
That's a PackageKit-qt bug, also reproducible with the yum backend under some conditions (but common operations work with the yum backend), already fixed upstream.

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