On Friday, February 04, 2011, Julie S wrote: > jackd watchdog: timeout - killing jackd > > I'm not even running jack.
You are, you're just not aware of it. Rosegarden tries to start JACK if it's not running, and that message tells me that Rosegarden got JACK going. Shortly after Rosegarden crashes (or probably when it exits normally too), you can expect one of those messages on the console. Yesterday, in fact, I kept getting confused because my core dumps were coming from jackd instead of Rosegarden. What was happening was Rosegarden was doing a core dump, and then jackd was following up with another core dump, writing over top of the first one. I edited ~/.jackdrc to say something stupid, so JACK would go away temporarily. > I'd like any suggestions on how to get the debugger working better. I've never enjoyed any success in this area, and I'm afraid I have nothing to suggest. -- D. Michael McIntyre ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
