<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 9:15 PM, <a href="mailto:jonetsu@teksavvy.com">jonetsu@teksavvy.com</a> <span dir="ltr"><<a href="mailto:jonetsu@teksavvy.com" target="_blank">jonetsu@teksavvy.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Tue, 11 Mar 2014 20:54:53 -0400,<br>
Paul Davis <<a href="mailto:paul@linuxaudiosystems.com">paul@linuxaudiosystems.com</a>> wrote:<br>
<br>
> useful backtraces generally come from the procedures described here:<br>
><br>
>     <a href="http://ardour.org/debugging_ardour" target="_blank">http://ardour.org/debugging_ardour</a><br>
<br>
</div>OK, I'll look into that soon.<br>
<div class=""><br>
> bugs/crashes without repeatable recipes generally do not receive much<br>
> attention.<br>
<br>
</div>At least, 'it' starts to manifest itself often !<br>
<div class=""><br>
> this wasn't a crash, however. how did you quit ardour?<br>
<br>
</div>Well, the KDE box said that the application was not responding anymore<br>
and offered to terminate it...<br></blockquote><div><br></div><div>that's wierd unless you tried to quit by using the "window delete/X" button (typically in the upper corner of a window)<br></div><div> <br>
</div></div></div></div>