[LAU] qjackctl gets confused when used through ssh -X

Jörn Nettingsmeier nettings at folkwang-hochschule.de
Tue Nov 3 04:40:41 EST 2009

Rui Nuno Capela wrote:
> On Mon, 02 Nov 2009 15:08:20 +0000, Rui Nuno Capela <rncbc at rncbc.org>
> wrote:
>> On Mon, 02 Nov 2009 13:17:49 +0100, Jörn Nettingsmeier
>>> you are testing some bleeding-edge jack checkout on a brand-new,
>>> pre-alpha rt kernel patch with highly demanding clients. every two
>>> minutes, jack goes down in flames, often taking qjackctl with it (or
>>> vice versa). the settings are not saved. on the next testing iteration,
>>> stuff magically works (or ceases to work), because the settings are not
>>> what you think they are.
>>> since it only bites when you're testing, i've never got around to
>>> reporting explicit state save as a feature request, but now i've
> learned
>>> i'm not alone, i will :-D
>>> rui, how about saving state whenever the "OK" button in the setup
> dialog
>>> is pressed?
>> sure. qjackctl will get that later tonight on svn.
> better yet,
> qjackctl (svn) might work ootb without being confused anymore when
> used through `ssh -X`, even though the infamous single instance restriction
> is in effect: the origin hostname is now taken into account when discerning
> qjackctl instances against a X11 display server.

more power to you, rui!

just built svn, and it works like a charm.
thanks a lot.



More information about the Linux-audio-user mailing list