<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Apr 17, 2013 at 8:42 PM, Karl Newman <span dir="ltr"><<a href="mailto:siliconfiend@gmail.com" target="_blank">siliconfiend@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I don't use LiveTV but my wife reported a problem with LiveTV since I updated to the latest 0.25.3 version about 3 weeks ago. When attempting to change a channel, the frontend freezes for about a minute, then dumps back to the menu with an error dialog. I don't remember the exact message but I believe it was the "Video buffering failed too many times" one. Re-entering LiveTV, the tuner is then on the desired channel and works normally.<br>
<br>My system uses a single PVR-500, so that implies analog, ivtv, MPEG-2 and all that associated.<br><br>I'm using Gentoo and the installed version includes commits to 0.25-fixes through March 22. Since there was a limited number of commits from the previous version (Jan 31) I looked through the list for likely culprits. Backing out commit 71ad653b9a7ba593eb5307d4cd88a81e4d9387a4 and its related partner <span><span>5f5e5f70b16f3733764a70c4767c2d4ebdd3a915 made channel changing in LiveTV work again.<br>
<br></span></span></div><span><span>I see those same cherry-picked commits are also in 0.26 and none of the commits after it appear to address any problem like this. I attempted to look up a ticket with this issue, but there were only 2 active tickets regarding LiveTV, and searching for "livetv" brought up 11 pages worth and I didn't feel like going through all that, sorry...<span class=""><font color="#888888"><br>
<br>Karl<br></font></span></span></span></div>
</blockquote></div><br></div><div class="gmail_extra">Replying to myself: As a follow-up to this, I discovered commit edefeb6f4c8d9deb792793acb22d342db90411cf in master (<span class=""><span class="">c1147b634ad9977d3bb480121b300ed92376b9a7 in 0.25-fixes, </span></span><br>
<span class=""><span class="">69cd78b4028b7b585d238713151b684c291158e7 in 0.26-fixes) solved this problem. It references ticket 11459, but those symptoms (problems in seeking) were not what I was experiencing. I guess I just had a build which happened to fall between the regression and its fix.<br>
<br>Karl<br></span></span></div></div>