Bug 24202 - lircd: error processing command: CODE causing core dumps
Summary: lircd: error processing command: CODE causing core dumps
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-18 06:41 CET by Bit Twister
Modified: 2020-08-23 15:35 CEST (History)
4 users (show)

See Also:
Source RPM: lirc-0.9.1a-4.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2019-01-18 06:41:27 CET
Description of problem:

error processing command: CODE causing core dumps and requires stop/start
mythfrontend to get a reconnect.

Jan 17 20:43:39 mtv.home.test lircrcd[8089]: error processing command: CODE
Jan 17 20:43:39 mtv.home.test lircrcd[8089]: protocol error

That piece of code needs to just log the error and continue as normal.

Guessing core caused when two buttons pushed at same time or unclean button
press generates an unknown code. My remote does not have separate up/down
arrow keys, just a ring around the OK button.

Happens on all three of my old RCA RCRN04GR remotes. New ones arrived tonight,
and new remote cored on about third delete recording. I hit delete recording,
Usually hit channel down or Arrow down and get the core dump.

Doing this bug happened with channel down.

Version-Release number of selected component (if applicable):


How reproducible: Way too many times


Steps to Reproduce:
1. Enable core dump.
2. run the remote until it quit responding.

Using SiliconDust HDHR-US as my network IR receiver.

# ll *core | awk '{print $6, $7, $8}' | sort -V
Jan 6 05:45
Jan 6 14:29
Jan 6 20:07
Jan 7 17:33
Jan 7 18:15
Jan 7 22:54
Jan 7 23:03
Jan 8 18:01
Jan 8 19:12
Jan 8 23:28
Jan 9 02:25
Jan 9 02:27
Jan 9 17:08
Jan 9 18:16
Jan 10 21:34
Jan 10 22:12
Jan 10 22:55
Jan 10 23:17
Jan 11 06:29
Jan 11 06:38
Jan 11 08:31
Jan 11 21:58
Jan 12 06:37
Jan 12 21:45
Jan 13 07:33
Jan 13 17:36
Jan 13 17:51
Jan 14 00:46
Jan 14 22:04
Jan 15 05:32
Jan 15 17:25
Jan 15 22:50
Jan 16 00:19
Jan 16 01:18
Jan 16 13:13
Jan 16 14:38
Jan 16 23:22
Jan 17 02:10
Jan 17 18:25
Jan 17 20:26
Jan 17 23:11
Comment 1 Marja Van Waes 2019-01-19 19:20:36 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package.

CC'ing a recent committer.

Assignee: bugsquad => pkg-bugs
CC: (none) => geiger.david68210, marja11

Comment 2 Bit Twister 2019-01-29 12:31:47 CET
I would be happy to test lirc-0.10.1-5 in mga6 testing to see if it resolves
the core problem.
Comment 3 Bit Twister 2019-02-01 12:19:53 CET
Verified lirc-0.10.1 does not have the problem that lirc-0.9.1 has.

I had mga6 running on my mtv node and mag7 running on my test bed node tb
with mythfrontend running on both nodes.

Twice I had lirc-0.9.1 core which drops the lircd connection and lircd
did not core on mga7 and tv remote continued to work on 7 and no longer
worked on 6.
Comment 4 Lewis Smith 2019-08-22 21:17:27 CEST
(In reply to Bit Twister from comment #3)
> Verified lirc-0.10.1 does not have the problem that lirc-0.9.1 has.
Thank you for confirming the resolution with version 0.10.1 in Mageia 7.
Mageia 6 still has lirc-0.9.1a and the problem, so the bug remains open for that unless ...  https://bugs.mageia.org/show_bug.cgi?id=13978#c24

CC: (none) => lewyssmith

Comment 5 Aurelien Oudelet 2020-08-23 15:35:23 CEST
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:OLD

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.