Bug 216800

Summary: don't crash on info:octave
Product: Red Hat Enterprise Linux 5 Reporter: Matthias Clasen <mclasen>
Component: yelpAssignee: Matthew Barnes <mbarnes>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: desktop-bugs, ndai, zcerza
Target Milestone: ---Keywords: Desktop
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 5.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-28 06:05:17 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 Matthias Clasen 2006-11-22 01:05:03 UTC
first filed upstream at: http://bugzilla.gnome.org/show_bug.cgi?id=376861
fix is contained in 2.16.2

Comment 1 Matthias Clasen 2006-11-23 06:15:03 UTC
fixed in yelp-2.16.0-11.el5

Comment 2 RHEL Program Management 2006-11-28 02:38:23 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Zack Cerza 2006-12-06 21:42:51 UTC
It looks like we're not even shipping octave...

Comment 4 Nicole Dai 2006-12-18 09:24:22 UTC
I tried "yelp info:octave/yelp info:firefox/yelp info:gedit..." in the terminal
but did not find the crash in yelp-2.16.0-10.el5. There are some dependencies
when downgrade to lower version even if used --force. Is there anybody will
specify the problem version of yelp to avoid wasting time? Thanks in advance.

Comment 5 Nicole Dai 2006-12-28 06:03:44 UTC
Retested the test case got from Comment #4 in yelp-2.16.0-13.el5 on
RHEL5-Client-20061226.nightly and no crash was found. Resolve the bug now. Pls
feel free to reopen the bug if you get the same problem again.