Hi there!
I can't remember what spawned this issue, but it just so happened to occur while I was fiddling around with its configuration window for the JACK server trying to get it to work. That's another issue for another day, however.
It came out of nowhere and I cannot think of a single time where I messed with Cadence-specific options to make it do this. The only time I messed with the DBus was when I tried "jackdbus auto" in terminal to see if that would fix some of the issues that I was having with the JACK server, and of course that was after the Cadence issue appeared.
With this issue, I can only open Cadence once after rebooting and only open the configuration window once within the same session. Once I close Cadence or the configuration window, I have to at least suspend my session to be able to open Cadence again. I can work with it, but I'd rather not.
Here's the list of events that occur when I try to start Cadence via terminal:
PHP Code:
Using Tray Engine 'Qt'
ERROR:dbus.proxies:Introspect error on :1.52:/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 2372, in <module>
gui = CadenceMainW()
File "/usr/share/cadence/src/cadence.py", line 1200, in __init__
self.DBusReconnect()
File "/usr/share/cadence/src/cadence.py", line 1222, 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.
On a side note, I use GalliumOS. I wouldn't be surprised if my distro was causing the issues as Cadence indicates in its menu that there's issues with using Cadence in the System Checks section of the program, however I can't figure out how to spit more information. Additionally, I can't find any documentation on my situation, unless if I haven't looked hard enough.
Reinstalling Cadence does nothing to solve the issue, and I can't think of any other hotfixes to try and make it stop. I'll be willing to provide more information as needed as I'm very, very new to all of this.
DBus throws up errors upon attempting to open Cadence
