On Tue, 13 Feb 2018 21:54:19 +0100 Alec Leamas
wrote:
>
> This message really says it all: using irrecord with the devinput
> driver is a useless and dangerous idea. See my other replies in the bug
> for more.
>
>
This is bug is outdated and partly off-topic. Closing. That is not to
say
On Sun, 11 Feb 2018 10:07:02 -0800 James Bottomley
wrote:
> I'm getting this same segfault as well. My old remote fell apart, so I
> was trying to train the IR receiver on a new one (well, the unused VCR
> section of the current TV remote.
> This is what I
I'm getting this same segfault as well. My old remote fell apart, so I
was trying to train the IR receiver on a new one (well, the unused VCR
section of the current TV remote.
This is what I get:
Starting program: /usr/bin/irrecord -d /dev/lirc0 -f
[Thread debugging using libthread_db enabled]
On Sun, 24 Sep 2017, Alec Leamas wrote:
[...]
> I note that you seemingly havn't used mode2 (?) This is the tool to determine
> what kind of data the kernel makes available to lirc which in the end
> determines what driver to use. This is described in the configuration guide.
I ran it at some
On 24/09/17 16:12, Francois Gouget wrote:
Now as to why I have driver=devinput in lirc_options.conf, it's because
it's the only way I found to get my remote to work. Setting
driver=default driver does not work and if I only provide
devinput.lircd.conf and no Hauppauge_PVR350.conf file then it
On Sun, 24 Sep 2017, Alec Leamas wrote:
[...]
> > But it's not 100% reproducible now, particularly when I try to use
> > my own libirrecord.so so I have debugging symbols. What I can give you
> > though is the irrecord backtrace:
> >
> > #0 0x in ?? ()
> > #1 0x7f5644aaae73
On 24/09/17 03:50, Francois Gouget wrote:
Actually it's the -f option that causes the crash. I can reproduce it
with:
# irrecord -f /tmp/foo.conf
This would just indicate that foo.conf is broken somehow. Given the
state of lirc, I don't think it's feasible to make it handle any kind of
On Fri, 15 Sep 2017, Alec Leamas wrote:
[...]
> > As before I get:
> > # irrecord -H devinput -f -d /dev/input/event13 /tmp/foo.conf
>
> This is actually not sane, and a prominent note is displayed when you start
> irrecord like this [1]
Actually it's the -f option that causes the crash. I can
Hi!
On Tue, 22 Aug 2017 17:06:29 +0200 (CEST) Francois Gouget
wrote:
> On Fri, 18 Aug 2017, Gianfranco Costamagna wrote:
>
> > Hello,
> >
> > > Dear Maintainer,
> > >
> > > When trying to create a configuration file for my remote, irrecord
> > > crashes when it gets to the
On Fri, 18 Aug 2017, Gianfranco Costamagna wrote:
> Hello,
>
> > Dear Maintainer,
> >
> > When trying to create a configuration file for my remote, irrecord
> > crashes when it gets to the 'Now hold down button Xxx' step:
> can you please try 0.10.0 from unstable?
I tried with 0.10.0-2 but I'm
On Fri, 18 Aug 2017 22:38:15 +0200 Gianfranco Costamagna
wrote:
> Hello,
>
> > Dear Maintainer,
> >
> > When trying to create a configuration file for my remote, irrecord
> > crashes when it gets to the 'Now hold down button Xxx' step:
> can you please try 0.10.0 from
Hello,
> Dear Maintainer,
>
> When trying to create a configuration file for my remote, irrecord
> crashes when it gets to the 'Now hold down button Xxx' step:
can you please try 0.10.0 from unstable?
thanks
signature.asc
Description: OpenPGP digital signature
Package: lirc
Version: 0.9.4c-9
Severity: important
Dear Maintainer,
When trying to create a configuration file for my remote, irrecord
crashes when it gets to the 'Now hold down button Xxx' step:
# /etc/init.d/lircd stop
[] Stopping lircd (via systemctl): lircd.serviceWarning: Stopping
13 matches
Mail list logo