Bug 696016 - [abrt] kpackagekit-0.6.3.3-1.fc14: _int_malloc: Process /usr/bin/kpackagekit was killed by signal 11 (SIGSEGV)
Summary: [abrt] kpackagekit-0.6.3.3-1.fc14: _int_malloc: Process /usr/bin/kpackagekit ...
Keywords:
Status: CLOSED DUPLICATE of bug 693027
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0a48d843d07ff2f5ff433d1257a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-13 05:02 UTC by Kushagra Malviya
Modified: 2011-04-13 15:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-13 15:35:17 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (160.31 KB, text/plain)
2011-04-13 05:02 UTC, Kushagra Malviya 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.