Bug 13977 - Error reading man page /usr/share/man/man8/lircd.8.xz
Summary: Error reading man page /usr/share/man/man8/lircd.8.xz
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Anssi Hannula
QA Contact:
URL:
Whiteboard: MGA6TOO
Keywords: 6sta2, Triaged
Depends on:
Blocks:
 
Reported: 2014-08-24 00:54 CEST by Bit Twister
Modified: 2020-08-02 22:15 CEST (History)
2 users (show)

See Also:
Source RPM: lirc-0.10.0-2.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2014-08-24 00:54:33 CEST 
Description of problem:

# man lircd
fgets: No such file or directory
Error reading man page /usr/share/man/man8/lircd.8.xz
No manual entry for lircd

# dir /usr/share/man/man8/lircd*
-rw-r--r-- 1 root root   32 Aug 23 15:12 /usr/share/man/man8/lircd.8.xz

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. urpmi lirc
2. man lircd



Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-11-01 19:43:57 CET

Keywords: (none) => Triaged
Assignee: bugsquad => anssi.hannula

Comment 1 Samuel Verschelde 2015-05-20 00:00:04 CEST 
Is it still valid?

Keywords: (none) => NEEDINFO

Comment 2 Bit Twister 2015-05-20 01:33:03 CEST 
Yup.

Source RPM: lirc-0.9.1a-1.mga5.src.rpm => lirc-0.9.1a-3.mga5.src.rpm
Keywords: NEEDINFO => (none)

Rémi Verschelde 2015-05-20 08:21:01 CEST

Summary: 5a2: Error reading man page /usr/share/man/man8/lircd.8.xz => Error reading man page /usr/share/man/man8/lircd.8.xz
Whiteboard: (none) => MGA5TOO

Comment 3 Bit Twister 2015-07-01 11:13:50 CEST 
Just verifying problem valid on Release 5.
Comment 4 Herbert Poetzl 2015-07-13 06:57:03 CEST 
Yep, i can confirm this.

Note that e.g. /etc/lirc/lirc_options.conf refers to lircd(8) which is empty, i.e. gives:

fgets: No such file or directory
Error reading man page /usr/share/man/man8/lircd.8.xz
No manual entry for lircd

Best,
Herbert

CC: (none) => herbert

Bit Twister 2016-07-06 22:49:41 CEST

Summary: Error reading man page /usr/share/man/man8/lircd.8.xz => 6_s1: Error reading man page /usr/share/man/man8/lircd.8.xz

Bit Twister 2017-01-23 19:55:08 CET

Summary: 6_s1: Error reading man page /usr/share/man/man8/lircd.8.xz => Error reading man page /usr/share/man/man8/lircd.8.xz
Source RPM: lirc-0.9.1a-3.mga5.src.rpm => lirc-0.9.1a-4.mga6.src.rpm
Status comment: (none) => 6_s2

Bit Twister 2017-01-31 18:48:48 CET

Status comment: 6_s2 => (none)
Keywords: (none) => 6sta2

Comment 5 Bit Twister 2017-10-12 11:58:55 CEST 
Works in cauldron

Source RPM: lirc-0.9.1a-4.mga6.src.rpm => lirc-0.10.0-2.mga7.src.rpm
Whiteboard: MGA5TOO => MGA5TOO MGA6TOO
Version: Cauldron => 6

Bit Twister 2018-09-05 01:09:25 CEST

Whiteboard: MGA5TOO MGA6TOO => MGA6TOO

Comment 6 Aurelien Oudelet 2020-08-02 22:15:35 CEST 
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien
Note You need to log in before you can comment on or make changes to this bug.