[LAU] jack2 turned verbose

David Adler david.jo.adler at gmail.com
Tue May 29 07:05:42 UTC 2012

Since a few weeks I have issues with jack2 on Arch

1. It's gone pretty verbose, filling any terminal from where a jack
application was started with lots of messages. These mingle with
the client's output, rendering it more or less unreadable.
Neither --silent nor the --verbose flag change the amount of jack's

2. It behaves as if the -T (--temporary) flag where given, i.e. exits
once all clients have closed their connections.

Some example output, which is the result of jack2 started with
jackd -d alsa -d hw:0 -p 128 -n 3, then starting and quitting mplayer.

Arch currently provides 1.9.8, but this seems unrelated to the version.
Downgrading to older jack versions or package releases does not fix
this, despite those having been perfectly fine at the time.

Compiling locally and experimenting with configure flags didn't help

Searching the web&Arch fora brought nothing up,
so here I am, asking for help.


More information about the Linux-audio-user mailing list