Add a gnome-panel launcher (temporarily, of course) to screen 1 which launches the hacked gnome-terminal. Then use that to make it appear on the *wrong* screen. **What I most need the output of is a run where gnome-terminal shows up on the wrong screen.**
The other cases I would like (for comparison) are a run where gnome-terminal is launched in the same way from screen 0 and appears on screen 0, and a run where it is launched "correctly" on screen 1 (maybe via your hack.)
What I'm trying to do is figure out just where the bad terminal info is coming from, so that I work backwards and attack the problem from there.
In particular, I want to see if the environment that gnome-terminal is picking up is bad, or if the problem comes from something in the DBUS code ignoring the environment that is passed to it.
I think you're missing the point.
Add a gnome-panel launcher (temporarily, of course) to screen 1 which launches the hacked gnome-terminal. Then use that to make it appear on the *wrong* screen. **What I most need the output of is a run where gnome-terminal shows up on the wrong screen.**
The other cases I would like (for comparison) are a run where gnome-terminal is launched in the same way from screen 0 and appears on screen 0, and a run where it is launched "correctly" on screen 1 (maybe via your hack.)
What I'm trying to do is figure out just where the bad terminal info is coming from, so that I work backwards and attack the problem from there.
In particular, I want to see if the environment that gnome-terminal is picking up is bad, or if the problem comes from something in the DBUS code ignoring the environment that is passed to it.
Thanks!