Since it works from the command line, this shouldn't be the issue.
I would be nice to see the full mythcommflag log from one failing session. You could put
it at pastebin.com or wherever you prefer as long as anyone can read it. Put a link to it
here. Or, if it's short, just paste it here.
I would be nice to see the full mythcommflag log from one failing session. You could put
it at pastebin.com or wherever you prefer as long as anyone can read it. Put a link to it
here. Or, if it's short, just paste it here.
Give me maybe 30 minutes on this. I had already manually started mythcommflag to see if that would result in a log entry. That may have to complete before starting one in mythfrontend will run. I dunno.
Do you have a private version of mythcommflag? The link says change it to just: mythcommflag
(that's what mine is).
Yeah, I had reread that thread and noticed he said *"mythcommflag" is a special word that tells the job queue to use the normal commercial flagging application* probably about the same time you did. So I changed it and it does work! I've been stuck on this for about 2 1/2 years now and this was all it took to fix it. I'm pretty sure that doing the same to transcode will fix that problem, as well.
Thank you Very Very Much for helping me with this. I would still be foundering on the shores of aggravation without your help!