Bug 149704

Summary: Konqueror segvs frequently
Product: Red Hat Enterprise Linux 3 Reporter: Jay Fenlason <fenlason>
Component: kdebaseAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: jfeeney
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:07:01 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:

Description Jay Fenlason 2005-02-25 16:00:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3) Gecko/20050104 Red Hat/1.4.3-3.0.7

Description of problem:
Browsing some web sites (including bugzilla.redhat.com and theregister.com, probably others) causes konqueror to segv on an irregular basis.

Version-Release number of selected component (if applicable):
kdebase-3.1.3-5.8

How reproducible:
Sometimes

Steps to Reproduce:
1.start konqueor
2.attempt to enter a new bug (like this one) at bugzilla.redhat.com, or middle click on a news article at theregister.com
3.observer that all konqueror windows close, and a "konqueror got a segv" window appears.
  

Actual Results:  konqueror windows close and segv dialog appears.

Expected Results:  Windows should stay open.  No segv.

Additional info:

this is on fenlason-desk.boston.redhat.com, a dual-ht xeon running up2date kernel, X, etc.  Window manager is ctwm.

Comment 1 RHEL Program Management 2007-10-19 19:07:01 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.