[SOLVED] Jackdbus fails on boot and then succeeds. Why is it starting twice?

What other apps and distros do you use to round out your studio?

Moderators: MattKingUSA, khz

Post Reply
lad
Established Member
Posts: 45
Joined: Thu Aug 16, 2018 8:31 pm
Has thanked: 1 time
Been thanked: 1 time

[SOLVED] Jackdbus fails on boot and then succeeds. Why is it starting twice?

Post by lad »

I am trying to figure out why the log file indicates that Jack is attempting to start *twice* on boot. I am am at my wits end. Please see get the following message in my jackdbus log file when I boot my machine.

I am using cadence and have set it to start a ladish session on boot.

The crazy thing is that it appears jack is trying to start twice. The first time fails with the following error and then the subsequent attempt then it starts.
Fri Apr 9 18:51:13 2021: ERROR: Failed to acquire device name : Audio1 error : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broke
Fri Apr 9 18:51:13 2021: ERROR: Audio device hw:PCH cannot be acquired...
Fri Apr 9 18:51:13 2021: ERROR: Cannot initialize driver
Fri Apr 9 18:51:13 2021: ERROR: JackServer::Open failed with -1
Fri Apr 9 18:51:13 2021: ERROR: Failed to open server

Full Log file after rebooting:
Fri Apr 9 18:51:06 2021: ------------------
Fri Apr 9 18:51:06 2021: Controller activated. Version 1.9.12 (unknown) built on Sun Feb 25 11:41:33 2018
Fri Apr 9 18:51:06 2021: Loading settings from "/home/lad/.config/jack/conf.xml" using expat_2.2.6 ...
Fri Apr 9 18:51:06 2021: setting parameter 'engine':'driver':'(null)' to value "alsa"
Fri Apr 9 18:51:06 2021: setting parameter 'engine':'realtime':'(null)' to value "true"
Fri Apr 9 18:51:06 2021: setting parameter 'engine':'verbose':'(null)' to value "false"
Fri Apr 9 18:51:06 2021: setting parameter 'engine':'client-timeout':'(null)' to value "500"
Fri Apr 9 18:51:06 2021: setting parameter 'engine':'self-connect-mode':'(null)' to value "e"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'device' to value "hw:PCH"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'capture' to value "hw:PCH"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'playback' to value "hw:PCH"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'rate' to value "48000"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'period' to value "256"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'hwmon' to value "false"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'hwmeter' to value "false"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'duplex' to value "true"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'softmode' to value "false"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'monitor' to value "false"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'dither' to value "n"
Fri Apr 9 18:51:06 2021: setting parameter 'drivers':'alsa':'shorts' to value "false"
Fri Apr 9 18:51:06 2021: Listening for D-Bus messages
Fri Apr 9 18:51:06 2021: Controller deactivated.
Fri Apr 9 18:51:07 2021: ------------------
Fri Apr 9 18:51:07 2021: Controller activated. Version 1.9.12 (unknown) built on Sun Feb 25 11:41:33 2018
Fri Apr 9 18:51:08 2021: Loading settings from "/home/lad/.config/jack/conf.xml" using expat_2.2.6 ...
Fri Apr 9 18:51:08 2021: setting parameter 'engine':'driver':'(null)' to value "alsa"
Fri Apr 9 18:51:08 2021: setting parameter 'engine':'realtime':'(null)' to value "true"
Fri Apr 9 18:51:08 2021: setting parameter 'engine':'verbose':'(null)' to value "false"
Fri Apr 9 18:51:08 2021: setting parameter 'engine':'client-timeout':'(null)' to value "500"
Fri Apr 9 18:51:08 2021: setting parameter 'engine':'self-connect-mode':'(null)' to value "e"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'device' to value "hw:PCH"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'capture' to value "hw:PCH"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'playback' to value "hw:PCH"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'rate' to value "48000"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'period' to value "256"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'hwmon' to value "false"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'hwmeter' to value "false"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'duplex' to value "true"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'softmode' to value "false"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'monitor' to value "false"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'dither' to value "n"
Fri Apr 9 18:51:08 2021: setting parameter 'drivers':'alsa':'shorts' to value "false"
Fri Apr 9 18:51:08 2021: Listening for D-Bus messages
Fri Apr 9 18:51:08 2021: Starting jack server...
Fri Apr 9 18:51:08 2021: JACK server starting in realtime mode with priority 10
Fri Apr 9 18:51:08 2021: self-connect-mode is "Ignore self connect requests to external ports only"
Fri Apr 9 18:51:13 2021: Device reservation request with priority 2147483647 denied for "Audio1": org.freedesktop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply,
Fri Apr 9 18:51:13 2021: [1m[31mERROR: Failed to acquire device name : Audio1 error : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broke[0m
Fri Apr 9 18:51:13 2021: [1m[31mERROR: Audio device hw:PCH cannot be acquired...[0m
Fri Apr 9 18:51:13 2021: [1m[31mERROR: Cannot initialize driver[0m
Fri Apr 9 18:51:13 2021: [1m[31mERROR: JackServer::Open failed with -1[0m
Fri Apr 9 18:51:13 2021: [1m[31mERROR: Failed to open server[0m
Fri Apr 9 18:51:13 2021: Saving settings to "/home/lad/.config/jack/conf.xml" ...
Fri Apr 9 18:51:13 2021: Starting jack server...
Fri Apr 9 18:51:13 2021: JACK server starting in realtime mode with priority 10
Fri Apr 9 18:51:13 2021: self-connect-mode is "Ignore self connect requests to external ports only"
Fri Apr 9 18:51:13 2021: Acquired audio card Audio1
Fri Apr 9 18:51:13 2021: creating alsa driver ... hw:PCH|hw:PCH|256|2|48000|0|0|nomon|swmeter|-|32bit
Fri Apr 9 18:51:13 2021: configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 2 periods
Fri Apr 9 18:51:13 2021: ALSA: final selected sample format for capture: 32bit integer little-endian
Fri Apr 9 18:51:13 2021: ALSA: use 2 periods for capture
Fri Apr 9 18:51:13 2021: ALSA: final selected sample format for playback: 32bit integer little-endian
Fri Apr 9 18:51:13 2021: ALSA: use 2 periods for playback
Fri Apr 9 18:51:13 2021: graph reorder: new port 'system:capture_1'
Fri Apr 9 18:51:13 2021: New client 'system' with PID 0
Fri Apr 9 18:51:13 2021: graph reorder: new port 'system:capture_2'
Fri Apr 9 18:51:13 2021: graph reorder: new port 'system:playback_1'
Fri Apr 9 18:51:13 2021: graph reorder: new port 'system:playback_2'
Fri Apr 9 18:51:13 2021: New client 'PulseAudio JACK Sink' with PID 2292
Fri Apr 9 18:51:13 2021: ignoring port self connect request to external port (PulseAudio JACK Sink:front-left -> system:playback_1)
Fri Apr 9 18:51:13 2021: ignoring port self connect request to external port (PulseAudio JACK Sink:front-right -> system:playback_2)
Fri Apr 9 18:51:13 2021: New client 'PulseAudio JACK Source' with PID 2292
Fri Apr 9 18:51:13 2021: ignoring port self connect request to external port (system:capture_1 -> PulseAudio JACK Source:front-left)
Fri Apr 9 18:51:13 2021: ignoring port self connect request to external port (system:capture_2 -> PulseAudio JACK Source:front-right)
Fri Apr 9 18:51:13 2021: New client 'lsp' with PID 2633
Fri Apr 9 18:51:13 2021: Client 'lsp' with PID 2633 is out
Fri Apr 9 18:51:13 2021: Connecting 'PulseAudio JACK Sink:front-left' to 'system:playback_1'
Fri Apr 9 18:51:13 2021: Connecting 'PulseAudio JACK Sink:front-right' to 'system:playback_2'
Fri Apr 9 18:51:13 2021: Connecting 'system:capture_1' to 'PulseAudio JACK Source:front-left'
Fri Apr 9 18:51:13 2021: Connecting 'PulseAudio JACK Sink:front-left' to 'PulseAudio JACK Source:front-left'
Fri Apr 9 18:51:13 2021: Connecting 'PulseAudio JACK Sink:front-right' to 'PulseAudio JACK Source:front-right'
Fri Apr 9 18:51:13 2021: Connecting 'system:capture_2' to 'PulseAudio JACK Source:front-right'
Fri Apr 9 18:51:13 2021: [1m[31mERROR: cannot find client 4[0m
OS: Debian 11 kernel: Liquorix
...trying out AV Linux
lad
Established Member
Posts: 45
Joined: Thu Aug 16, 2018 8:31 pm
Has thanked: 1 time
Been thanked: 1 time

Re: [SOLVED] Jackdbus fails on boot and then succeeds. Why is it starting twice?

Post by lad »

Since I am using Cadence, I had to stop/disable pulseaudio from starting at boot. This allows Cadence to control when pulseaudio starts instead of systemd.

Solution:

systemctl stop --user pulseaudio.socket && systemctl --user disable pulseaudio.socket
systemctl stop --user pulseaudio && systemctl disable --user pulseaudio
OS: Debian 11 kernel: Liquorix
...trying out AV Linux
User avatar
TAERSH
Established Member
Posts: 455
Joined: Mon Feb 03, 2020 6:48 pm
Has thanked: 27 times
Been thanked: 21 times

Re: [SOLVED] Jackdbus fails on boot and then succeeds. Why is it starting twice?

Post by TAERSH »

lad wrote: Sat Apr 10, 2021 3:54 am Since I am using Cadence, I had to stop/disable pulseaudio from starting at boot. This allows Cadence to control when pulseaudio starts instead of systemd.
:lol:

Long live Pulse Audio!
Long live SystemD!

:lol:

I don't have nothing of them both in my system! :D
Post Reply