<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, May 23, 2014 at 5:08 PM, Craig Huff <span dir="ltr"><<a href="mailto:huffcslists@gmail.com" target="_blank">huffcslists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, May 17, 2014 at 1:32 AM, <<a href="mailto:f-myth-users@media.mit.edu">f-myth-users@media.mit.edu</a>> wrote:<br>
snip...<br>
><br>
> Try replacing the calls to the scripts with calls to a script<br>
> consisting of some or all of<br>
><br>
> #!/bin/bash<br>
> id >> /tmp/DEBUG<br>
> groups >> /tmp/DEBUG<br>
> set >> /tmp/DEBUG<br>
> printenv >> /tmp/DEBUG<br>
><br>
> and see if you get the same results when you call it as you, as the<br>
> mythtv user, and as when myth itself tries to change channels. If you<br>
> don't, try either changing the scripts' environments to match the<br>
> by-hand calls and see if they work, or try changing the by-hand<br>
> calling environment to match the mythtv environment and see if it<br>
> fails.<br>
><br>
> This will also tell you if your script is getting called at all when<br>
> mythtv tries to change channels, of course; maybe myth isn't even<br>
> trying.<br>
><br>
<br>
I took your suggestion and created the wrapper scripts. Manual<br>
testing worked fine, but it appears they don't even get called by<br>
myth. I verified that the fully-specified paths to the channel<br>
changing scripts are correct (no typos!), but nothing is getting added<br>
to the /tmp/DEBUG file when myth is supposed to be changing a channel!<br>
I re-verified that the scripts have world read-execute permissions,<br>
as do the scripts that really do the work. All the scripts write<br>
things that should end up in the log file, so they're never getting<br>
called.<br>
<br>
I did notice that mythmetadatalookup is being called when I'm trying<br>
to change the channel in live-tv mode. Is it possible that something<br>
else is getting stuck before the channel-changing script gets called?<br>
<br>
When I change the channel, I often (but not always) get a message<br>
about framebuffering failed too many times and then myth goes back to<br>
the main frontend screen. There is information in the screen info<br>
panel to the effect that the video signal level dropped out and/or the<br>
system couldn't lock on to the video signal. Since it never called<br>
the routine to change the channel, I don't understand this at all.<br>
<br>
I tracked the contents of several myth***.log files while I made an<br>
attempt to change the channel while in live-tv mode and noted these<br>
things:<br>
* mythpreviewgen complained that /home/mythtv/.mythtv/config.xml<br>
could not be opened for writing, but it seemed to succeed at grabbing<br>
a preview anyway.<br>
* while it shouldn't be relevant, for full disclosure's sake, I also<br>
have a configuration problem with the audio controls and mythfrontend<br>
reported that ALSA couldn't register device /dev/mixer.<br>
* mythfrontend reported numerous messages about waiting for video<br>
buffers that all end with 32 "A"s in a row followed by a "P".<br>
<br>
Your ideas were great, but no Eureka! ensued. I really hate grasping<br>
at straws, but I've completely run out of ideas on this one.<br>
<br></blockquote><div><br></div><div>After the initial run as "user", the DEBUG file already existed. The mythtv user probably cannot write to it. Delete /tmp/DEBUG and try it again. Or /tmp is not writeble by mythtv maybe? </div>
</div></div></div>