Bug 558812

Summary: [abrt] crash in kdebase-runtime-4.3.4-2.fc12
Product: [Fedora] Fedora Reporter: palo.liska
Component: kdebase-runtimeAssignee: Than Ngo <than>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: fedora, jreznik, kevin, lorenzo, ltinkl, rdieter, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:7ce4f8eadfe877256b09850ddf17afc307cb0b75
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-28 01:43:12 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 palo.liska 2010-01-26 13:54:16 UTC 
abrt 1.0.3 detected a crash.

How to reproduce
-----
1.Running firefox in background.
2.Try to start Konqueror


Comment
-----
It is probably not systematic. It happend after more than 24 hours of
running fedora with firefox. 
See bug 558810 (https://bugzilla.redhat.com/show_bug.cgi?id=558810)

Attached file: backtrace
cmdline: /usr/libexec/kde4/drkonqi -display :0.0 --appname plasma-desktop --signal 11 --pid 1492 --appversion 0.3 --programname 'Plasma Plasma Wo' --bugaddress submit.org --startupid 0
component: kdebase-runtime
executable: /usr/libexec/kde4/drkonqi
kernel: 2.6.31.12-174.2.3.fc12.i686
package: kdebase-runtime-4.3.4-2.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 palo.liska 2010-01-26 13:54:18 UTC 
Created attachment 386833 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-02-18 22:53:08 UTC 
Thank you for taking the time to report this issue to us.  This is an issue which is best addressed by the upstream developers.

Please file a report at bugs.kde.org , and when done add the upstream report info to this report.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.
Comment 3 palo.liska 2010-02-19 08:18:57 UTC 
https://bugs.kde.org/show_bug.cgi?id=227635
Comment 4 Steven M. Parrish 2010-02-28 01:43:12 UTC 
Thanks for taking the time to report this upstream.  Will close this report as UPSTREAM and monitor the upstream report for a resolution.