[Slackbuilds-users] gxine/lirc breaks Slackware

[David Chmelik]

In other words, I can't post on Slackware's LinuxQuestions thread about 
packages not building, because that's not the issue: there's no thread 
yet for otherwise broken.

On 12/25/25 3:26 PM, David Chmelik wrote:
> I have double-checked it's indeed in lirc-0.10.2-x86_64-1_SBo's 
> lib/udev/rules.d/60-lirc.rules.  I've just removed & rebuilt lirc 
> before testing.  I now realise that's only for Slackware-current, 
> which (unless you can tell me where such issues should be discussed) 
> may be beside the point, because it breaks for people using that and 
> if it not fixed will break Slackware 15.1-stable.
>
> On 12/25/25 11:42 AM, Jeremy Hansen wrote:
>> That file was updated after the release of lirc used on SBo. It does 
>> not contain that command.
>>
>> This is the version of the file included with the version on SBo.
>>
>> https://sourceforge.net/p/lirc/git/ci/5914451b1bc739713da22f12639ee6cf5ebcee08/tree/contrib/60-lirc.rules 
>> <https://sourceforge.net/p/lirc/git/ci/5914451b1bc739713da22f12639ee6cf5ebcee08/tree/contrib/60-lirc.rules> 
>>
>>
>> David doesn't seem to be using the version of lirc on SBo and updated 
>> it without telling the distro he updated it and then complained it 
>> was broken. Go figure...
>>
>> I am the maintainer of lirc (only because it was unmaintained and it 
>> was a hard dependency of kodi at the time). I haven't updated it due 
>> to reports of v0.10 breaking a lot of people's setups.
>>
>> All that being said, I do not use lirc, so if someone else who does 
>> use it wants to maintain it, I'm happy to relinquish maintainership.
>>
>> Jeremy
>>
>> On Thu, Dec 25, 2025, 2:30 PM fsLeg via SlackBuilds-users 
>> <slackbuilds-users at slackbuilds.org 
>> <mailto:slackbuilds-users at slackbuilds.org>> wrote:
>>
>>     Here's your problem:
>> <https://sourceforge.net/p/lirc/git/ci/master/tree/contrib/60-lirc.rules
>> <https://sourceforge.net/p/lirc/git/ci/master/tree/contrib/60-lirc.rules>>
>>
>>     The rule has been present in lirc sources for the past 10 years,
>>     according to the commit at blame date. I guess it says a lot about
>>     how many Slackware users use it, that's why it went unnoticed for
>>     so long.
>>
>>     Try contacting the script's maintainer so they could patch the
>>     rule in the SlackBuild. If they don't respond in a week or two you
>>     can submit the necessary change yourself after getting admins'
>>     approval here.
>>
>>     On December 25, 2025 21:43:56 GMT+03:00, David Chmelik
>>     <dchmelik at gmail.com <mailto:dchmelik at gmail.com>> wrote:
>>     >Whenever I connect certain types of devices, I get an error like
>>     "udevd[n]: failed to execute '/usr/bin/sh' '/usr/bin/sh -c
>>     '/usr/bin/setfacl -m g:lirc:rw /dev/bus/usb/001/004 2>/dev/null ||
>>     :'': No such file or directory" and the devices don't work.