Are others having double key presses with lirc-0.9.3-2? [solved]

graysky · 2015-10-01 20:27:50

The purpose of this post is to see if the problem I describe is unique to my hardware [remote] or more general. Are other Archers experiencing the sensitivity issue I describe below upon updating?

Issue: upon updating to lirc-1:0.9.3-2, my streamzap remote is experiencing key presses that are often but not always echoed twice to applications. Under previous versions of lirc, it worked flawlessly. Since the python rebulds, I have rebuild 1:0.9.2a-1 myself against the current packages which solves this sensitivity problem; I can confirm this on several different machines using the same remote and remote config file (which has been working flawlessly for years).

I also posted to the upstream ML but am holding off opening a bug against our package until someone upstream can weigh in.

Thank all!

Last edited by graysky (2015-10-06 07:40:51)

snakebite · 2015-10-03 14:19:54

I'm also experiencing something like this. What I'm seeing is that sometimes when I press a button, the previous button is repeated, eg. down, ok is sometimes seen as down, down, ok, no matter what the interval between the two button presses are.

FTR I'm using a Logitech Harmony 200 emulating an Xbox MCE.

Downgrading to lirc-0.9.2.a-1 solves the issue for me.

graysky · 2015-10-03 14:50:25

OK. Thank you for the report. Glad to see it is more than me and my hardware. Opened FS#46550 to get the devs to see this.

Last edited by graysky (2015-10-03 18:38:39)

Ttz_ztT · 2015-10-03 14:53:53

I have the same problem.

And i can confirm that downgrading to lirc-0.9.2.a-1 helps.

I'm using an atric ir device via lirc_serial.

Last edited by Ttz_ztT (2015-10-03 14:54:21)

snakebite · 2015-10-03 15:09:16

I've just completed a git bisect and the offending commit is 78a2e110a355849d7fa0a51225e26ae9501d3285. If you're still on their mailing list that would probably be a good place to mention that. I'll mention it on the FS bug.

graysky · 2015-10-03 15:27:12

I will post your observations about that commit. I am ignorant to the bisect process. If you revert that commit and compile 0.9.3 with that reverted, do you get the expected behavior? I am away from home now so I can't try it myself.

snakebite · 2015-10-03 15:37:27

Yep, reverted the commit against latest master and the remote behaves as expected.

graysky · 2015-10-03 18:38:14

Posted and thank you for tracking it down: https://sourceforge.net/p/lirc/mailman/ … /34512064/

EDIT: AH! Reverting that commit and building against 0.9.3 doesn't fix it for me

Last edited by graysky (2015-10-03 18:42:34)

snakebite · 2015-10-03 19:37:06

I tried the same revert against 0.9.3 and the issue still appears solved for me.

Here's the exact patch and PKGBUILD I used: lirc.tar.gz

If that still doesn't work you could try doing git bisect on your own and see if you somehow come up with a different commit. Maybe there are other bugs that cause similar issues for different remotes.

graysky · 2015-10-03 23:45:43

@snakebite - I built your package but it doesn't help with my issue I have no idea how to do a bisect, can you point me to a good guide or post your shell history or something?

snakebite · 2015-10-04 08:54:27

http://git-scm.com/docs/git-bisect has a fairly straight forward guide to bisecting.

Start the bisect with

$ git bisect start master lirc-0_9_2a

then just run

$ git bisect bad

or

$ git bisect good

after each build until it tells you it's done.

I had to clean the directory between builds to avoid build errors so do something like this on each build (note that the git clean command deletes anything not tracked by git):

$ git clean -fdx
$ sh autogen.sh
$ ./configure --sysconfdir=/etc
$ make
$ sudo daemons/lircd --nodaemon

graysky · 2015-10-04 10:06:39

So you're running lircd from the git repo without installing it to the filesystem. On my machine without the lirc package installed, I get errors trying to run the freshly compiled lircd:

