Comment 2 for bug 490436

Request for SRU:
1. The bug is fixed in the current development release (maverick) and this bug report is marked "Fix Released".

2.1. This bug prevents users from making connections via qjackctl's Connection window to ports (tracks in Ardour) that are renamed. The workaround for this is either to use the innocuous default names for tracks (i.e. audio 1, audio 2) which make it difficult to ascertain which track is being connected or to close all audio applications after renaming and restart them which is a substantial regression. Backporting this fix to the stable release will eliminate this regression.

2.2. The bug has been resolved by an upstream release (qjackctl-0.3.5), however qjackctl-0.3.6 is currently in the current development branch (maverick). The attached patch cherry picked the fix from qjackctl-0.3.5.

2.3. The patch will be attached to this bug report.

2.4. These are detailed instructions to reproduce the bug:
TEST CASE:
   a. start jack using qjackctl
   b. start ardour
   c. create two tracks in ardour (these are considered "ports" in qjackctl)
   d. rename one of the tracks (ports) in ardour
   e. using qjackctl Connections try to connect an input to both ports (tracks)

You will see that you can connect to the port (track) that was not renamed. You will NOT be able to connect to the renamed port (track). In fact, the Connections window in qjackctl will continue to show the original name for a renamed port (track). The Refresh button will NOT update the renamed port (track).

2.5. I am unaware of any potential regression, however if should be noted that if a regression did occur it would affect those using qjackctl (i.e. excludes practically all desktop users and only the subset of ubuntu studio users who use qjackctl).

It should also be noted that the patch was successfully tested on a fresh lucid install.