Bug 1545264

Summary: Man stops working because MANPATH is set to /usr/share/lmod/lmod/share/man:.:.
Product: [Fedora] Fedora Reporter: Dmitry Tantsur <dtantsur>
Component: LmodAssignee: Orion Poplawski <orion>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: jeff.backus, orion, tmz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Lmod-7.7.35-1.fc28 Lmod-7.7.35-1.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-11 20:16:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dmitry Tantsur 2018-02-14 13:49:08 UTC
Description of problem:
I cannot access any man pages, "man <anything>" returns "No manual entry for <anything>". On further investigation I realized that my MANPATH is set to /usr/share/lmod/lmod/share/man:.:. and I don't know where this is coming from.

Version-Release number of selected component (if applicable):
Lmod-7.5.16-3.fc27

How reproducible:
Always

Steps to Reproduce:
1. "man bash"

Actual results:
"No manual entry for bash"

Expected results:
The man page for bash

Additional info:
Just removing Lmod does not help, I will try logging in and out now.

Comment 1 Dmitry Tantsur 2018-02-14 13:50:29 UTC
Yep, removing Lmod and logging out helped me get my 'man' command back.

Comment 2 Todd Zullinger 2018-05-17 16:31:40 UTC
Removing Lmod removes python{2,3}-sphinx, but only because Lmod provides the 'environment(modules)' dependency they both need.  That dep is also provided by environment-modules package.  I haven't looked into why the sphinx packages require 'environment(modules)' or whether Lmod provides what they need.

I had removed the environment-modules package while testing #1578587.

Comment 3 Todd Zullinger 2018-05-17 17:06:13 UTC
Upstream Lmod issue https://github.com/TACC/Lmod/issues/348 addressed the double colon, but that doesn't fix bash-completion.  There is a fix in bash-completion upstream, referenced in issue https://github.com/scop/bash-completion/issues/160.

The bash-completion patch was applied to the master and f28 branches to fix #1495055.

Apologies if this is unrelated, as I didn't catch the ":.:." instead of "::" in the MANPATH until just now.

Comment 4 Fedora Update System 2018-06-22 03:58:18 UTC
Lmod-7.7.35-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-306294687a

Comment 5 Fedora Update System 2018-06-22 03:58:26 UTC
Lmod-7.7.35-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0b87a81978

Comment 6 Fedora Update System 2018-06-22 13:47:40 UTC
Lmod-7.7.35-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-306294687a

Comment 7 Fedora Update System 2018-06-22 15:53:03 UTC
Lmod-7.7.35-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0b87a81978

Comment 8 Fedora Update System 2018-07-11 20:16:31 UTC
Lmod-7.7.35-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2018-09-11 14:52:55 UTC
Lmod-7.7.35-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.