El 09/04/11 22:47, Andrew escribió: > Are you using qtjackctl or launching from a script/command line? > Andrew Euell > The Sound of IT - High tech solutions for audio problems > > -----Original Message----- > From: wfdudley <[email protected]> > Sender: [email protected] > Date: Sat, 9 Apr 2011 14:18:59 > To: <[email protected]> > Reply-To: Ubuntu Studio Users Help and Discussion > <[email protected]> > Subject: help, jackd crashing, don't know why > > Hi, > > I upgraded my ubuntu studio box to Lucid Lynx and now jackd is crashing. > > Here's the log: > > 09:49:11.871 Patchbay deactivated. > 09:49:11.914 Statistics reset. > 09:49:12.068 ALSA connection graph change. > 09:49:12.427 ALSA connection change. > 09:49:21.874 Startup script... > 09:49:21.876 artsshell -q terminate > sh: artsshell: not found > 09:49:22.280 Startup script terminated with exit status=32512. > 09:49:22.281 JACK is starting... > 09:49:22.283 /usr/bin/jackd -v -dalsa -dhw:0 -r44100 -p1024 -n3 > jackd 0.118.0 > Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben > Hohn and others. > jackd comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > Memory locking is unlimited - this is dangerous. You should probably > alter the line: > @audio - memlock unlimited > in your /etc/limits.conf to read: > @audio - memlock 354993 > 09:49:22.318 JACK was started with PID=4646 > getting driver descriptor from /usr/lib/jack/jack_dummy.so > getting driver descriptor from /usr/lib/jack/jack_alsa.so > getting driver descriptor from /usr/lib/jack/jack_firewire.so > no message buffer overruns > getting driver descriptor from /usr/lib/jack/jack_net.so > getting driver descriptor from /usr/lib/jack/jack_oss.so > JACK compiled with System V SHM support. > server `default' registered > registered builtin port type 32 bit float mono audio > registered builtin port type 8 bit raw midi > clock source = system clock via clock_gettime > start poll on 3 fd's > loading driver .. > apparent rate = 44100 > creating alsa driver ... hw:0|hw:0|1024|3|44100|0|0|nomon|swmeter|-|32 bit > control device hw:0 > new client: alsa_pcm, id = 1 type 1 @ 0x8fe7df8 fd = -1 > 09:49:24.722 Could not connect to JACK server as client. - Please > check the messages window for more info. > server thread back from poll > new client: qjackctl, id = 2 type 2 @ 0xb788c000 fd = 13 > start poll on 4 fd's > cannot read event connect result from server (interrupted system call) > 09:49:25.155 JACK was stopped successfully. > 09:49:25.162 Post-shutdown script... > 09:49:25.164 killall jackd > 09:49:25.165 Jack has crashed. > jackd: no process found > 09:49:25.661 Post-shutdown script terminated with exit status=256. > > The result of uname -a: > Linux hdrec 2.6.31-11-rt #154-Ubuntu SMP PREEMPT RT Wed Jun 9 12:28:53 > UTC 2010 i686 GNU/Linux > > Current Ubuntu version: Lucid Lynx > > Is there anything more I should be reporting? > > Thanks in advance, > Bill Dudley > avid ubuntu user >
I think you have little RAM, 512 MB or so? Check "ls /dev/shm". The problem could have to do with this: https://bugs.launchpad.net/ubuntu/+source/jack-audio-connection-kit/+bug/491329 (This bug affects many more than 4 people even if they don't know, which is the worst case). See also: http://www.linuxmusicians.com/viewtopic.php?f=27&t=2790 Cheers! Pablo -- Ubuntu-Studio-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
