here you are, if you want to compare my zyntrace.txt, with yours. See the attached file. You should use kompare, to compare the two files. :D<br>good luck.<br><br>Mysth-R<br><br><div><span class="gmail_quote">2007/11/24, Fernando Lopez-Lezcano <
<a href="mailto:nando@ccrma.stanford.edu">nando@ccrma.stanford.edu</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Sat, 2007-11-24 at 17:46 +0100, Nigel Henry wrote:
<br>> On Saturday 24 November 2007 12:13, Mysth-R wrote:<br>> > Perhaps you could try to compile Zyn by yourself ?<br>><br>> Hi. First I created a new user as Fernando had suggested, but the problem<br>> still exists.
<br>[MUNCH]<br>> This is really weird, as you say that you have no problems with Zyn on F8, and<br>> KDE. I asked the same ? a while back, and Fernando said he had no problems<br>> with it on Gnome, so I logged out of F7 KDE, and logged back into Gnome, and
<br>> Zyn performed as expected, no problems, which is why I thought it was some<br>> problem with KDE on F7, and now F8.<br><br>Puzzling.<br>What video card and driver are you using in the machine that fails?<br><br>
Maybe you could strace zyn and that may (unlikely) tell us something.<br>You can do (if using bash as the shell):<br><br> strace zynaddsubfx &>zyntrace.txt<br><br>And then quit zyn after the problem manifests itself. The trace will be
<br>very long (it is a trace of all system calls that the executable makes).<br>Maybe you could compare it with one from the systems that work fine.<br>Unlikely we'll know what's going on but worth a try.<br><br>-- Fernando
<br><br><br></blockquote></div><br><br clear="all"><br>-- <br>{^_^} Mysth-R {^_^}<br><br><a href="http://myspace.com/mysthr">http://myspace.com/mysthr</a><br><a href="http://myspace.com/aideauditive">http://myspace.com/aideauditive
</a><br><A href=<a href="http://mysthr.free.fr/ErwanInyzant/">http://mysthr.free.fr/ErwanInyzant/</a>>Gagner plein d'argent en restant chez soit</A>