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

[Alec Leamas]

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.


Cheers!

--alec