Acknowledgement sent
to Torsten Crass <torsten.crass@eBiology.de>:
New Bug report received and forwarded. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Fri, 03 Jul 2015 11:18:05 GMT) (full text, mbox, link).
Package: lirc
Version: 0.9.0~pre1-1.2
Severity: normal
Dear Maintainer,
I am using a home-brew serial receiver in conjunction with an All In One
URC 7730 remote control in DVD mode with preset 0695 for our HTPC. This
setup has served me well for almost 10 years, but since a couple of
weeks or so (unfortunately, I can't figure out since how long exactly),
lircd obviously has trouble recognizing the keys pressed on the remote.
mode2 still shows nice pulses and spaces, and so does xmode2, but irw
rarely ever outputs a recognized key press. (The system journal,
however, shows frequent "Ignoring spike" messages. Don't recall if I've
had those before, though.)
I also tried to re-create the lircd.conf file using irrecord, but this
failed for various reasons:
- A lircd.conf created when forcing irrecord into raw mode doesn't lead
to any recognized key presses.
- When not in raw mode, irrecord detects the remote to use either the
RC-5 or RC-6 protocol. In the former case, each attemt to record a key
press results in a "Something went wrong" message, while in the latter
case irrecord exits complaining about not having detected a toggle bit mask.
Frankly, I don't know for sure if this is a lirc problem since according
to the change log there were no changes in the lirc package since
January. To me it seems more likely that the trouble was introduces by
some other package (possibly used by lircd) when I did a system upgrade
(which I usually do about once a month). But since I don't have a clue
which package this might be, I am reporting this to the lirc bug tracker.
Best regards --
Torsten
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.0.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages lirc depends on:
ii libasound2 1.0.29-1
ii libc6 2.19-18
ii libftdi1 0.20-2
ii liblircclient0 0.9.0~pre1-1.2
ii libusb-0.1-4 2:0.1.12-25
ii lsb-base 4.1+Debian13+nmu1
lirc recommends no packages.
Versions of packages lirc suggests:
pn ir-keytable <none>
ii lirc-x 0.9.0~pre1-1.2
ii setserial 2.17-48
-- Configuration Files:
/etc/lirc/hardware.conf changed:
LIRCD_ARGS=""
LOAD_MODULES=true
DRIVER=""
DEVICE="/dev/lirc0"
MODULES="lirc_serial"
LIRCD_CONF=""
LIRCMD_CONF=""
/etc/lirc/lircd.conf changed:
begin remote
name Aiwa0695
bits 16
flags SPACE_ENC|CONST_LENGTH
eps 30
aeps 100
header 9002 4379
one 622 1607
zero 622 491
ptrail 622
pre_data_bits 16
pre_data 0x8E71
gap 107584
toggle_bit_mask 0x0
begin codes
power 0x52AD
1 0x827D
2 0x42BD
3 0xC23D
4 0x22DD
5 0xA25D
6 0x629D
7 0xE21D
8 0x12ED
9 0x926D
0 0x02FD
ch+ 0x26D9
ch- 0xA659
mute 0x56A9
vol+ 0xF609
vol- 0x0EF1
left 0x1AE5
right 0x9A65
up 0x6A95
down 0xEA15
ok 0x5AA5
menu 0xAA55
exit 0x2AD5
aspect 0x9669
rew 0xC639
pause 0x16E9
play 0x06F9
ffw 0x46B9
red 0x728D
green 0x8679
yellow 0x817E
blue 0x0AF5
end codes
end remote
-- no debconf information
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Thu, 05 Nov 2015 09:30:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Alec Leamas <leamas.alec@gmail.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Thu, 05 Nov 2015 09:30:04 GMT) (full text, mbox, link).
Contrary to all other lirc bugs, updating to latest upstream is most
likely not the silver bullet here.
My first thought is that this is a hardware problem. Things like
fluorescent light, bad batteries or simply something else broken in the
old remote. That irrecord doesn't work clearly indicates that the input
is broken.
The only thing between lircd and the remote is the kernel and the
hardware. I wouldn't rule out the kernel completely, but I'd check the
hardware first: If possible, try it against some other device, check
batteries, check for fluorescent light, change the distance...
To accept this as a lircd bug you would have to try another remote as
well. If it fails for two remotes there might be a bug. But as it
stands, I doubt it. All symptoms are as expected if the remote is broken.
Cheers!
--alec
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Sun, 26 Jun 2016 15:03:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Heinlein <aheinlein@gmx.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Sun, 26 Jun 2016 15:03:03 GMT) (full text, mbox, link).
I came acrosss this bug since it describes exactly my problem - except
that I can rule out any hardware fault.
My setup is working fine under Ubuntu 12.04 with Kernel 3.13 and LIRC
0.9.0. I installed Debian 8.5 on the same machine on another partition,
using the same lircd.conf and getting exactly the problems that are
describe above. I am using kernel 4.6 from jessie-backports.
I too have a One4All remote, namely URC-6440.
I would be glad to help solve this problem, as it is a real show-stopper.
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Mon, 27 Jun 2016 03:27:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Alec Leamas <leamas.alec@gmail.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Mon, 27 Jun 2016 03:27:04 GMT) (full text, mbox, link).
To: Andreas Heinlein <aheinlein@gmx.com>, 790969@bugs.debian.org
Subject: Re: [Pkg-lirc-maint] Bug#790969: Same here...
Date: Mon, 27 Jun 2016 05:25:49 +0200
On 26/06/16 17:01, Andreas Heinlein wrote:
> I came acrosss this bug since it describes exactly my problem - except
> that I can rule out any hardware fault.
>
> My setup is working fine under Ubuntu 12.04 with Kernel 3.13 and LIRC
> 0.9.0. I installed Debian 8.5 on the same machine on another partition,
> using the same lircd.conf and getting exactly the problems that are
> describe above. I am using kernel 4.6 from jessie-backports.
>
> I too have a One4All remote, namely URC-6440.
>
> I would be glad to help solve this problem, as it is a real show-stopper.
>
>
So, it's not about the hardware. The culprit is then most likely the
kernel, there are changes made in the IR subsystem.
Unfortunately, the 0.9.0 version is really old. The current version is
0.9.4, but this is not officially yet packaged for Debian. If you want
to help tracking down this the first step would be to update to 0.9.4 so
we have some fresh code to start with. The upstream release [1] contains
a debian source package which hopefully can be used to update.
However, be aware the 0.9.4 is quite a different beast than 0.9.0. In
particular, the configuration has changed. Please read the
debian/README.Debian file as a starter after unpacking the tarball as
described in README.md.
If you can reproduce the bug on 0.9.4 we have a reasonable start to
track this down. If we are lucky, the update might even solve the
problem. Don't hold your breath, though.
Cheers!
--alec
[1]
https://sourceforge.net/projects/lirc/files/LIRC/0.9.4/lirc-debian-src-0.9.4-1.1.tar.gz
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Sun, 03 Jul 2016 09:24:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Heinlein <aheinlein@gmx.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Sun, 03 Jul 2016 09:24:04 GMT) (full text, mbox, link).
Subject: Re: [Pkg-lirc-maint] Bug#790969: Same here...
Date: Sun, 3 Jul 2016 11:21:29 +0200
I did as described and could reproduce the bug. Both the debug messages
and irrecord claiming it cannot find any toggle mask. What now?
Greets,
Andreas
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Sun, 03 Jul 2016 09:48:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Alec Leamas <leamas.alec@gmail.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Sun, 03 Jul 2016 09:48:04 GMT) (full text, mbox, link).
Hi! On Phone now (sailing), back later -Alec
Andreas Heinlein <aheinlein@gmx.com> skrev: (3 juli 2016 11:21:29 CEST)
>I did as described and could reproduce the bug. Both the debug messages
>and irrecord claiming it cannot find any toggle mask. What now?
>
>Greets,
>Andreas
>
>_______________________________________________
>Pkg-lirc-maint mailing list
>Pkg-lirc-maint@lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-lirc-maint
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Fri, 08 Jul 2016 16:09:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Alec Leamas <leamas.alec@gmail.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Fri, 08 Jul 2016 16:09:08 GMT) (full text, mbox, link).
To: Andreas Heinlein <aheinlein@gmx.com>, 790969@bugs.debian.org
Subject: Re: [Pkg-lirc-maint] Bug#790969: Bug#790969: Same here...
Date: Fri, 8 Jul 2016 18:07:34 +0200
On 03/07/16 11:21, Andreas Heinlein wrote:
> I did as described and could reproduce the bug. Both the debug messages
> and irrecord claiming it cannot find any toggle mask. What now?
>
>
First, since the bug is present also on 0.9.4 I filed an upstream bug
[1]. If possible, I would appreciate if we could continue the discussion
there.
Secondly, the logical step would be to use and check the kernel the
original 3.16 jessie kernel - my gut feeling is that this is related to
the kernel.
Third: could you please record one or two buttons (a few presses of each
button) using mode2 and submit the mode2 output. Please mark each
recording with the button used, and insert some newlines or so between
each button press.
Cheers!
--alec
PS: Ashore just for a short time, returning to the sea ASAP. So, further
replies might take some time, sorry.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790969
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Wed, 27 Jul 2016 13:39:10 GMT) (full text, mbox, link).
Acknowledgement sent
to Alec Leamas <leamas.alec@gmail.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Wed, 27 Jul 2016 13:39:10 GMT) (full text, mbox, link).
Subject: Re: [Pkg-lirc-maint] Bug#790969: Bug#790969: Same here...
Date: Wed, 27 Jul 2016 15:35:10 +0200
On Fri, 8 Jul 2016 18:07:34 +0200 Alec Leamas <leamas.alec@gmail.com> wrote:
>
>
> On 03/07/16 11:21, Andreas Heinlein wrote:
> > I did as described and could reproduce the bug. Both the debug messages
> > and irrecord claiming it cannot find any toggle mask. What now?
> >
This might be a new change in the kernel output. See
https://bugzilla.redhat.com/show_bug.cgi?id=1360688. According to this,
it should work using kernel 4.4.7 or earlier.
Cheers!
--alec
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Sun, 23 Oct 2016 17:45:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Kolmodin <mk@kolmodin.net>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Sun, 23 Oct 2016 17:45:05 GMT) (full text, mbox, link).
... with this bug.
Given that it surfaces around kernel version 4.0, my first bet would be
that this is https://bugzilla.redhat.com/show_bug.cgi?id=1260862. It's
not hard to check, just look for the consecutive spaces described in the
bug.
This bug is fixed (really, worked around) in the latest LIRC packages in
experimental, see https://sourceforge.net/p/lirc/tickets/172/.
Unfortunately, the update is non-trivial with configuration changes.
Please let me know if you are still interested in hunting down this;
otherwise we need to close the bug.
Cheers
--alec
Information forwarded
to debian-bugs-dist@lists.debian.org, lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>: Bug#790969; Package lirc.
(Tue, 20 Dec 2016 11:51:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Alec Leamas <leamas.alec@gmail.com>:
Extra info received and forwarded to list. Copy sent to lirc Maintainer Team <pkg-lirc-maint@lists.alioth.debian.org>.
(Tue, 20 Dec 2016 11:51:02 GMT) (full text, mbox, link).
There are now updated lirc packages in stretch and sid. Assuming that
this is indeed about the kernel bug described above, the issue is
worked-around by them.
Of course, I would appreciate if there was more input on this bug. Will
close shortly otherwise.
Marked Bug as done
Request was from Alec Leamas <leamas.alec@gmail.com>
to control@bugs.debian.org.
(Sat, 14 Jan 2017 21:54:07 GMT) (full text, mbox, link).
Notification sent
to Torsten Crass <torsten.crass@eBiology.de>:
Bug acknowledged by developer.
(Sat, 14 Jan 2017 21:54:08 GMT) (full text, mbox, link).
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Sun, 12 Feb 2017 07:35:23 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.