Bug 216800 - don't crash on info:octave
Summary: don't crash on info:octave
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yelp
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Matthew Barnes
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-22 01:05 UTC by Matthias Clasen
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version: 5.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-28 06:05:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 376861 0 None None None Never

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