Skip to content

Using a lock function to prevent the raising events twice.#452

Open
pylover wants to merge 2 commits intopopcornmix:masterfrom
pylover:master
Open

Using a lock function to prevent the raising events twice.#452
pylover wants to merge 2 commits intopopcornmix:masterfrom
pylover:master

Conversation

@pylover
Copy link

@pylover pylover commented May 7, 2016

in most distros, including: rpi3 & jessie, all lirc command raises twice.

pylover added 2 commits May 7, 2016 20:40
in most distros, including: rpi3 & jessie, all lirc command raises twice.
@Ruffio
Copy link

Ruffio commented Jun 9, 2016

@pylover can you resolve the conflicts?

@pylover
Copy link
Author

pylover commented Jun 9, 2016

Yes. of course
On Jun 9, 2016 1:13 PM, Rasmus Christiansen notifications@github.com wrote:@pylover can you resolve the conflicts?

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.

@Ruffio
Copy link

Ruffio commented Jan 7, 2017

@pylover can you resolve the conflicts?

@Ruffio
Copy link

Ruffio commented Mar 30, 2017

@popcornmix can this be merged?

@popcornmix
Copy link
Owner

It's not clear to me why this is needed and what connection LIRC has with omxplayer/dbus.

It looks like this change will have a detrimental (slowing down) effect on users using dbug who don't have this issue.

@pylover
Copy link
Author

pylover commented Mar 30, 2017

Actually, It's the LIRC problem for many years.

@popcornmix
Copy link
Owner

Have you tried playing with the repeat parameter in /etc/lirc/lircrc
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=91317

It seems the right place to fix this is at the lirc end, not the omxplayer end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants