brockgr
csshX windows are "hidden" if launched to a screen that isn't the active screen in os x Mavericks
Steps to Reproduce
1. Using a Mac running Mavericks and set up with multiple monitors/screens
2. Move your terminal to a window/screen 2 there by making screen 2 active
(the top bar in the display will be brighter)
3. From that terminal launch csshX against some cluster. (leave the screen
setting as default = 1)
4. The windows will flash open and then seem to disappear. However, if you
use "App Expose" on the Terminal you'll see that the windows are still there,
but seem to be inaccessible.
5. Now if instead of leaving the screen setting to the default, change it to 2
the same as your terminal and relaunch csshX, and it opens as expected.
It appears that csshX fails to open properly if launched to a target screen
that is not the active screen.
I'm on OS X 10.9 and using csshX 0.74.
Original issue reported on code.google.com by [email protected] on 24 Oct 2013 at 9:29
I'm seeing the same issue. The suggested fix from step #5 of running `csshX
-screen 2 <host1> ...<hostn>` works.
Original comment by [email protected] on 19 Nov 2013 at 4:31
I too have this problem. Thanks marsh for the solution
Original comment by [email protected] on 8 Apr 2014 at 8:14
I have this problem as well. The workaround suggested by Marsh works, thanks!
I also have the problem that if you open the windows on a screen other than the
"primary" (the one with the dock), that they don't quite fit properly (likely
due to the menu at the top which wasn't there in previous releases).
Workaround: CTRL+A, B, ENTER
(reset the "bounds" which seems to fix the windows geometry so they fit
properly)
Original comment by [email protected] on 8 Apr 2014 at 3:49
The workaround definitely seems to be working.. do we have a permanent fix in
the works?
Original comment by [email protected] on 25 Jun 2014 at 3:13
Put together a small zsh function called "activate":
activate () {
app=$1
echo "tell application \"$app\" to activate" | osascript
}
You can then use it with csshx: "csshx user@host; activate terminal"
Which seems to help.
Original comment by [email protected] on 29 Aug 2014 at 5:02
The -screen workaround doesn't help if you then later reposition to another
monitor. Once you make a false move to another screen, all of the windows are
as good as dead.
This is a critical bug, and it's been open for almost a full year. Any idea on
what it will take to get it fixed?
Original comment by [email protected] on 10 Sep 2014 at 10:36
I tried this and it works like charm.
1) Open mission control in "System Preferences"
2) Uncheck "Display have Separate spaces"
3) logout or restart
csshx -screen 2 user@host1 user@host2 worked fine.
Original comment by [email protected] on 1 Oct 2014 at 7:55
Yea, but separate spaces per screen is a *vast* improvement that I don't really
want to disable. Thanks for the workaround though :)
Original comment by [email protected] on 1 Oct 2014 at 8:49
Selecting the terminal window and then toggling it to full screen makes it show
up. Toggling off full screen makes it visible again.
Original comment by [email protected] on 8 Nov 2014 at 5:05
Hi Guys,
A lot of us out there who are using CSSHX use multiple screens. This seems a deal breaker for me. For now I have written a slim-down version of CSSHX until this issue is fixed.
I don't see the problem when using the version in:
https://github.com/carenas/csshx
anyone interested on giving it a try for your setup?
@carenas your version fixes the problem for me, on macos 10.12.6, with two side-by-side displays (not using the workarounds from https://github.com/brockgr/csshx/issues/76#issuecomment-128536277 of turning off separate spaces per screen or specifying the screen in the csshx arguments).
