[mythtv-users] Upgraded to Fedora 22 and lirc is misbehaving

[Jerry]

On Wed, May 27, 2015 at 2:29 PM, Alec Leamas <leamas.alec at gmail.com> wrote:

> On 27/05/15 15:33, Hika van den Hoven wrote:
>
>> Hoi Jerry,
>>
>> Wednesday, May 27, 2015, 1:46:57 PM, you wrote:
>>
>>  On Tue, May 26, 2015 at 9:48 PM, Hika van den Hoven <hikavdh at gmail.com>
>>> wrote:
>>>
>>
>>  <big snip>
>>>
>>
>>  A few things. First about the rule. A single '=' means assign and a
>>>
>>>> double compare. So the rule should be:
>>>>
>>>> KERNEL=="lirc0", NAME=="lirc0", GROUP="lirc", MODE="0660"
>>>>
>>>> in stead of
>>>>
>>>> KERNEL=="lirc0", NAME=="lirc0", GROUP="lirc", MODE=="0660"
>>>>
>>>> Since the mode isn't 0660 it compares false and fails.
>>>>
>>>> Have you double checked that the group for user lirc is indeed lirc?
>>>>
>>>> Try to set the owner too. Also if I check, I only see KERNEL and
>>>> SUBSYSTEM and to be save change KERNEL to 'lirc*'. You can add a
>>>> DRIVERS part (e.g. DRIVERS=="lirc_serial" or whatever your driver is.
>>>> Check with: udevadm info --attribute-walk --name /dev/lirc0)
>>>>
>>>> KERNEL=="lirc*", SUBSYSTEM=="lirc", OWNER="lirc", GROUP="lirc",
>>>> MODE="0660"
>>>>
>>>>
>>  Hi Hika,
>>>
>>
>>  Okay, I changed the rule to the last one above, and it worked well,
>>> changing the permissions and ownership of /dev/lirc0.  The remote control
>>> only works when I set the MODE to 0666.  I don't know who is trying to
>>> access the device!  Maybe it is okay as 0666?
>>>
>>
>
> On a sane lirc setup the only thing accessing /dev/lirc0  is the lircd
> daemon.  The question is how this is run. Out of the top of my head I
> think the default configuration starts it as root:root, dropping it's
> privileges after opening devices and such.
>
> Have you modified the lircd.service setup e. g., by creating your own
> /etc/systemd/system/lircd.service? Or are you starting it by some other
> means? The default configuration is supposed top work out of the box w r
> t this.
>
> BTW, the distribution contains a similar rule as an example in the
> contrib/ directory. In the fedora package, this is /usr/share/lirc/contrib.
>
>
This is what I have right now:

[root at htpc ~]# more /usr/lib/systemd/system/lircd.service
[Unit]
Description=LIRC Infrared Signal Decoder
After=network.target

[Service]
Type=simple
ExecStart=/usr/sbin/lircd --nodaemon

[Install]
WantedBy=multi-user.target
[root at htpc ~]# ls /etc/systemd/system/lirc*
ls: cannot access /etc/systemd/system/lirc*: No such file or directory
[root at htpc ~]# more /etc/udev/rules.d/80-lirc.rules
KERNEL=="lirc0", SUBSYSTEM=="lirc", MODE="0666"
[root at htpc ~]#

looking in /usr/share/lirc/contrib:

[root at htpc contrib]# more 60-lirc.rules
# Installing this udev rule will make the /dev/lirc* devices accessible
# for users in the group "lirc". To enable, copy to /etc/udev/rules.d or
# /usr/lib/udev/rules.d.
KERNEL=="lirc[0-9]*", SUBSYSTEM=="lirc", GROUP="lirc", MODE="0660"
[root at htpc contrib]#

If I use the above rule, lircd doesn't function until I chmod to 0666.

Not to repeat myself, but just for clarity:

[root at htpc ~]# ps aux | grep lirc
lirc       877  0.0  0.0  57956  3828 ?        Ss   12:39   0:00
/usr/sbin/lircd --nodaemon
root     18449  0.0  0.0 114332  2392 pts/0    S+   15:20   0:00 grep
--color=auto lirc
[root at htpc ~]#

Thanks!
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20150527/46a22bbc/attachment.html>