Hej, I have a problem with connecting to a running jackd, clients are not able to connect. They are definitly not running as another user as jackd itself. I even tried (only for testing) to run qjackctl as root, with no success either. I can start jackd by a shell and by qjackctl, but after starting no client is able to connect. Even giving the jackd-instance a name by the -n option, clients are not able to connect while specifying that name. There are also no other clients running that could have the same client-id as my test-clients (qjackctl itself, meterbridge, adour2). OS: Ubuntu 6.10 (Edgy), Kernel 2.6.17-10-386 Hardware: M-Audio Delta 44 jackd: 0.102.20 qjackctl: 0.2.20 I had no problems with jackd before upgrading ubuntu from 6.06 to 6.10. Adour points to a problem with ulimit and locked memory while starting, so I give the contents of limits.conf, too (this is not the cause for my troubles, I believe): mechko@almeida:~$ cat /etc/security/limits.conf | grep -v "#" @audio - rtprio 99 @audio - memlock 250000 @audio - nice -10 The message-window after pressing the Start-Button in qjackctl (verbose mode on). There should be an error-message that gives a reason why clients are not able to connect, but I can find none. //snap///////////// 12:05:39.529 Patchbay deactivated. 12:05:39.602 Statistics reset. 12:05:39.973 MIDI connection graph change. 12:05:40.011 MIDI connection change. QInputContext: no input method context available QInputContext: no input method context available 12:05:47.289 Startup script... 12:05:47.289 artsshell -q terminate can't create mcop directory Creating link /home/mechko/.kde/socket-almeida. 12:05:47.559 Startup script terminated with exit status=256. 12:05:47.561 JACK is starting... 12:05:47.563 jackd -v -R -t2000 -dalsa -dhw:0 -r44100 -p128 -n2 -S 12:05:47.570 JACK was started with PID=25103 (0x620f). getting driver descriptor from /usr/local/lib/jack/jack_alsa.so getting driver descriptor from /usr/local/lib/jack/jack_dummy.so getting driver descriptor from /usr/local/lib/jack/jack_oss.so jackd 0.102.20 Copyright 2001-2005 Paul Davis 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 JACK compiled with System V SHM support. server `default' registered loading driver .. apparent rate = 44100 creating alsa driver ... hw:0|hw:0|128|2|44100|0|0|nomon|swmeter|-|16bit control device hw:0 configuring for 44100Hz, period = 128 frames, buffer = 2 periods ALSA: final selected sample format for capture: 32bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit little-endian ALSA: use 2 periods for playback 25103 waiting for signals registered builtin port type 32 bit float mono audio registered builtin port type 8 bit raw midi clock source = system clock via gettimeofday new client: alsa_pcm, id = 1 type 1 @ 0x805a738 fd = -1 new buffer size 128 registered port alsa_pcm:capture_1, offset = 512 registered port alsa_pcm:capture_2, offset = 1024 registered port alsa_pcm:capture_3, offset = 1536 registered port alsa_pcm:capture_4, offset = 2048 registered port alsa_pcm:capture_5, offset = 2560 registered port alsa_pcm:capture_6, offset = 3072 registered port alsa_pcm:capture_7, offset = 3584 registered port alsa_pcm:capture_8, offset = 4096 registered port alsa_pcm:capture_9, offset = 4608 registered port alsa_pcm:capture_10, offset = 5120 registered port alsa_pcm:capture_11, offset = 5632 registered port alsa_pcm:capture_12, offset = 6144 registered port alsa_pcm:playback_1, offset = 0 registered port alsa_pcm:playback_2, offset = 0 registered port alsa_pcm:playback_3, offset = 0 registered port alsa_pcm:playback_4, offset = 0 registered port alsa_pcm:playback_5, offset = 0 registered port alsa_pcm:playback_6, offset = 0 registered port alsa_pcm:playback_7, offset = 0 registered port alsa_pcm:playback_8, offset = 0 registered port alsa_pcm:playback_9, offset = 0 registered port alsa_pcm:playback_10, offset = 0 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. -- jack_rechain_graph() load = 0.0861 max usecs: 5.000, spare = 2897.000 12:05:49.611 Could not connect to JACK server as client. Please check the messages window for more info. load = 0.3877 max usecs: 20.000, spare = 2882.000 load = 0.2800 max usecs: 5.000, spare = 2897.000 load = 0.2261 max usecs: 5.000, spare = 2897.000 load = 0.2337 max usecs: 7.000, spare = 2895.000 load = 0.2030 max usecs: 5.000, spare = 2897.000 load = 0.1876 max usecs: 5.000, spare = 2897.000 load = 0.1627 max usecs: 4.000, spare = 2898.000 load = 0.3054 max usecs: 13.000, spare = 2889.000 load = 0.3077 max usecs: 9.000, spare = 2893.000 12:05:58.362 Could not connect to JACK server as client. Please check the messages window for more info. load = 1.0153 max usecs: 50.000, spare = 2852.000 load = 0.6627 max usecs: 9.000, spare = 2893.000 load = 0.6587 max usecs: 19.000, spare = 2883.000 load = 0.4327 max usecs: 6.000, spare = 2896.000 load = 0.4231 max usecs: 12.000, spare = 2890.000 load = 0.5045 max usecs: 17.000, spare = 2885.000 load = 0.5968 max usecs: 20.000, spare = 2882.000 load = 0.4362 max usecs: 8.000, spare = 2894.000 load = 0.3215 max usecs: 6.000, spare = 2896.000 load = 0.4709 max usecs: 18.000, spare = 2884.000 load = 0.5456 max usecs: 18.000, spare = 2884.000 load = 0.3934 max usecs: 7.000, spare = 2895.000 load = 0.4551 max usecs: 15.000, spare = 2887.000 load = 0.5377 max usecs: 18.000, spare = 2884.000 12:06:12.597 Could not connect to JACK server as client. Please check the messages window for more info. load = 0.3722 max usecs: 6.000, spare = 2896.000 [and so on] \\snip\\\\\\\\\\\\\\\\\\\\\ jackd is running: mechko@almeida:~$ ps aux | grep jackd mechko 25185 0.5 2.6 20552 20592 ? SLsl 12:07 0:00 jackd -v -R -t2000 -dalsa -dhw:0 -r44100 -p128 -n2 -S meterbridge fails: mechko@almeida:~$ meterbridge -t vu alsa_pcm:capture_1 alsa_pcm:capture_2 jack server not running? Could you please give me a hint what to do? Thanks in advance, Mirko Swillus
