Bug 516055

Summary: Bash info not showing menus
Product: [Fedora] Fedora Reporter: Jerry James <loganjerry>
Component: texinfoAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 11CC: pertusus, vcrhonek
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-07 07:03:57 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 Jerry James 2009-08-06 14:47:54 UTC
Description of problem:
"info bash" shows pages with empty menus, and some other information missing.  Direct examination of /usr/share/info/bash.info.gz shows that the missing information is present in the file, but is not being displayed.  If I use the info reader built into XEmacs, the menus are displayed.  It's only the command-line "info" tool that is having this problem.  However, I am not having trouble with any other info pages, just bash's.  This may indicate some weirdness in the bash info pages, but if so, the XEmacs info reader can cope with the weirdness.

Version-Release number of selected component (if applicable):
info-4.13a-2.fc11.x86_64

How reproducible:
Always

Steps to Reproduce:
1. info bash
  
Actual results:
The top level page has an empty menu.  Other pages with menus also show empty menus.

Expected results:
The top level menu should have 14 entries; similarly for other pages with menus.

Additional info:

Comment 1 Jerry James 2009-08-06 15:13:44 UTC
I found another info page that illustrates the same problem: the top level one.  Just run "info".  I get a blank page instead of the menu of applications with installed info pages.

Comment 2 Vitezslav Crhonek 2009-08-07 07:03:57 UTC

*** This bug has been marked as a duplicate of bug 515402 ***