Thanks for the 10.2 referral. Sorry for veering off a bit here. I've seen set_transmitters. What I don't understand is how to define multiple devices and drivers in (presumably) lirc_options.conf. I suppose those would be transmitter 1 2, etc. based on the order defined? I may also need to connect to another upstream machine. Here's my conf file. [lircd] nodaemon = False driver = usb_uirt_raw #devinput device = /dev/serial/by-id/usb-FTDI_USB-UIRT-if00-port0 #auto output = /var/run/lirc/lircd pidfile...
Here's what I see for that library: sudo apt list | grep libsystemd-dev librust-libsystemd-dev/oldstable 0.2.1-2 arm64 librust-libsystemd-dev/oldstable 0.2.1-2 armhf libsystemd-dev/oldstable-security 247.3-7+deb11u6 arm64 libsystemd-dev/oldstable-security 247.3-7+deb11u6 armhf I guess the library's installed. Maybe there's a permissions issue? I need to use sudo a lot. Anyway, as per my 2023-10-14 note above. I got it working. Actually, the IR messages are generated on an upstream ubuntu x86 machine...
Here's what I see for that library: sudo apt list | grep libsystemd-dev librust-libsystemd-dev/oldstable 0.2.1-2 arm64 librust-libsystemd-dev/oldstable 0.2.1-2 armhf libsystemd-dev/oldstable-security 247.3-7+deb11u6 arm64 libsystemd-dev/oldstable-security 247.3-7+deb11u6 armhf I guess the library's installed. Maybe there's a permissions issue? I need to use sudo a lot. Anyway, as per my 2023-10-14 note above. I got it working. Actually, the IR messages are generated on an upstream ubuntu x86 machine...
Here's what I see for that library: sudo apt list | grep libsystemd-dev librust-libsystemd-dev/oldstable 0.2.1-2 arm64 librust-libsystemd-dev/oldstable 0.2.1-2 armhf libsystemd-dev/oldstable-security 247.3-7+deb11u6 arm64 libsystemd-dev/oldstable-security 247.3-7+deb11u6 armhf I guess the library's installed. Maybe there's a permissions issue? I need to use sudo a lot. Anyway, as per my 2023-10-14 note above. I got it working. Actually, the IR messages are generated on an upstream ubuntu x86 machine...
Here's what I see for that library: sudo apt list | grep libsystemd-dev librust-libsystemd-dev/oldstable 0.2.1-2 arm64 librust-libsystemd-dev/oldstable 0.2.1-2 armhf libsystemd-dev/oldstable-security 247.3-7+deb11u6 arm64 libsystemd-dev/oldstable-security 247.3-7+deb11u6 armhf I guess the library's installed. Maybe there's a permissions issue? I need to use sudo a lot. Anyway, as per my 2023-10-14 note above. I got it working. Actually, the IR messages are generated on an upstream ubuntu x86 machine...
Here's what I see for that library: sudo apt list | grep libsystemd-dev librust-libsystemd-dev/oldstable 0.2.1-2 arm64 librust-libsystemd-dev/oldstable 0.2.1-2 armhf libsystemd-dev/oldstable-security 247.3-7+deb11u6 arm64 libsystemd-dev/oldstable-security 247.3-7+deb11u6 armhf I guess the library's installed. Maybe there's a permissions issue? I need to use sudo a lot. Anyway, as per my 2023-10-14 note above. I got it working. Actually, the IR messages are generated on an upstream ubuntu x86 machine...
I see that the Milestone for this fix is Future. However, the changed daemons/lircd.cpp file may be found here. I downloaded and replaced the copy in the 0.10.2 distribution tarball with this one and irsend no longer hangs when using --count=2 (or greater). Thank you for the fix!
After changing the Type=notice to Type=simple in lircd.service, the daemon starts and stays running using sudo systemctl start lircd. irsend --count=4 xxx yyy works. This was based on using ./configure --bindir=/bin --sbindir=/usr/sbin --libexecdir=/usr/libexec --sysconfdir=/etc --libdir=/var/lib --datarootdir=/usr/share on a RasPi 4 running Raspberry OS. Now on to trying the installation on an x86 box running ubuntu.