
Hi, When I open a window on a workspace (A) and that is delayed (firefox download window is a good example since it waits for server response), and I move to another workspace (B) in the interim, the window of the latter gets pulled into the first workspace (A). Is this behavior defined and/or a bug? How to avoid this? Regards, -- Raghavendra Prabhu GPG Id : 0xD72BE977 Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977 www: wnohang.net

On Fri, Dec 28, 2012 at 5:44 AM, Raghavendra D Prabhu
Hi,
When I open a window on a workspace (A) and that is delayed (firefox download window is a good example since it waits for server response), and I move to another workspace (B) in the interim, the window of the latter gets pulled into the first workspace (A). Is this behavior defined and/or a bug? How to avoid this?
Hello Raghavendra, The usual issue would be that the "firefox download window" ends up on workspace B. For that complaint, workarounds include using XMonad.Actions.SpawnOn if the program is started from xmonad, or defining manageHooks that shift windows to the right workspace. But what you described sounds like a bug. If we can see your xmonad.hs (attach to an email, hpaste.org, etc.), it will be easier for us to figure out why this is happening. -- Adam

Hi,
* On Fri, Dec 28, 2012 at 01:27:08PM -0500, adam vogt
On Fri, Dec 28, 2012 at 5:44 AM, Raghavendra D Prabhu
wrote: Hi,
When I open a window on a workspace (A) and that is delayed (firefox download window is a good example since it waits for server response), and I move to another workspace (B) in the interim, the window of the latter gets pulled into the first workspace (A). Is this behavior defined and/or a bug? How to avoid this?
Hello Raghavendra,
The usual issue would be that the "firefox download window" ends up on workspace B. For that complaint, workarounds include using XMonad.Actions.SpawnOn if the program is started from xmonad, or defining manageHooks that shift windows to the right workspace.
I have manageHooks in place; in this case, the manageHook is for terminal to be on workspace B and firefox on workspace A and somehow the terminal gets pulled into workspace B. Note that this doesn't only happen with windows with manageHooks but any active window. To reproduce this, create a request to make a window in a time-delayed fashion, best way is to start firefox download for a busy site (or just enough for you to move to other workspace).
But what you described sounds like a bug. If we can see your xmonad.hs (attach to an email, hpaste.org, etc.), it will be easier for us to figure out why this is happening.
My xmonad.hs is https://gist.github.com/a63243e5e906f7f8802c Also I am using xmonad built on latest darcs HEAD.
-- Adam
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
Regards, -- Raghavendra Prabhu GPG Id : 0xD72BE977 Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977 www: wnohang.net

On Fri, Dec 28, 2012 at 2:05 PM, Raghavendra D Prabhu < raghu.prabhu13@gmail.com> wrote:
I have manageHooks in place; in this case, the manageHook is for terminal to be on workspace B and firefox on workspace A and somehow the terminal gets pulled into workspace B. Note that this doesn't only happen with windows with manageHooks but any active window. To reproduce this, create a request to make a window in a time-delayed fashion, best way is to start firefox download for a busy site (or just enough for you to move to other workspace).
But I tend to do this somewhat regularly, and don't see this. EXCEPT: if I'm using xcompmgr, which seems to get confused in this and similar cases. (If you use a compositing manager, it draws and positions all actual windows; an application "window" exists but is never mapped. Compositing in X is rather hacky.) Are you using xcompmgr, by any chance? I have heard that compton fixes this issue with xcompmgr, but have not been able to verify. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

I remember asking a while back about Firefox imposing a switch of workspaces when I opened a link via another program on another workspace, and got a response that it was the fault of Firefox for doing something it shouldn't. I can't remember more than that, I'm afraid, having long since stopped using Firefox! For the details, you might want to search the archives. On 15:31, Fri 28 Dec 2012, Brandon Allbery wrote:
Date: Fri, 28 Dec 2012 15:31:55 -0500 From: Brandon Allbery
Subject: Re: [xmonad] Window gets pulled into another workspace To: adam vogt , Xmonad Mailing List List-Id: "xmonad: a tiling window manager" On Fri, Dec 28, 2012 at 2:05 PM, Raghavendra D Prabhu < raghu.prabhu13@gmail.com> wrote:
I have manageHooks in place; in this case, the manageHook is for terminal to be on workspace B and firefox on workspace A and somehow the terminal gets pulled into workspace B. Note that this doesn't only happen with windows with manageHooks but any active window. To reproduce this, create a request to make a window in a time-delayed fashion, best way is to start firefox download for a busy site (or just enough for you to move to other workspace).
But I tend to do this somewhat regularly, and don't see this.
EXCEPT: if I'm using xcompmgr, which seems to get confused in this and similar cases. (If you use a compositing manager, it draws and positions all actual windows; an application "window" exists but is never mapped. Compositing in X is rather hacky.) Are you using xcompmgr, by any chance?
I have heard that compton fixes this issue with xcompmgr, but have not been able to verify.
-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

On Fri, Dec 28, 2012 at 4:05 PM, Owain Sutton
I remember asking a while back about Firefox imposing a switch of workspaces when I opened a link via another program on another workspace, and got a response that it was the fault of Firefox for doing something it shouldn't. I can't remember more than that, I'm afraid, having long since stopped using Firefox! For the details, you might want to search the archives.
But this user reports that other windows (specifically an unrelated terminal window), not the Firefox window, are being moved. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

Hi,
* On Fri, Dec 28, 2012 at 04:23:47PM -0500, Brandon Allbery
On Fri, Dec 28, 2012 at 4:05 PM, Owain Sutton
wrote: I remember asking a while back about Firefox imposing a switch of workspaces when I opened a link via another program on another workspace, and got a response that it was the fault of Firefox for doing something it shouldn't. I can't remember more than that, I'm afraid, having long since stopped using Firefox! For the details, you might want to search the archives.
But this user reports that other windows (specifically an unrelated terminal window), not the Firefox window, are being moved.
I have seen it mostly with firefox (don't remember with others) and any other type of window. Regarding compo. manager I use compton. I didn't know about the issue with xcompmgr. I will kill compton and see if that helps.
-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
Regards, -- Raghavendra Prabhu GPG Id : 0xD72BE977 Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977 www: wnohang.net

On Sat, Dec 29, 2012 at 2:54 AM, Raghavendra D Prabhu < raghu.prabhu13@gmail.com> wrote:
I have seen it mostly with firefox (don't remember with others) and any other type of window.
If it's Firefox windows and not terminal windows that switch workspaces on you, it is Firefox sending EWMH messages to steal focus, which can have the side effect of the window moving to the workspace that has the focus. Changing this requires disabling EwmhDesktops, or modifying it (there is no control for it, sadly) to disable the focus message — or inserting an earlier handleEventHook to detect and ignore the message without passing it on ("return (All False)"), which requires switching from the "ewmh" combinator to inlining it to your config, or writing a combinator of your own that you can stick in front of "ewmh" to override its handleEventHook. Additionally, note that windows normally open on the current workspace; X11 isn't smart enough to do otherwise. There's something in ManageHelpers that can attempt to relocate popup windows to the workspaces of their parents: http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-ManageHelpers.html... trailing dash is part of the URL). -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
participants (4)
-
adam vogt
-
Brandon Allbery
-
Owain Sutton
-
Raghavendra D Prabhu