Hide Forgot
Description of problem: type "man telnet" and get bad output Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. type "man telnet" 2. look at screen 3. sigh. Actual results: Text is there, but messed up. Expected results: Nice output. Additional info: According to Michal Actually /usr/share/man/man1/telnet.1.gz is fine. The problem seems to be that 'man telnet' is picking up /usr/kerberos/man/man1/telnet.1.gz and this file is not using 'mandoc' macros. I did not try to check what else in /usr/kerberos/man/man1/ will have similar issues. You can workaround for the time beeing by setting an explicit MANPATH in /etc/man.config with /usr/kerberos/man further down the pike. Currently 'man -w' shows /usr/kerberos/man on the leading position.
As the default path setup goes to the kerberos-ized version of telnet rather than the plain one, man's behavior of prefering the kerberos version is correct. changing to the responsible component.-
$ man /usr/kerberos/man/man1/tmac.doc.gz shows nothing $ man /usr/kerberos/man/man5/.k5login.5.gz is ok, but this manpage is hard to find $ man -k k5login k5login: nothing appropriate
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there haven't been any updates to the report in quite a long time now after we've requested additional information, we're assuming the problem is either no longer present in our current OS release, or that there is no longer any interest in tracking the problem. Setting status to "INSUFFICIENT_DATA", however if you still experience this problem after updating to our latest Fedora release and are still interested in Red Hat tracking the issue, and assisting in troubleshooting the problem, please feel free to provide the information requested above, and reopen the report. Thank you in advance.