SOLVED: Cadence / JACK2 won't start under Deb Jessie
Posted: Wed Apr 16, 2014 3:08 pm
I know that I've had Cadence running under Debian before but I'm not sure I ever had it running under Deb/KDE - certainly not recently under Deb Jessie, thats for sure.
When I try to start Cadence, I get the errors:
I do not have Pulseaudio installed, nor has it ever been installed on this fresh Jessie (amd64) install, so its not a PA clash.
I thought it could be KDE's sound system blocking JACK from using hw:1 so I disabled it under System Settings -> App and System Notifications -> Player Settings -> No audio output but I just get the same Cadence/JACK error.
Starting Cadence with
Doesn't help either.
JACK/Cadence doesn't even offer me hw:1 as an option. lsof says kded4 is using asound but it shouldn't be after having disabled its audio notifications output, right?
Hopefully it doesn't require rebuilding KDE to fix this as IIRC KXStudio has patched KDE's sound system somehow. Was that just to stop the "Do you want to forget about this device?" prompts or did it fix this issue too?
When I try to start Cadence, I get the errors:
Code: Select all
Wed Apr 16 15:56:12 2014: Starting jack server...
Wed Apr 16 15:56:12 2014: JACK server starting in realtime mode with priority 10
Wed Apr 16 15:56:12 2014: self-connect-mode is "Don't restrict self connect requests"
Wed Apr 16 15:56:12 2014: ERROR: cannot register object path "/org/freedesktop/ReserveDevice1/Audio0": A handler is already registered for /org/freedesktop/ReserveDevice1/Audio0
Wed Apr 16 15:56:12 2014: ERROR: Failed to acquire device name : Audio0 error : A handler is already registered for /org/freedesktop/ReserveDevice1/Audio0
Wed Apr 16 15:56:12 2014: ERROR: Audio device hw:0 cannot be acquired...
Wed Apr 16 15:56:12 2014: ERROR: Cannot initialize driver
Wed Apr 16 15:56:12 2014: ERROR: JackServer::Open failed with -1
Wed Apr 16 15:56:12 2014: ERROR: Failed to open serverCode: Select all
lsof | grep asound
kded4 2260 d76 mem REG 8,2 1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
QInotifyF 2260 2296 d76 mem REG 8,2 1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
jackdbus 2497 d76 mem REG 8,2 1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
a2jmidid 2499 d76 mem REG 8,2 1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
kmix 2607 d76 mem REG 8,2 1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
QInotifyF 2607 2609 d76 mem REG 8,2 1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0Code: Select all
cat /proc/asound/cards
0 [HDMI ]: HDA-Intel - HDA Intel HDMI
HDA Intel HDMI at 0xf7e14000 irq 49
1 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7e10000 irq 45Starting Cadence with
Code: Select all
cadence-session-start -sJACK/Cadence doesn't even offer me hw:1 as an option. lsof says kded4 is using asound but it shouldn't be after having disabled its audio notifications output, right?
Hopefully it doesn't require rebuilding KDE to fix this as IIRC KXStudio has patched KDE's sound system somehow. Was that just to stop the "Do you want to forget about this device?" prompts or did it fix this issue too?