Page 1 of 1

Can't start Cadence; "No Reply" error -- but maybe Cadence is already running?

Posted: Wed Nov 21, 2018 5:03 am
by Jeff Brown
I can only start Cadence from the command line with sudo. If I do that it looks different, though -- as if it's using Qt instead of Gtk, or vice versa. That sudo version of Cadence shows "User in audio group: No", and when I click "start" it says "unable to start, check the logs". Those logs include the line The playback device "hw:PCH,0" is already in use. That's what makes me think maybe Cadence is already running, just not displaying the gui or producing sound.

Here's the complete contents of the Cadence logs.

Code: Select all

Tue Nov 20 23:26:17 2018: ------------------
Tue Nov 20 23:26:17 2018: Controller activated. Version 1.9.12 (0+) built on Mon Oct 15 04:25:15 2018
Tue Nov 20 23:26:17 2018: Loading settings from "/home/jeff/.config/jack/conf.xml" using expat_2.2.5 ...
Tue Nov 20 23:26:17 2018: setting parameter 'engine':'driver':'(null)' to value "alsa"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'device' to value "hw:PCH,0"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'capture' to value "hw:PCH,0"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'playback' to value "hw:PCH,0"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'rate' to value "192000"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'period' to value "1024"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'duplex' to value "true"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'monitor' to value "false"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'inchannels' to value "2"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'outchannels' to value "2"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'alsa':'midi-driver' to value "raw"
Tue Nov 20 23:26:17 2018: setting parameter 'drivers':'dummy':'rate' to value "48000"
Tue Nov 20 23:26:17 2018: Listening for D-Bus messages
Tue Nov 20 23:26:27 2018: Saving settings to "/home/jeff/.config/jack/conf.xml" ...
Tue Nov 20 23:26:40 2018: Starting jack server...
Tue Nov 20 23:26:40 2018: JACK server starting in realtime mode with priority 10
Tue Nov 20 23:26:40 2018: self-connect-mode is "Don't restrict self connect requests"
Tue Nov 20 23:26:40 2018: Acquired audio card Audio0
Tue Nov 20 23:26:40 2018: creating alsa driver ... hw:PCH,0|hw:PCH,0|1024|2|192000|2|2|nomon|swmeter|-|32bit
Tue Nov 20 23:26:40 2018: Using ALSA driver HDA-Intel running on card 0 - HDA Intel PCH at 0xd1228000 irq 129
Tue Nov 20 23:26:40 2018: ERROR:

ATTENTION: The playback device "hw:PCH,0" is already in use. Please stop the application using it and run JACK again
Tue Nov 20 23:26:40 2018: Released audio card Audio0
Tue Nov 20 23:26:40 2018: ERROR: Cannot initialize driver
Tue Nov 20 23:26:40 2018: ERROR: JackServer::Open failed with -1
Tue Nov 20 23:26:40 2018: ERROR: Failed to open server
Tue Nov 20 23:31:15 2018: ------------------
Tue Nov 20 23:31:15 2018: Controller activated. Version 1.9.12 (0+) built on Mon Oct 15 04:25:15 2018
Tue Nov 20 23:31:15 2018: Loading settings from "/home/jeff/.config/jack/conf.xml" using expat_2.2.5 ...
Tue Nov 20 23:31:15 2018: setting parameter 'engine':'driver':'(null)' to value "alsa"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'device' to value "hw:PCH,0"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'capture' to value "hw:PCH,0"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'playback' to value "hw:PCH,0"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'rate' to value "192000"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'period' to value "1024"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'duplex' to value "true"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'monitor' to value "false"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'inchannels' to value "2"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'outchannels' to value "2"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'alsa':'midi-driver' to value "raw"
Tue Nov 20 23:31:15 2018: setting parameter 'drivers':'dummy':'rate' to value "48000"
Tue Nov 20 23:31:15 2018: Listening for D-Bus messages
Tue Nov 20 23:31:46 2018: Starting jack server...
Tue Nov 20 23:31:46 2018: JACK server starting in realtime mode with priority 10
Tue Nov 20 23:31:46 2018: self-connect-mode is "Don't restrict self connect requests"
Tue Nov 20 23:31:46 2018: Acquired audio card Audio0
Tue Nov 20 23:31:46 2018: creating alsa driver ... hw:PCH,0|hw:PCH,0|1024|2|192000|2|2|nomon|swmeter|-|32bit
Tue Nov 20 23:31:46 2018: Using ALSA driver HDA-Intel running on card 0 - HDA Intel PCH at 0xd1228000 irq 129
Tue Nov 20 23:31:46 2018: ERROR:

