Bug 700290

Summary: [abrt] kdebase-runtime-4.6.1-3.fc15: Process /usr/bin/kcmshell4 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: ewright2
Component: PackageKitAssignee: Richard Hughes <richard>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: jonathan, jreznik, kevin, ltinkl, rdieter, richard, rnovacek, ry, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:945648aa3c94443cba59489bf6f000c1af0130db
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-28 04:02:04 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 ewright2 2011-04-28 03:12:29 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 186593 bytes
cmdline: /usr/bin/kcmshell4 kpk_addrm
comment: I have not restarted the system after it rebooted during the install process.  I guess it's related to that.
component: kdebase-runtime
Attached file: coredump, 21385216 bytes
crash_function: QString::fromLatin1_helper(char const*, int)
executable: /usr/bin/kcmshell4
kernel: 2.6.38.2-9.fc15.x86_64
package: kdebase-runtime-4.6.1-3.fc15
rating: 4
reason: Process /usr/bin/kcmshell4 was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1303959365
uid: 500

How to reproduce
-----
1. Right after installing Fedora 15 beta.
2.
3.
Comment 1 ewright2 2011-04-28 03:12:33 UTC 
Created attachment 495384 [details]
File: backtrace
Comment 2 Kevin Kofler 2011-04-28 04:02:04 UTC 
"kcmshell4 kpk_addrm" is actually part of KPackageKit (kcmshell4 is in kdebase-runtime, but it only invokes the KCM). The crash is an already known infinite recursion in PackageKit-qt, already fixed upstream for weeks, but still not fixed in Fedora. :-(

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