Arch Linux

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,567

JACK occasionally doesn't start on boot

JACK occasionally doesn't start on boot. It does not happen every time I boot but I am just wondering what causes it.
Here is the log from Cadence:

Thu Apr 19 08:38:59 2018: Starting jack server...
Thu Apr 19 08:38:59 2018: JACK server starting in realtime mode with priority 10
Thu Apr 19 08:38:59 2018: self-connect-mode is "Don't restrict self connect requests"
Thu Apr 19 08:39:05 2018: 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, 
Thu Apr 19 08:39:05 2018: 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
Thu Apr 19 08:39:05 2018: ERROR: Audio device hw:PCH,3 cannot be acquired...
Thu Apr 19 08:39:05 2018: ERROR: Cannot initialize driver
Thu Apr 19 08:39:05 2018: ERROR: JackServer::Open failed with -1
Thu Apr 19 08:39:05 2018: ERROR: Failed to open server

It seems some bus security issue? udev perhaps? Or is this hardware problem?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,657

Re: JACK occasionally doesn't start on boot

The card might also be occupied by some other utility or the cardindex it looks for changes, compare the outputs of

aplay -l
sudo fuser -v /dev/snd/*

during a working and not working boot. Also how and when are you starting the jack server?

Last edited by V1del (2018-04-19 07:51:32)

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,567

Re: JACK occasionally doesn't start on boot

I use Cadence to automate starting the JACK server. I just enabled the option to start JACK on startup. As I said most of the time it works but occasionally doesn't.
I'll have a look at your aplay outputs and see what I can find. Thanks.

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,567

Re: JACK occasionally doesn't start on boot

This is the output when it's not working:

dipswitch@TUF-Z270 ~]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: C20 [Cambridge Audio USB Audio 2.0], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC1220 Analog [ALC1220 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 1: ALC1220 Digital [ALC1220 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
[dipswitch@TUF-Z270 ~]$ 
[dipswitch@TUF-Z270 ~]$ sudo fuser -v /dev/snd/*
[sudo] password for dipswitch: 
                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  dipswitch   1203 F.... pulseaudio
/dev/snd/controlC1:  dipswitch   1203 F.... pulseaudio

And this is the output when it's working:

[dipswitch@TUF-Z270 ~]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: C20 [Cambridge Audio USB Audio 2.0], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC1220 Analog [ALC1220 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 1: ALC1220 Digital [ALC1220 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]                                                                                                                             
  Subdevices: 1/1                                                                                                                                                                  
  Subdevice #0: subdevice #0                                                                                                                                                       
card 1: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]                                                                                                                             
  Subdevices: 1/1                                                                                                                                                                  
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
[dipswitch@TUF-Z270 ~]$ sudo fuser -v /dev/snd/*
                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  dipswitch   1199 F.... jackdbus
                     dipswitch   1203 F.... pulseaudio
/dev/snd/controlC1:  dipswitch   1203 F.... pulseaudio
/dev/snd/pcmC0D0p:   dipswitch   1199 F...m jackdbus

Seems the problem is with jackdbus? Any solution?