Typically man pages are under subdirectores in that dir ie man1/man2/.... So it may be ignoring the top level directory by design. I don't have any man "files" in that top directory, there are just directories below it that have the actual man pages in it. It sounds like a rpm spec file is putting in the wrong place. On Mon, Dec 7, 2020 at 7:15 AM Patrick O'Callaghan <pocallaghan(a)gmail.com&gt; wrote: > > $ rpm -qd lutris > /usr/share/man/lutris.1 > [poc@Bree ~]$ man lutris > No manual entry for lutris > [poc@Bree ~]$ ls -l /usr/share/man/lutris.1 > -rw-r--r--. 1 root root 1433 Jul 19 00:02 /usr/share/man/lutris.1 > > I also ran 'mandb' just in case. No difference. > > poc > > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

On 12/7/20 2:15 PM, Patrick O'Callaghan wrote: No surprise. This man page is installed into a bogus directory, i.e. this is a packaging bug. File a bug against this package to have it fixed. Ralf

On Mon, Dec 7, 2020, 6:15 AM Patrick O'Callaghan <pocallaghan(a)gmail.comwrote: I ran into this yesterday. In my case i was doing 'man zram-genarator.conf' and also for a few bcc tools programs. No entry. Two Fedora 33 systems affected, Workstation and Server. But not a third Workstation. In the first case I reinstalled the zram-generator package. I noticed this kicked off a mandb process. Problem fixed. On the second machine I found a mandb rebuild service unit (I can't remember the exact name and I'm mobile at the moment) and just did 'sudo systemctl start mandbwhatever.service' and that also fixed it. What I don't know is why it broke in the first place. -- Chris Murphy

On Tue, 2020-12-08 at 19:19 +1100, Cameron Simpson wrote: There was already a report in BZ which hadn't been attended to. The maintainer says he'll fix it. https://bugzilla.redhat.com/show_bug.cgi?id=1887130 poc