I’m sorry for the late reply.
Let me give you a simple run-down on how that “X” stuff works:
- you have some application (i.e. YaST) that want to offer a GUI - that’s called the “X client”
- the X client on *nix looks for an environment variable named “DISPLAY” - the context usually is “:0” for a local display or “somehost:0” for a remote display (see next lines)
- somewhere there’s an “X server” running, which offers to display the graphical stuff sent by the “X client”. That server may run on the same box as the client, or remotely
The X server must both be reachable the way that “DISPLAY” on the client proposes (always via TCP/IP for a remote connection, locally a “local socket” will do… usually none of your business) and it must permit the connection. You can control access permissions via the “xhosts” command - but let’s leave that for a while, until we have sorted out the basics
You say you’re connecting via SSH to the machine where YaST runs - I take it that by “it worked fine when I was running windows 7” you meant that you received YaST graphical output on your win7 machine. For this to work, the following had to happen:
- You must have had an X server software running on your Win7 machine (i.e. “Xserver”)
- You must have configured permission to access that Win7 X server from either any client machine or at least from that Linux server you’re ssh’ing to
- After logging in the the Linux machine via SSH, the DISPLAY variable must have been set in some way pointing to your Win7 machine. (There are quite a number of ways to do this… I wouldn’t want to complicate things at this moment, so I’ll resist from giving you a complete list of possibilities )
From the error message I deduct that the “DISPLAY” variable is either empty or not set at all - probably the latter. You can verify this easily by entering “echo $DISPLAY” after logging in to the Linux machine… if you get no mentionable output, then the variable isn’t set… an “empty line” means the variable exists, but is without content (or full of blanks), and if you see some “true output”, that’s what the variable contains. Could you please perform that test?
The next thing is: If my assumption about the Win7 situation was correct (graphical YaST output on your Win7 machine), then two questions arise:
- Do you still have some sort of X server installed after the Win8 upgrade?
- Did your (Win7) SSH software somehow transport the X data from the Linux machine to your Win7 machine and/or cause the DISPLAY variable to be set properly? What SSH software were/are you using (win7/win8)?
I believe Xserver must be running on the same samba/file server I’m connecting too.
Were this the case, then you’d have to physically switch from your Win7/8 machine to the server console (after starting YaST) to see and operate the graphical output I guess this wasn’t the case, was it?
As this can get a bit complicated, are you actually after this for learning purposes, or might you as well work with the curses interface of YaST? In the former case I’ll of course guide you through all of this. But in the latter case, we could shorten the discussion substantially
PS: Running “xhost” on the Linux machine isn’t a required step: You already need to have permission to connect to the X server to use “xhost”, that’s why it usually called from an existing/local graphical session. Try “xterm” instead - when everything works, you’ll see a new command prompt on the X server’s display. (If the command just “hangs”, it’s probably outputting on some unexpected X server - then just kill it with Ctrl-C.)