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

[Rui Nuno Capela]

On Thu, 29 Oct 2009 16:00:56 +0100, fons at kokkinizita.net wrote:
> On Thu, Oct 29, 2009 at 10:35:30AM -0400, Paul Davis wrote:
> 
>> 2009/10/29 Jörn Nettingsmeier <nettings at folkwang-hochschule.de>:
>> > hi rui, hi *!
>> >
>> >
>> > two hosts connected via netjack. local host uses qjackctl.
>> > now ssh -X into remote host, start qjackctl and hope for a forwarded
>> > window. no luck. all that happens is that the *local* qjackctl window
>> > pops up.
>> >
>> > this doesn't happen with other gui apps. i use several xosviews on
>> > several hosts frequently without problems.
>> >
>> > any guesses as to what might be going on?
>> 
>> guess; Qt is trying to be way too clever.
>> 
>> firefox does sort of the same thing - it registers some kind of
>> service handle with the X server, and when starting up on a given
>> display, a new firefox looks to see if the service already exists on
>> that X server.
> 
> Other guess: your WM trying to be clever. It could recognise
> the window of the remote app, think you want to local one and
> move that to the current workspace which could result in the
> two windows on top of each other.
> 
> Something like that (but harmless) happens in WindowMaker.
> When you have an app icon for e.g. qjakctl, then launch it
> on a remote machine, the icons 'start by double click' 
> function doesn't work anymore because wm thinks the app
> is already running (you can still start on the icon's 
> menu).
> 

nope. it is qjackctl itself trying to be clever by going trough x11
property ownership and make sure there can only be one single instance of
it up and running.

no system-tray nor window manager in between, it's plain xlib trickery :)

cheers
-- 
rncbc aka Rui Nuno Capela
rncbc at rncbc.org