id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
399	Quick state change can result in backend looping	Anduin Withers <awithers@…>	danielk	"The switch from RecordingOnly to None and then a quick switch from None to RecordingOnly (the sort you get with consecutive schedules) seems to currently cause a certain amount of badness.

Results vary from a few slightly bad log messages, to a spiraling death loop.

Log attached (removed scheduler calls, otherwise unaltered).
"	defect	closed	major	unknown	mythtv	head	high	fixed			0