Bug 10537

Summary:	warning in systemd journal because of incorrect udev rules for lirc
Product:	Mageia	Reporter:	Gilles Mouchard <gilles.mouchard>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	minor
Priority:	Normal	CC:	anssi.hannula, bittwister2, mageia, tmb
Version:	3	Keywords:	Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	lirc-0.9.0-9.mga3.src.rpm	CVE:
Status comment:

Description Gilles Mouchard 2013-06-15 23:05:58 CEST

Description of problem:

udev rule for lirc is not correct. Command journalctl shows the following message: 
Jun 15 21:44:06 ion systemd-udevd[355]: NAME="lirc/%n" ignored, kernel device nodes can not be renamed; please fix it in /usr/lib/udev/rules.d/lirc.rules:1

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


How reproducible:

Have lirc service started and a supported remote controller.
Run journalctl to see the systemd journal.

Steps to Reproduce:
1. Run journalctl to see the warning in the log
2.
3.

Proposed solutions:

The source of the problem is in /usr/lib/udev/rules.d/lirc.rules:
KERNEL=="lirc[0-9]*",   NAME="lirc/%n"

Kernel device can't be renamed and it should not be renamed because service lircd needs /dev/lirc0 not /dev/lirc/0. Symlink instead of renaming should fix the warning:
KERNEL=="lirc[0-9]*",   SYMLINK+="lirc/%n"


Reproducible: 

Steps to Reproduce:

Comment 1 Bit Twister 2013-06-16 00:01:32 CEST

(In reply to Gilles Mouchard from comment #0)
> 
> Proposed solutions:
> 
> Kernel device can't be renamed and it should not be renamed because service
> lircd needs /dev/lirc0 not /dev/lirc/0. Symlink instead of renaming should
> fix the warning:
> KERNEL=="lirc[0-9]*",   SYMLINK+="lirc/%n"

Making the change still does not create a device /dev/ :(

# cat /usr/lib/udev/rules.d/lirc.rules
KERNEL=="lirc[0-9]*",   SYMLINK+="lirc/%n"

# ll /dev/lir*
ls: cannot access /dev/lir*: No such file or directory

# systemctl status lircd
lircd.service - LIRC Infrared Signal Decoder
          Loaded: loaded (/usr/lib/systemd/system/lircd.service; enabled)
          Active: active (running) since Sat, 2013-06-15 16:35:38 CDT; 21min ago
         Process: 1827 ExecStart=/usr/sbin/lircd --driver=default --device=/dev/lirc0 (code=exited, status=0/SUCCESS)
        Main PID: 1832 (lircd)
          CGroup: name=systemd:/system/lircd.service
                  â 1832 /usr/sbin/lircd --driver=default --device=/dev/lirc0

systemd[1]: Starting LIRC Infrared Signal Decoder...
lircd-0.9.0[1832]: lircd(default) ready, using /var/run/lirc/lircd
systemd[1]: Started LIRC Infrared Signal Decoder.
lircd-0.9.0[1832]: accepted new client on /var/run/lirc/lircd
lircd-0.9.0[1832]: could not get file information for /dev/lirc0
lircd-0.9.0[1832]: default_init(): No such file or directory
lircd-0.9.0[1832]: Failed to initialize hardware
Jun 15 16:38:52 mtv.home.test lircd-0.9.0[1832]: removed client

CC: (none) => junk_no_spam
Hardware: i586 => All

Manuel Hiebel 2013-07-09 09:33:42 CEST

Component: Release (media or process) => RPM Packages
Keywords: (none) => Triaged
CC: sysadmin-bugs => anssi.hannula, mageia, tmb

Comment 2 Anssi Hannula 2014-02-09 16:30:06 CET

I'm sorry for the delay.

I've removed the rule, since /dev/lirc0 is what is supposed to be used now.

There is an update/testing request for mga4, bug #12685.
I don't think I'll be making an update for mga3 for this, but I'll keep this open just in case.

Bit Twister, your issue is a different one, please report a separate bug if you are still experiencing it.

Comment 3 Marja Van Waes 2015-03-31 16:03:48 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 4 Gilles Mouchard 2015-03-31 16:29:09 CEST

Mageia 4 is probably not affected by the bug because the warnings no longer appears in journalctl output.
Thanks.