Peter Pumpkin

Had the machine on standby for about 20 hours to test whether or not my issue is the same as [#279] - tried it out, no dice. Only double clicking buttons "wakes" the driver up to future inputs.

Trying it out on my VM at the moment. Am I correct in assuming that making a stacktrace requires you to "make" lirc from source?

This is definitely a bug. Could you please produce a stacktrace as described therein? I'll get on it. This might be a duplicate of [#279] Would it be possible for me to build the current build of 0.10 and test it out to see whether or not it actually was [#279]?

Thank you for your continued support! I tried using irrecord before. Specifically as a means of testing the functionality of the default driver versus the devinput driver - with the default driver specified the binary recognized the IR signals, with devinput it gave out complete radio silence and quit itself because of that silence. I followed your advice and tried making a new lircd.conf using this command "sudo irrecord --driver default --device /dev/lirc0" first on the VM, then on the actual machine....

Thank you for your continued support! I tried using irrecord before. Specifically as a means of testing the functionality of the default driver versus the devinput driver - with the default driver specified the binary recognized the IR signals, with devinput it gave out complete radio silence and quit itself because of that silence. I followed your advice and tried making a new lircd.conf using this command "sudo irrecord --driver default --device /dev/lirc0" first on the VM, then on the actual machine....

Thank you for your continued support! I tried using irrecord before. Specifically as a means of testing the functionality of the default driver versus the devinput driver - with the default driver specified the binary recognized the IR signals, with devinput it gave out complete radio silence and quit itself because of that silence. I followed your advice and tried making a new lircd.conf using this command "sudo irrecord --driver default --device /dev/lirc0" first on the VM, then on the actual machine....

Thank you for your continued support! I tried using irrecord before. Specifically as a means of testing the functionality of the default driver versus the devinput driver - with the default driver specified the binary recognized the IR signals, with devinput it gave out complete radio silence and quit itself because of that silence. I followed your advice and tried making a new lircd.conf using this command "sudo irrecord --driver default --device /dev/lirc0" first on the VM, then on the actual machine....

It mentions that since 0.9.4, devinput driver is only supposed to work with remotes that are supported by the kernel, and mine is not (that's why I created a custom config). I started using LIRC in Septermber 2015, and ran fine up until May 2017, when I updated to Zesty. May it be possible that in Zesty the Ubuntu team started "shipping" LIRC 0.9.4, where before it was an older version? I'm gasping at straws, I know, but after reading the guide again, there seems to be nothing else that would mess...