Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have the Jack Audio Connection Kit (JACK) installed, but cannot seem to get jack_control start to start the service.

I'm using Slackware64-current, which recently updated its /etc/dbus-1/system.conf to have a more restrictive configuration:

<!-- ... -->
<policy context="default">
  <!-- All users can connect to system bus -->
  <allow user="*"/>

  <!-- Holes must be punched in service configuration files for
       name ownership and sending method calls -->
  <deny own="*"/>
  <deny send_type="method_call"/>

  <!-- Signals and reply messages (method returns, errors) are allowed
       by default -->
  <allow send_type="signal"/>
  <allow send_requested_reply="true" send_type="method_return"/>
  <allow send_requested_reply="true" send_type="error"/>

  <!-- All messages may be received by default -->
  <allow receive_type="method_call"/>
  <allow receive_type="method_return"/>
  <allow receive_type="error"/>
  <allow receive_type="signal"/>

  <!-- Allow anyone to talk to the message bus -->
  <allow send_destination="org.freedesktop.DBus"/>
  <!-- But disallow some specific bus services -->
  <deny send_destination="org.freedesktop.DBus"

Ever since the update, running jack_control start as a regular user produces the following error:

--- start
DBus exception: org.jackaudio.Error.Generic: failed to activate
dbusapi jack client. error is -1

It did not do this before. The new configuration file says I'm supposed to punch a hole for it in the service configuration files, but I'm baffled as to how I'm supposed to do that. I'm not even quite sure what DBUS has to do with JACK.

If you could please help me by giving me a little background information or lending me your expertise regarding configuration of DBUS, I would be most grateful.

Extra information:

  • JACK2 SVN revision 4120 (2011-02-09)
  • DBUS version 1.4.1
  • DBUS-Python version 0.83.1
share|improve this question
up vote 1 down vote accepted

I figured this out a while ago. Turns out it was a CAS-ARMv7 patch to JACK that broke DBUS functionality and I managed to fix using this patch. The issues were resolved some time ago in the JACK subversion repository and it works fine now.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.