Bug 700290 - [abrt] kdebase-runtime-4.6.1-3.fc15: Process /usr/bin/kcmshell4 was killed by signal 11 (SIGSEGV)
Summary: [abrt] kdebase-runtime-4.6.1-3.fc15: Process /usr/bin/kcmshell4 was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 693027
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:945648aa3c94443cba59489bf6f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-28 03:12 UTC by ewright2
Modified: 2011-04-28 04:02 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-28 04:02:04 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (182.22 KB, text/plain)
2011-04-28 03:12 UTC, ewright2 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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