% sudo ./daemons/lircd --nodaemon
Warning: cannot open /etc/lirc/lirc_options.conf
Driver `default' not found (wrong or missing -U/--plugindir?).

snakebite · 2015-10-04 10:20:51

You need to have the package installed since it removes the config files when you uninstall it. By running it from the repo you don't have to create and install a new package for every build you want to test. As long as the lirc services aren't running there shouldn't be any problems testing it this way.

graysky · 2015-10-04 10:34:39

Actually, I just needed the conf files in /etc/lirc and I needed to edit lirc_options.conf like this:

#plugindir       = /usr/lib/lirc/plugins
plugindir       = /scratch/lirc/plugins/.libs

graysky · 2015-10-04 10:39:54

EDIT: removed incorrect statement.

Last edited by graysky (2015-10-04 11:12:45)

graysky · 2015-10-04 10:56:54

I am getting build errors on the `make` step now after a series of "good bisects"

130 facade@desk /scratch/lirc (git)-[3869b68...|bisect] % git bisect good
Bisecting: 4 revisions left to test after this (roughly 2 steps)
[7c68069f6c35ffb78e39f58e24084850d5bf9949] lircd: Set supplementary groups (RH bz 1253907).
% ./autogen.sh
<< no errors>>
% ./configure --prefix=/usr --sbindir=/usr/bin --sysconfdir=/etc --localstatedir=/var
<< no errors>>
% make -j9
...
make[2]: *** No rule to make target 'lirc.org/images/marb18.jpg', needed by 'all-am'.  Stop.
make[2]: *** Waiting for unfinished jobs....
src=$(echo  ./man/lircmd.8 | /usr/bin/sed 's|/man/|/man-source/|'); \
    /usr/bin/sed "s/@version@/0.9.3pre2/" <$src >man/lircmd.8
src=$(echo  ./man/lircd.conf.5 | /usr/bin/sed 's|/man/|/man-source/|'); \
    /usr/bin/sed "s/@version@/0.9.3pre2/" <$src >man/lircd.conf.5
src=$(echo  ./man/lircrcd.8 | /usr/bin/sed 's|/man/|/man-source/|'); \
    /usr/bin/sed "s/@version@/0.9.3pre2/" <$src >man/lircrcd.8
src=$(echo  ./man/mode2.1 | /usr/bin/sed 's|/man/|/man-source/|'); \
    /usr/bin/sed "s/@version@/0.9.3pre2/" <$src >man/mode2.1
make[2]: Leaving directory '/scratch/lirc/doc'
Makefile:633: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/scratch/lirc'
Makefile:429: recipe for target 'all' failed
make: *** [all] Error 2

Complete make log: https://gist.github.com/graysky2/22b92f480ed032afe39d

...so I appear to be stuck.

EDIT: I ran make with the -k flag and was able to build a running lircd so I will continue...

Last edited by graysky (2015-10-04 11:06:22)

snakebite · 2015-10-04 11:13:47

Looks like it's already built lircd (line 102) and struggling with the docs for some reason. If the following:

make -C daemons lircd

prints "lircd is up to date" it should be already built, and you can just ignore the error.

graysky · 2015-10-04 11:33:19

Seems I am done bisecting:

b59b88e79c2ae62ca8f2e1766a50678de5e3c4e7 is the first bad commit

Complete log of bisect:

% git bisect start

% git bisect good lirc-0_9_2a

% git bisect bad lirc-0_9_3pre3
Bisecting: 136 revisions left to test after this (roughly 7 steps)
[4ebae71cb8517b906ad676bf81eda22a0aed8fbe] daemons: Formatted.

% git bisect good
Bisecting: 68 revisions left to test after this (roughly 6 steps)
[5a7e6618cb5f6fd05c5dbf1503733b7f63241352] lirc-lsplugins: Display log after parsing file(s).

% git bisect good
Bisecting: 34 revisions left to test after this (roughly 5 steps)
[91aa31c87d4a0fcc2b92d9aa2307a92d1ff09dd6] doc: index: Clean up manpage TOC, add programs overview.

% git bisect good
Bisecting: 17 revisions left to test after this (roughly 4 steps)
[9aaffcae5cbc4135eccdb67ab1fa73f079b86067] build: Let configure die without suitbale python (#112)

% git bisect good
Bisecting: 8 revisions left to test after this (roughly 3 steps)
[6b799dbe89bb47bb3ba35545ac3529b06733cadc] irrecord-ui: More user feedback, formatting.

% git bisect good
Bisecting: 4 revisions left to test after this (roughly 2 steps)
[7c68069f6c35ffb78e39f58e24084850d5bf9949] lircd: Set supplementary groups (RH bz 1253907).

% git bisect bad
Bisecting: 1 revision left to test after this (roughly 1 step)
[b59b88e79c2ae62ca8f2e1766a50678de5e3c4e7] plugins: default: Work around kernel bug (#119).

% git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[2d468b78b6659db6b78b66c44901e4ab86133011] tools: pronto2lirc: Fix stoneage python syntax (#118).

% git bisect good
b59b88e79c2ae62ca8f2e1766a50678de5e3c4e7 is the first bad commit
commit b59b88e79c2ae62ca8f2e1766a50678de5e3c4e7
Author: Alec Leamas <leamas.alec@gmail.com>
Date:   Sun Aug 16 09:21:50 2015 +0200

    plugins: default: Work around kernel bug (#119).

		:040000 040000 7593a67b6d8b2206943fd4807f409e1cc89d31d9 85e18e31f94266dd83b4ac38fbfeeaea52467515 M	plugins

I updated the upstream ticket. Let's see what Alec says.

Last edited by graysky (2015-10-04 11:42:35)

snakebite · 2015-10-04 11:43:37

That commit is apparently not in the master branch, which I bisected against:

$ git branch -a --contains b59b88e79c2ae62ca8f2e1766a50678de5e3c4e7
  remotes/origin/release
  remotes/origin/release-0_9_3

Which branch did you use? release-0_9_3? I should try bisecting again on my end against the same branch.

graysky · 2015-10-04 11:49:40

I thought I started on master...

% git branch
* (no branch, bisect started on master)
  3
  master
  new

3 and new was when I simply checked out the two tags to verify where it started.

3 = lirc-0_9_3pre3
new = lirc-0_9_2a

git checkout -b new lirc-0_9_2a
git checkout -b 3 lirc-0_9_3pre3

Last edited by graysky (2015-10-04 11:52:04)

snakebite · 2015-10-04 11:51:55

git branch should show you what branch you're on, and what branch you started on (if you're still in bisect mode, which you should be unless you've done git bisect reset). If you checked out a release tag you might have switched to a commit which is in another branch.

Edit: FTR I'm bisecting against release-0_9_3, will post results when done.

Last edited by snakebite (2015-10-04 11:53:22)

graysky · 2015-10-04 11:52:59

I was editing while you posted, to clarify:

% git branch
* (no branch, bisect started on master)

snakebite · 2015-10-04 11:57:10

It's probably because of this:

% git bisect bad lirc-0_9_3pre3

which is not reachable from master:

 $ git branch -a --contains lirc-0_9_3pre3
  remotes/origin/release
  remotes/origin/release-0_9_3

I marked master as the first bad commit.

EDIT: Just finished bisecting against release-0_9_3 and got 7dca803fc6b6b7090d057194f2828c21e186dfd6 as the bad commit. Exact same change as my previous bisect, just in a different branch (so different commit hashes). So I'm guessing we're seeing similar issues but due to different bugs.

Last edited by snakebite (2015-10-04 12:06:27)

wilberfan · 2015-10-06 00:17:44

Wanted to chime in and say I'm experiencing this same issue. It started a week or so ago when I did an upgrade. A bunch of stuff updated--among them the kernel and lirc. I figured the problem was probably due to one or the other. (I'm pleased to see that graysky made the original post, here. He's the one that walked me thru getting my streamzap remote to work with my mythtv frontend. If HE'S having trouble, then I know it's not just something I borked. ;-) )

I haven't read the entire thread yet...is it possible to restore my remote functionality by downgrading lirc?

[edit] Just saw this in snakebite's post: "Downgrading to lirc-0.9.2.a-1 solves the issue for me."

Last edited by wilberfan (2015-10-06 00:27:20)

graysky · 2015-10-06 00:20:35

See the arch bug report wherein I posted the patch that fixes it. Just build from abs applying that patch and it will be fine again.
https://bugs.archlinux.org/task/46550

Last edited by graysky (2015-10-06 00:22:33)

Arch Linux

#1 2015-10-01 20:27:50

Are others having double key presses with lirc-0.9.3-2? [solved]

#2 2015-10-03 14:19:54

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#3 2015-10-03 14:50:25

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#4 2015-10-03 14:53:53

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#5 2015-10-03 15:09:16

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#6 2015-10-03 15:27:12

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#7 2015-10-03 15:37:27

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#8 2015-10-03 18:38:14

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#9 2015-10-03 19:37:06

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#10 2015-10-03 23:45:43

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#11 2015-10-04 08:54:27

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#12 2015-10-04 10:06:39

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#13 2015-10-04 10:20:51

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#14 2015-10-04 10:34:39

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#15 2015-10-04 10:39:54

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#16 2015-10-04 10:56:54

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#17 2015-10-04 11:13:47

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#18 2015-10-04 11:33:19

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#19 2015-10-04 11:43:37

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#20 2015-10-04 11:49:40

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#21 2015-10-04 11:51:55

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#22 2015-10-04 11:52:59

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#23 2015-10-04 11:57:10

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#24 2015-10-06 00:17:44

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

#25 2015-10-06 00:20:35

Re: Are others having double key presses with lirc-0.9.3-2? [solved]

Board footer