#663468 audacious-plugins: [regression] jack output plugin fails to start jack server

Package:
audacious-plugins
Source:
audacious-plugins
Description:
Base plugins for audacious
Submitter:
"Francesco Poli \(wintermute\)"
Date:
2015-06-06 09:18:03 UTC
Severity:
normal
#663468#5
Date:
2012-03-11 15:00:18 UTC
From:
To:
Hello,
I've just upgraded audacious on my Debian testing boxes:

  [REMOVE, NOT USED] libmcs1
  [INSTALL, DEPENDENCIES] audacious-plugins-data
  [INSTALL, DEPENDENCIES] libbs2b0
  [INSTALL, DEPENDENCIES] libguess1
  [INSTALL, DEPENDENCIES] libmpg123-0
  [UPGRADE] audacious 2.4.4-1 -> 3.2.1-2
  [UPGRADE] audacious-plugins 2.4.4-1+b2 -> 3.2.1-3
  [UPGRADE] libaudclient2 2.4.4-1 -> 3.2.1-2
  [UPGRADE] libaudcore1 2.4.4-1 -> 3.2.1-2

I think I found a regression: the jack output plugin is no longer able
to start the jack server and spits out errors like the following ones,
as soon as I try to play something:

  ERR: bio2jack.c::JACK_Error(967) Cannot connect to server socket err = No such file or directory
  ERR: bio2jack.c::JACK_Error(967) Cannot connect to server socket
  ERR: bio2jack.c::JACK_Error(967) jack server is not running or cannot be started
  ERR: bio2jack.c::JACK_Error(967) Cannot connect to server socket err = No such file or directory
  ERR: bio2jack.c::JACK_Error(967) Cannot connect to server socket
  ERR: bio2jack.c::JACK_Error(967) jack server is not running or cannot be started
  ERR: bio2jack.c::JACK_OpenDevice(1019) jack server not running?

My setup used to work perfectly with audacious/2.4.4-1 and previous
versions.
I still have the environment variable set:

  $ env | grep JACK
  JACK_START_SERVER=

and the following configuration file:

  $ cat ~/.jackdrc
  /usr/bin/jackd --temporary --realtime -d alsa --softmode --hwmeter --rate 44100

If I manually start jackd with the above-quoted command-line, after starting
audacious and before attempting to play something, the jack outplug plugin
works flawlessly and I can listen to music and everything is back to normal.

But apparently, the jack output plugin fails to start the jack server,
when it does not find it already running.

Please fix this annoying bug.
Thanks for your time!
#663468#10
Date:
2013-05-17 22:17:21 UTC
From:
To:
On Sun, 11 Mar 2012 16:00:18 +0100 Francesco Poli (wintermute) wrote:

[...]
[...]

Is there any progress on this issue?
Has it been investigated?
Has my bug report been forwarded upstream?

I've just checked with audacious-plugins/3.3.4-2 and I am still able to
reproduce the bug.

Please let me know.
Thanks for your time!
#663468#17
Date:
2015-06-06 09:13:44 UTC
From:
To:
Control: found -1 audacious-plugins/3.5-1

Hello again.
I am still able to reproduce the bug with audacious-plugins/3.5-1 ...

I haven't received any reply at all for more than 3 years.
Having to manually start the jack server is really annoying.

Could this bug be addressed somehow, please?
Thanks for any help you may provide.