Rosie go fails with display error

General
1

Hi,

I (aduffeyum) tried to run ''rosie go" on puma2 today and got an error that seems to be do with X-11 and/or display opening, which starts:

[aduffeyum@puma2 ~]$ rosie go
/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/init.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
/home4/home/n02-puma/fcm/metomi/rose-2019.01.3/lib/python/rose/gtk/splash.py:56: Warning: invalid (NULL) pointer instance
super(SplashScreen, self).init()
/home4/home/n02-puma/fcm/metomi/rose-2019.01.3/lib/python/rose/gtk/splash.py:56: Warning: g_signal_connect_data: assertion ‘G_TYPE_CHECK_INSTANCE (instance)’ failed
super(SplashScreen, self).init()

As far as i’m aware nothing has changed with my accounts and ssh configs since last time rosie go worked fine for me, a week or two ago. Any suggestions?

Thanks!

Alistair

2

You can check that X11 forwarding works by opening xterm or something?

If you can’t open a pop-up, then quit out of everything and make sure that every step of your ssh-ing has X11 forwarding enabled.

I’m sure that you’re correct and this is the issue - it’s one of those annoying things that keeps happening.

3

thanks for this!

Trying xterm gives the error that display is not set:

[aduffeyum@puma2 ~]$ xterm
xterm: Xt error: Can’t open display:
xterm: DISPLAY is not set

I have ForwardX11 yes in my .ssh.config for both puma2 and archer2.

4

you can try testing the intermediate step:

ie try something on ARCHER2. Unless you have changed your emacs settings then just typing:
emacs

should make a window pop-up

If not then it’s the laptop → Archer2 step which is probably the issue

5

Thanks, I seem to have now fixed the issue.

In case its useful to anyone: the problem was with the step to Archer2. I did a verbose ssh (ssh -v …) and that showed my ssh step into Archer2 was picking up the settings from a wildcard host (Host *) in my .ssh/config file, rather than the Archer2 settings. Deleting the wildcard host from my local .ssh/config file seems to have fixed the problem.

Thanks very much for your help!

6

Good stuff.
I’m glad you found the culprit - ssh can be a pain.