Opened 14 years ago

Closed 14 years ago

#3022 closed defect (fixed)

Mythbackend dies in HandleRemoteEncoder

Reported by: jose.bandos@… Owned by: Isaac Richards
Priority: minor Milestone: 0.20
Component: mythtv Version: 0.20
Severity: medium Keywords:
Cc: Ticket locked: no


This happens to me with all .20 svn versions at least up to rev. 12677. When a tuner isn't bound to a input, the backend dies when queried for tuner status (in mythwelcome or inside the information center). The following is the relevant log output:

2007-01-30 11:06:04.428 MainServer?: HandleRemoteEncoder?(cmd GET_STATE) Unknown encoder: 2, exiting

This has been already discussed in, and the patch in that thread fixed the problem for me. Can it be added to the main trunk? Thank you.

Attachments (1)

allowmissingdecoders.patch (1.2 KB) - added by jose.bandos@… 14 years ago.

Download all attachments as: .zip

Change History (5)

Changed 14 years ago by jose.bandos@…

Attachment: allowmissingdecoders.patch added


comment:1 Changed 14 years ago by cpinkham

Resolution: fixed
Status: newclosed

(In [12972]) Don't exit mythbackend just because someone gave us some invalid information. Instead use the philosophy of Garbate-In, Garbage-Out and let them die a slow painful death if they choose to. This could be on purpose or something as simple as a tuner without any valid inputs attached.

Closes #3022. For this specific case of the invalid tuner, the answer given (-1) is actually valid so this does fix #3022's GET_STATE issue, but now the backend will no longer die for other commands for an incorrectly setup tuner.

comment:2 Changed 14 years ago by stuartm

Resolution: fixed
Status: closedreopened

[12972] needs to be backported to -fixes

comment:3 Changed 14 years ago by stuartm

Milestone: 0.210.20

comment:4 Changed 14 years ago by stuartm

Resolution: fixed
Status: reopenedclosed

(In [14066]) Backports [12972] to -fixes. Don't exit the backend if the user has misconfigured their capture cards. Nothing good can come from such misconfiguration but exiting the backend is potentially worse due to missed recordings etc.

Fixes #3022

Note: See TracTickets for help on using tickets.