ATTENTION: The playback device "hw:PCH,0" is already in use. Please stop the application using it and run JACK again
Tue Nov 20 23:31:46 2018: Released audio card Audio0
Tue Nov 20 23:31:46 2018: ERROR: Cannot initialize driver
Tue Nov 20 23:31:46 2018: ERROR: JackServer::Open failed with -1
Tue Nov 20 23:31:46 2018: ERROR: Failed to open server


If I try to start cadence from KLauncher, I see the blue triangular cadence icon, about the size of the mouse pointer, and then it goes away, and nothing appears. If I run it from the command line without sudo, this prints to the console:

Code: Select all

jeff@jeff-inspiron-2017:~$ cadence
Using Tray Engine 'Qt'
ERROR:dbus.proxies:Introspect error on :1.41:/org/jackaudio/Controller: dbus.exceptions.DBusException: 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, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/share/cadence/src/cadence.py", line 2394, in <module>
    gui = CadenceMainW()
  File "/usr/share/cadence/src/cadence.py", line 1232, in __init__
    self.DBusReconnect()
  File "/usr/share/cadence/src/cadence.py", line 1254, in DBusReconnect
    if gDBus.jack.IsStarted():
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: 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, the reply timeout expired, or the network connection was broken.
jeff@jeff-inspiron-2017:~$


I thought restarting jack might help. The only running service that begins with jack is jackdbus, and it respawns every time I kill it:

Code: Select all

jeff@jeff-inspiron-2017:~$ killall jackdbus
jeff@jeff-inspiron-2017:~$ killall jackdbus
jeff@jeff-inspiron-2017:~$ killall jackdbus
jeff@jeff-inspiron-2017:~$ killall jackdbus
jeff@jeff-inspiron-2017:~$ killall jackdbus
jeff@jeff-inspiron-2017:~$ killall jackdbus
jeff@jeff-inspiron-2017:~$ killall jackdbus
jeff@jeff-inspiron-2017:~$ killall jackdbus

Re: Can't start Cadence; "No Reply" error -- but maybe Cadence is already running?

Posted: Wed Nov 21, 2018 6:38 am
by rghvdberg
Which distro are you running?

Re: Can't start Cadence; "No Reply" error -- but maybe Cadence is already running?

Posted: Wed Nov 21, 2018 11:55 pm
by Jeff Brown
Ubuntu 18.04. All my sound stuff came from KXStudio, via apt. The computer's a Dell Inspiron laptop.

Re: Can't start Cadence; "No Reply" error -- but maybe Cadence is already running?

Posted: Thu Nov 22, 2018 6:48 am
by rghvdberg
Just to make sure everything is set up correctly.

Did you precisely follow the install instructions on the KX website?
People often overlook things like adding the gcc5 repo and installing kxstudio-default-settings package?

Re: Can't start Cadence; "No Reply" error -- but maybe Cadence is already running?

Posted: Thu Nov 22, 2018 10:39 pm
by Jeff Brown
KXStudio has been working well for me for nigh on a year. I'm afraid I don't remember what I did to install it.

I've been using Claudia perpetually, for everything (web browsers, mp3 players, etc.), with the PulseAudio and Alsa bridges both enabled almost always. I've been using alsamixer almost perpetually, to manage the volume between my headphones and the laptop speakers. Sometimes I would switch to an external audio interface from within Claudia to use SuperCollider or Ardour (selecting a different device, sample rate, and number of inputs and outputs), and then switch back for non-musical use. I don't remember doing anything unusual around the time that Claudia got messed up, but I did have to manually restart the computer once or twice recently, and those events may have coincided.

Re: Can't start Cadence; "No Reply" error -- but maybe Cadence is already running?

Posted: Fri Nov 23, 2018 6:25 am
by rghvdberg
Well I guess falktx should have a look at this.
Since he's not on the forum anymore try to contact him via either github, irc (freenode #kxstudio or #lad) or on the kxstudio discord channel (https://discord.gg/jAaXTe).

Re: Can't start Cadence; "No Reply" error -- but maybe Cadence is already running?

Posted: Fri Nov 23, 2018 8:55 am
by rghvdberg
Falktx on Discord wrote:that seems like the usual "run gui tools with sudo once, and now you broke your system because the same tool will need sudo again"
anyway, it is a matter of trying to remove all configs related to cadence in the home dir
ie, check which files belong to root user and delete those

ftr. my Cadence config files are in

Code: Select all

 ~/.config/Cadence/