[SOLVED] Unable to launch Xserver on SuSE

valjester · 01-12-2015, 02:38 PM

I'm trying to figure out why I can't seem to do anything X related on a machine with Xserver installed. The OS is SuSE Linux Enterprise Server 11. When I try to run startx on the machine, it shows:

Code:

xauth:  creating new authority file /home/bfagent/.serverauth.3466


Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.


Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.

Invalid MIT-MAGIC-COOKIE-1 keygiving up.
xinit:  Resource temporarily unavailable (errno 11):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

If I check to see if the service is running

Code:

ps aux | grep X
root      2961  0.1  0.8 109836 24504 tty7     Ss+  15:07   0:02 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-1GpEOt/database vt7
bfagent   3515  0.0  0.0   5704   800 pts/0    S+   15:30   0:00 grep X

So the Xserver should be running right? However if I try to run

Code:

export DISPLAY=:0.0
xhost +localhost

It gives me:

Code:

No protocol specified
xhost:  unable to open display "localhost:0.0"

I get this message no matter if I set $DISPLAY to be :0, localhost:0.0, or the ip of the machine. Trying xclock also gives the same message. Any ideas on what I can do?

P.S. In case it's significant, it looks like the .Xauthority file in my /home/username directory is an empty file. I don't know if it's supposed to be or not, but maybe it's related?

John VV · 01-12-2015, 07:10 PM

on suse you do not run "startx" after a text boot

you use "gdm " or " xdm"

veerain · 01-13-2015, 03:09 AM

Quote:

If this server is no longer running, remove /tmp/.X0-lock

This means X is running.

Quote:

/usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-1GpEOt/database vt7

This also means X is running probably with GDM and in vt7 i.e in virtual terminal 7.

See if you can see gui by pressing Alt-F7 or Ctrl-Alt-F7.

Using xhost in vt is no use. You should use this inside X.

valjester · 01-14-2015, 02:24 PM

Thanks for the replies.

I don't have physical access to the machine since it's a VM, I've been running commands on it through a SSH client. I've tried connecting with Cygwin/X but when I enter

Code:

XWin -query %hostname%

it just launches a completely blank screen. No mouse or login screen. Alt+F7 and Ctrl+Alt+F7 do nothing. Is there some way I can diagnose the issue without having direct access to the machine?

I've checked and it looks like gdm is running.

Code:

ps aux | grep gdm
root      2915  0.0  0.1  66840  3628 ?        S    15:12   0:00 /usr/sbin/gdm
root      2940  0.0  0.1  53536  3164 ?        S    15:12   0:00 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
root      2951  0.2  0.8 109840 24240 tty7     Rs+  15:12   0:01 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-dfkWco/database vt7
gdm       3151  0.0  0.0  22192   596 ?        S    15:12   0:00 /usr/bin/dbus-launch --exit-with-session
gdm       3152  0.0  0.0  13448   800 ?        Ss   15:12   0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
gdm       3153  0.0  0.2 158204  7416 ?        Ssl  15:12   0:00 /usr/bin/gnome-session --autostart=/usr/share/gdm/autostart/LoginWindow/
gdm       3172  0.0  0.1  39460  5036 ?        S    15:12   0:00 /usr/lib/GConf/2/gconfd-2
gdm       3175  0.0  0.1 127444  5816 ?        S    15:12   0:00 /usr/lib/at-spi/at-spi-registryd
gdm       3178  0.1  0.4 272472 12816 ?        Ssl  15:12   0:01 /usr/lib/gnome-settings-daemon/gnome-settings-daemon --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins
gdm       3180  0.0  0.1 121892  3504 ?        Ssl  15:12   0:00 /usr/lib/bonobo/bonobo-activation-server --ac-activate --ior-output-fd=12
gdm       3185  0.0  0.3 230168 10600 ?        Ss   15:12   0:00 gnome-power-manager
gdm       3188  0.0  0.0  43416  2148 ?        S    15:12   0:00 /usr/lib64/gvfs/gvfsd
gdm       3189  0.0  0.3 216880 10184 ?        S    15:12   0:00 metacity
gdm       3190  0.2  0.6 248656 18216 ?        S    15:12   0:01 /usr/lib/gdm/gdm-simple-greeter
root      3196  0.0  0.1  89464  3612 ?        S    15:12   0:00 /usr/lib/gdm/gdm-session-worker
gdm       3203  0.0  0.1 186544  3124 ?        Ssl  15:12   0:00 /usr/bin/pulseaudio --start --log-target=syslog
root      3308  0.0  0.0   5700   800 pts/0    R+   15:21   0:00 grep gdm

However if I try running gdm -version or gdm-debug or anything other than gdm-help, I get the following message (running as root):

Code:

gdm -debug

** (gdm:3312): WARNING **: Failed to acquire org.gnome.DisplayManager

** (gdm:3312): WARNING **: Could not acquire name; bailing out

valjester · 01-19-2015, 09:37 AM

gdm was running, I could see the login screen if I connected to the console via VMWare vSphere Client. Still not sure why I couldn't see it if I connected with Cygwin/X, but for now that solves my problem as I just needed access to a GUI one way or another.