Public bug reported:
After observing various strange problems accessing the socket at
/run/lirc/lircd, I dug a little deeper and found that the socket is
occasionally missing. This can happen after lircd has just been started,
or in the socket-activatable phase when lircd.service is inactive
(governed by lircd.socket), meaning that a started service is not usable
and a non-started service cannot be socket-activated.
The above problems did not occur with an earlier version of the lirc
package (from Jammy), and seem to have been introduced with the line
'RuntimeDirectory=lirc' in /lib/systemd/system/lircd.service, which by
default causes the runtime directory to be removed when the service is
stopped, which seems to badly interact with socket activation (as it
tries to reuse/create that directory and/or socket).
I checked other packages' way of handling this case, and there actually
are a few that use socket activation inside a RuntimeDirectory. All of
them use an additional line 'RuntimeDirectoryPreserve=yes', which I
added to my lircd.service.
Seems to have fixed it, so I suggest to add this to the packaged
version.
Observed and fixed on: Ubuntu Questing (25.10), lirc 0.10.2-0.10build1
** Affects: lirc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2139559
Title:
lircd.service should have RuntimeDirectoryPreserve=yes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/2139559/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
