<br><br><div class="gmail_quote">On Fri, Apr 10, 2009 at 8:21 AM, John Werner <span dir="ltr"><<a href="mailto:flybrick@frontiernet.net">flybrick@frontiernet.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
I just updated myth installs (6 machines) to the latest trunk variant.<br>
The SVN pull included the changeset 20310 which disables starting if<br>
pulse audio is found. While I fully understand the reasons for not<br>
wanting pulse audio running, completely failing to start mythfrontend<br>
seems like a fairly harsh way to handle it. I would much rather see a<br>
warning printed then actually making what was a running system suddenly<br>
not run.</blockquote><div><br>Welcome to life on the bleeding edge. If the developers believed it a strong enough issue to be a full stop error, then your options really are to remove pulse audio or stay with a revision prior to that changeset until a pulse audio fix is committed or it is clear that it will never be included, in which case, you're back to option #1.<br>
<br>Kevin</div></div><br>