[mythtv-commits] Ticket #12972: Frontend idle timeout cannot be fully disabled

MythTV noreply at mythtv.org
Mon Aug 14 18:16:59 UTC 2017


#12972: Frontend idle timeout cannot be fully disabled
------------------------------+------------------------
 Reporter:  amb@…             |          Owner:
     Type:  Patch - Bug Fix   |         Status:  new
 Priority:  minor             |      Milestone:  29.0
Component:  MythTV - General  |        Version:  0.28.0
 Severity:  low               |     Resolution:
 Keywords:                    |  Ticket locked:  0
------------------------------+------------------------

Comment (by amb@…):

 1. The code does not operate as the documentation string say so it **is**
 a bug (of one sort or another).

 2. The default value of this configuration setting is non-zero - it has to
 be explicitly set to zero by the user.

 3. There are three places in the code where FrontendIdleTimeout is used
    a. One is in the function MythMainWindow::MythMainWindow() where it
 starts a timer to go to standby after an idle time **only** if
 FrontendIdleTimeout>0.
    b. One is in the function MythMainWindow::customEvent() where the idle
 timeout is restarted when the configuration item is changed but **only**
 if FrontendIdleTimeout>0.
    c. The third one is the one that I patched where the system will go to
 standby on automatic startup whether the FrontendIdleTimeout is zero or
 not.

 4. If a user has set the configuration value to zero then their system
 will **only** enter standby if mythfrontend is started just before a
 recording is scheduled to start.  It will not enter standby if they leave
 it idle for hours because the timer that checks for idleness is never
 started.

 5. Yes, I am using Mythwelcome and my system doesn't run 24x7.  The
 problem is triggered if I start the frontend from mythwelcome just before
 a recording is scheduled to start when it goes to standby and I have to
 press another key to exit standby.

 6. There is nobody who could be disadvantaged by this change.
   a. Without the change
      i. If they have set the configuration value to nono-zero then they
 will go to standby.
      ii. If they have set the configuration value to zero then they will
 not go to standby **except if they start mythfrontend just before a
 recording**
   b. With the change
      i. If they have set the configuration value to non-zero then they
 will go to standby.
      ii. If they have set the configuration value to zero then they will
 not go to standby **ever**.

--
Ticket URL: <https://code.mythtv.org/trac/ticket/12972#comment:5>
MythTV <http://www.mythtv.org>
MythTV Media Center


More information about the mythtv-commits mailing list