Bug ID | 1026958 |
---|---|
Summary | man not working as expected |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 42.2 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Documentation |
Assignee | fs@suse.com |
Reporter | dieter.jurzitza@t-online.de |
QA Contact | fs@suse.com |
Found By | --- |
Blocker | --- |
When attempting to access manpages an unexpected behavior can be observed on leap 42.2. man systemd.mount brings "Kein Handbucheintrag f�r systemd.mount vorhanden" man 5 systemd.mount brings the expected, the manpage for systemd.mount. The file exists and can be found in the apropriate location /usr/share/man/man5/systemd.mount.5.gz. The permissions are as expected. I cannot observe this on leap 42.1. The file /etc/manpath.conf do not differ between leap-42.1 and leap-42.2, this cannot be the reason. Moreover, MANPATH shows identical results on both systems. Downgrading man from the version on leap-42.2 to the version on leap-42.1 does not help. The strange thing: some manpages may be accessed sometimes, for example man auto.master may work, sometimes even systemd.mount is functional, but in the very moment I start a new xterm and say man systemd.mount or man auto.master it doesn't work any more. man 5 systemd.mount works always as readily mentioned, however, this implies you know the section where the corresponding manpage can be found - this should not be required. Thank you for looking into this, regards Dieter Jurzitza