You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon restart, mythbackend appears to be issuing two calls to the channel change script when scheduling the first recording after the backend starts. The same occurs if entering Live TV after the backend restarts.
This is occurring with an external recorder .
Platform: Ubuntu 22.04 (Linux mythtv 5.15.0-37-generic 39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux)
How often does it reproduce? Is there a required condition?
Every time after mythbackend restarts
What is the expected behaviour?
Only a single call to the channel change script
What do you see instead?
Two calls to the channel change script
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: I MetadataDownload metadatagrabber.cpp:377 (RunGrabber) Running Grabber: /usr/share/mythtv/metadata/Television/ttvdb4.py -l en -a US -N Chicago Fire Retaliation Hit
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: D MetadataDownload mythsystemunix.cpp:808 (Fork) Launching: /usr/share/mythtv/metadata/Television/ttvdb4.py -l en -a US -N Chicago Fire Retaliation Hit
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: I MetadataDownload mythsystemunix.cpp:965 (Fork) Managed child (PID: 3623) has started! command=/usr/share/mythtv/metadata/Television/ttvdb4.py -l en -a US -N Chicago Fire Retaliation Hit, timeout=0
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: I SystemManager mythsystemunix.cpp:354 (run) Managed child (PID: 3552) has exited! command=/usr/local/bin/ir_channel_change.bash 510, status=0, result=0 Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: D TVRecEvent mythsystemunix.cpp:808 (Fork) Launching: /usr/local/bin/ir_channel_change.bash 550
Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: I TVRecEvent mythsystemunix.cpp:965 (Fork) Managed child (PID: 3638) has started! *& command=/usr/local/bin/ir_channel_change.bash 550, timeout=0 Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: D TVRecEvent mythsystemunix.cpp:808 (Fork) Launching: /usr/local/bin/ir_channel_change.bash 550
Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: I TVRecEvent mythsystemunix.cpp:965 (Fork) Managed child (PID: 3641) has started! *& command=/usr/local/bin/ir_channel_change.bash 550, timeout=0
Additional information
I've been seeing missed channel changes for several months, and unfortunately only now tracked down the culprit.
The text was updated successfully, but these errors were encountered:
Upon restart, mythbackend appears to be issuing two calls to the channel change script when scheduling the first recording after the backend starts. The same occurs if entering Live TV after the backend restarts.
This is occurring with an external recorder .
Platform: Ubuntu 22.04 (Linux mythtv 5.15.0-37-generic 39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux)
MythTV version: fixes/32
Package version: mythbuntu ppa: v32.0+fixes.202206060103.7077a824d2~ubuntu22.04.1
Component: mythbackend
What steps will reproduce the bug?
or
How often does it reproduce? Is there a required condition?
Every time after mythbackend restarts
What is the expected behaviour?
Only a single call to the channel change script
What do you see instead?
Two calls to the channel change script
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: I MetadataDownload metadatagrabber.cpp:377 (RunGrabber) Running Grabber: /usr/share/mythtv/metadata/Television/ttvdb4.py -l en -a US -N Chicago Fire Retaliation Hit
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: D MetadataDownload mythsystemunix.cpp:808 (Fork) Launching: /usr/share/mythtv/metadata/Television/ttvdb4.py -l en -a US -N Chicago Fire Retaliation Hit
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: I MetadataDownload mythsystemunix.cpp:965 (Fork) Managed child (PID: 3623) has started! command=/usr/share/mythtv/metadata/Television/ttvdb4.py -l en -a US -N Chicago Fire Retaliation Hit, timeout=0
Jun 11 16:09:55 mythtv mythbackend: mythbackend[3537]: I SystemManager mythsystemunix.cpp:354 (run) Managed child (PID: 3552) has exited! command=/usr/local/bin/ir_channel_change.bash 510, status=0, result=0
Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: D TVRecEvent mythsystemunix.cpp:808 (Fork) Launching: /usr/local/bin/ir_channel_change.bash 550
Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: I TVRecEvent mythsystemunix.cpp:965 (Fork) Managed child (PID: 3638) has started! *& command=/usr/local/bin/ir_channel_change.bash 550, timeout=0
Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: D TVRecEvent mythsystemunix.cpp:808 (Fork) Launching: /usr/local/bin/ir_channel_change.bash 550
Jun 11 16:09:59 mythtv mythbackend: mythbackend[3537]: I TVRecEvent mythsystemunix.cpp:965 (Fork) Managed child (PID: 3641) has started! *& command=/usr/local/bin/ir_channel_change.bash 550, timeout=0
Additional information
I've been seeing missed channel changes for several months, and unfortunately only now tracked down the culprit.
The text was updated successfully, but these errors were encountered: