FS#22264 - jack2-dbus does not provide jack-audio-connection-kit or jack

Attached to Project: Community Packages
Opened by Ng Oon-Ee (ngoonee) - Friday, 31 December 2010, 10:43 GMT
Last edited by Ray Rashif (schivmeister) - Thursday, 06 January 2011, 08:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ray Rashif (schivmeister)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
jack2 provides the following:-
Provides : jack=0.118.0 jack-audio-connection-kit=0.118.0 jackdbus jack-audio-connection-kit-mp jackmp jackdmp
jack2-dbus provides the following:-
Provides : jackdbus
Both should provide at least jack-audio-connection-kit and jack, for compatibility with all other jack applications. Looking at the split PKGBUILD in abs, most likely just removing line 81 would be fine.

Additional info:
jack2-1.9.6-2 and jack2-dbus-1.9.6-2
This task depends upon

Closed by  Ray Rashif (schivmeister)
Thursday, 06 January 2011, 08:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  Update rolled to community
Comment by Ray Rashif (schivmeister) - Thursday, 06 January 2011, 06:46 GMT
This is intentional. jack2-dbus has no 'jackd' binary, and so a provision for jack is incorrect.

However, I may be wrong with regards to how 'jackdbus' works. Can you confirm that having jack2-dbus works with everything (force it for the moment)? Technically, how a jack server is started shouldn't matter to the client/app. If so, then a provision for jack wouldn't hurt.
Comment by Ng Oon-Ee (ngoonee) - Thursday, 06 January 2011, 06:58 GMT
Jack2 is a drop-in replacement for jack, such that (for example) ardour will not notice which one is running underneath it. Even qjackctl can control/monitor jack2's process (but it can't start it since its not jack_control aware).

Just did a quick test and hydrogen and qjackctl work (output sound) with jack2-dbus installed in place of jack2.

Loading...