On Wed, 28 Jun 2017 10:53:12 +0200 Alec Leamas
wrote:
> On Wed, 21 Jun 2017 09:44:28 +0200 Alec Leamas
> wrote:
> > This is tracked in upstream bug
> https://sourceforge.net/p/lirc/tickets/295/
> >
> > --alec
>
>
> Fixed upstream and in experimental. Thanks for reporting and debugging!
>
On Wed, 21 Jun 2017 09:44:28 +0200 Alec Leamas
wrote:
> This is tracked in upstream bug
https://sourceforge.net/p/lirc/tickets/295/
>
> --alec
Fixed upstream and in experimental. Thanks for reporting and debugging!
--alec
This is tracked in upstream bug https://sourceforge.net/p/lirc/tickets/295/
--alec
It seems the message "lircmd.cpp":394: Bad file descriptor" was misleading.
You are right the commandline option --uinput is not needed. The
--uinput option is also read from config file.
But when this opition is used, no lircm filedescriptor is correctly
initialized in daemons/lircmd.cpp
On Sat, 15 Apr 2017 06:37:28 +0200 Alec Leamas
wrote:
> I cannot reproduce this... something is missing. Could you please expand
> on what you did to get this message?
Ping?
Cheers!
--alec
On 14/04/17 11:18, Bernd Schumacher wrote:
I want to use lircmd
After making sure that lirc works to control vdr and kodi, I configured lircmd
in /etc/lirc/lirc_options.conf
[lircmd]
uinput = True
nodaemon= False
After starting "systemctl start lircmd", lircmd started withou
Package: lirc
Version: 0.9.4c-9
Severity: important
Dear Maintainer,
I want to use lircmd
After making sure that lirc works to control vdr and kodi, I configured lircmd
in /etc/lirc/lirc_options.conf
[lircmd]
uinput = True
nodaemon= False
After starting "systemctl start lircmd
7 matches
Mail list logo