Good morning Hermann :) > yeah, I noticed this strange behaviour too. It's sufficient to close > the shell > and open another one. Of course, reboot fixes it too :-P
I was thinking of testing "just" to start a new session instead of doing a reboot, but I didn't thought about just to close and open the shell, because I'm most time using Yakuake, this terminal emulation starts with each session and the terminal emulation will scroll down, when I push F12. I seldom open or close a shell. > yes, all done correctly. > You did run qsynth and jackd from a terminal on which you set the > ulimit -c unlimited prior to running them? But didn't get a core dump? > Then indeed it looks as if they got killed by a signal or it could be > an emergency shutdown triggered from within the applications. Anyway, > if an program actually crashes (segmentation fault or similar), you > should get an core file. If this isn't the case, I'd report this > behaviour and just ask the autor(s) how to proceed or what additional > informations they need. Shell: [EMAIL PROTECTED]:~> jackd -R -p1024 -dalsa -r48000 -p256 -n2 -D -Chw:0 -Phw:0 [snip] jackd watchdog: timeout - killing jackd [EMAIL PROTECTED]:~> Shell No. 2 [EMAIL PROTECTED]:~> ulimit -c 10240 [EMAIL PROTECTED]:~> qsynth -v [snip] Killed [EMAIL PROTECTED]:~> The whole report is here: http://www.linux-archive.org/64-studio-user/199594-problems-qtractor-debugging-qsynth-failed.html Cheers, Ralf
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
