I demand that David Barker may or may not have written...
I demand that David Barker may or may not have top-posted...
[snip]
Now I compiled it myself it doesn't really matter anyway, thanks though.
This is still a little odd. I don't see anything in there which would cause vdr's LIRC support (when enabled) to fail unless lircd isn't running; with my build of 1.3.24, it just works.
(I'm assuming that you got source for 1.2.6-12, 1.2.6-13 or my 1.3.24-1 via apt-get and that you rebuilt the packages by running 'debuild binary' or otherwise using the debian/rules file.)
BTW, don't top-post. Don't quote signatures or attachments (unless you're specifically referring to them)...
Sorry I don't know what top-posting is so if I am doing it again I apologise.
You did: it's the putting of *all* of the new text above the quoted text. You've also quoted everything (including my .sig) again; that's also considered to be bad practice.
Anyway I didn't use apt-get to get the source or anything debian specific, I just downloaded the source of the vdr homepage and compiled it the normal way. I think there is somthing wrong with the debian package because after compiling it myself it worked fine no problems.
<fiddles about a bit in a chroot>
Hmm. 1.2.6-13 "works" here with LIRC - it starts up happily then just sits there waiting for input which (apparently) never arrives, although that /could/ be a lircd problem. It definitely works in daemon mode.
[snip .sig - *don't* quote it!]