[mythtv-commits] Ticket #9360: Delete - "Yes, and allow re-record" doesn't reschedule episodes

[MythTV]

#9360: Delete - "Yes, and allow re-record" doesn't reschedule episodes
-------------------------------------------+----------------------------
 Reporter:  skd5aner <skd5aner@…>          |          Owner:  gigem
     Type:  Bug Report                     |         Status:  new
 Priority:  minor                          |      Milestone:  unknown
Component:  MythTV - Scheduling            |        Version:  0.24-fixes
 Severity:  medium                         |     Resolution:
 Keywords:                                 |  Ticket locked:  0
-------------------------------------------+----------------------------
Description changed by wagnerrp:

Old description:

> I'm no longer able to reschedule episodes of shows by using the "delete -
> yes, and allow re-record" option on a recording from the watch recordings
> screen.  I believe, but can not confirm that this has happened sometime
> after the 0.22 release. I first noticed this behavior sometime during my
> usage of 0.23, after I finally looked at why episodes weren't eventually
> re-recording.  I was waiting until after 0.24's release to see if the
> behavior resolved itself, but after testing, it appears to still be
> present.  I can replicate it on any recording rule, new or old, where
> episodes are recorded, deleted and allowed to re-record, and then later
> re-aired.
>
> Step to replicate:
>
> 1) Create a recording rule, an "any channel" rule for example, for a
> series that usually re-airs episodes (Discovery Channel/TLC/History
> typically air the same episodes multiple times a day/week).
>
> 2) Allow a non-generic episode to record that has a later airing.
>
> 3) Delete the recording through the watch recordings screen by going to
> Menu, Delete, select "Yes, and allow re-record".
>
> 4) Wait for the scheduler to run (or run mythbackend --resched)
>
> 5) Check the "Upcoming Episodes" screen for the recording rule and look
> for any airings of the same episode that was marked for delete and re-
> record.  They will continue to be marked as "Record All - Previously
> Recorded" and will not be scheduled to record.
>
> The only way to re-record (via the frontend UI) is to go into the
> recording history and forget the recording.
>

> I have also tested this against the "Delete + rerecord" button in mythweb
> and it *does not* exhibit the same behavior - it actually works as
> expected.  "Delete + rerecord" in mythweb, will both delete the recording
> and reschedule the episode to be re-recorded.
>

> I typically would provide logs in the initial report, but I'm not sure
> which verbose options might be of use without further guidance.  Please
> let me know and I'd be happy to report back with any details necessarily
> to help with the report.
>
> Thank you in advance!
>

> {{{
> mythbackend --version
> Please attach all output as a file in bug reports.
> MythTV Version   : 27373
> MythTV Branch    : branches/release-0-24-fixes
> Network Protocol : 63
> Library API      : 0.24.20101124-1
> QT Version       : 4.7.0
> Options compiled in:
>  linux release using_alsa using_oss using_pulse using_pulseoutput
> using_backend using_bindings_perl using_bindings_python using_dvb
> using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv
> using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video
> using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11
> using_xrandr using_xv using_bindings_perl using_bindings_python
> using_mythtranscode using_opengl using_ffmpeg_threads using_live
> using_mheg
> }}}

New description:

 I'm no longer able to reschedule episodes of shows by using the "delete -
 yes, and allow re-record" option on a recording from the watch recordings
 screen.  I believe, but can not confirm that this has happened sometime
 after the 0.22 release. I first noticed this behavior sometime during my
 usage of 0.23, after I finally looked at why episodes weren't eventually
 re-recording.  I was waiting until after 0.24's release to see if the
 behavior resolved itself, but after testing, it appears to still be
 present.  I can replicate it on any recording rule, new or old, where
 episodes are recorded, deleted and allowed to re-record, and then later
 re-aired.

 Step to replicate:

 1) Create a recording rule, an "any channel" rule for example, for a
 series that usually re-airs episodes (Discovery Channel/TLC/History
 typically air the same episodes multiple times a day/week).

 2) Allow a non-generic episode to record that has a later airing.

 3) Delete the recording through the watch recordings screen by going to
 Menu, Delete, select "Yes, and allow re-record".

 4) Wait for the scheduler to run (or run mythbackend --resched)

 5) Check the "Upcoming Episodes" screen for the recording rule and look
 for any airings of the same episode that was marked for delete and re-
 record.  They will continue to be marked as "Record All - Previously
 Recorded" and will not be scheduled to record.

 The only way to re-record (via the frontend UI) is to go into the
 recording history and forget the recording.


 I have also tested this against the "Delete + rerecord" button in mythweb
 and it *does not* exhibit the same behavior - it actually works as
 expected.  "Delete + rerecord" in mythweb, will both delete the recording
 and reschedule the episode to be re-recorded.


 I typically would provide logs in the initial report, but I'm not sure
 which verbose options might be of use without further guidance.  Please
 let me know and I'd be happy to report back with any details necessarily
 to help with the report.

 Thank you in advance!

--

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/9360#comment:1>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center