x server already running on display :0

[rugger_2]

I have been getting a recurring error that says, "There appears to be an x server already running on display :0, would you like to try starting again on display :0..." If I choose yes or no, it seems to have the same affect. I end up getting another message saying that it was started on display :1. I choose okay and it is fine, it is just annoying to be getting this error every time I boot.

It was working fine previously, but started doing this about a week ago. I don't know how the displays work on OpenSUSE very well, but if I ctrl-alt-f1 I see tty1 through f6/tty6. f7 shows a black screen with a blinking cursor, and f8 shows my graphical session. I'm assuming then that f7 is display :0 and f8 is display :1. Any ideas on what may be wrong or how I can fix it? Is this likely a configuration problem or a bug?

Any ideas would be appreciated.

-rugger

[apoorv_khurasia]

What do you do to get this error? As in what command/application causes this? Do you issue these commands/start the applications in the GUI mode (i.e., kde/gnome running and you starting the app/exec the command in term window) or you are using a tty?

[rugger_2]

This happens on boot. I have default run-level 5, and during boot I see the message that run-level 5 has been reached. At that point, the screen either stays with a terminal login, or it flashes the error. If I see just the login screen then I hit ctrl-alt-f8 and I see the error message that display :0 already has xserver running. If I hit ctrl-alt-f1 I can get back to tty1. I haven't changed anything away from the default installation as far as the startup procedure. I'm too new to Suse to do that stuff.

On another note, I updated last night and there was a security patch for x11 and an apparent new version/bugfix. When I booted up this morning all the Xgl functionality was broken.

Looking through the logs I found this line in /var/log/boot.msg
Boot logging started on /dev/tty1(/dev/console (deleted)) at Mon Jan 15 04:46:21 2007

and the last part of boot log--
Master Resource Control: runlevel 5 has been reached
Skipped services in runlevel 5: smbfs nfs
<notice>killproc: kill(2606,3)

and from /var/log/system/messages--
Jan 14 15:33:14 Ares logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Jan 14 15:33:14 Ares logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Jan 14 15:33:15 Ares SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jan 14 15:33:15 Ares SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jan 14 15:33:15 Ares SuSEfirewall2: Warning: no interface active
Jan 14 15:33:17 Ares SuSEfirewall2: batch committing...
Jan 14 15:33:18 Ares SuSEfirewall2: Firewall rules successfully set
Jan 14 15:33:18 Ares kernel: bootsplash: status on console 0 changed to on
Jan 14 15:33:21 Ares kernel: sky2 eth0: enabling interface
Jan 14 15:33:27 Ares kernel: [drm] Initialized drm 1.0.1 20051102
Jan 14 15:33:27 Ares kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 177
Jan 14 15:33:27 Ares kernel: [drm] Initialized i915 1.5.0 20060119 on minor 0
Jan 14 15:33:36 Ares gdm[3935]: Display :0 is busy. There is another X server running already.
Jan 14 15:33:39 Ares gdm[3935]: Display :0 is busy. There is another X server running already.
Jan 14 15:33:46 Ares gdm[3935]: gdm_server_start: Display :0 busy. Trying another display number.

-not sure that that is anything other than tty1 is where the boot stops. I don't see the graphical boot without getting the error message or switching to f8 as I mentioned earlier.

[rugger_2]

I was able to uninstall the update from yesterday and Xgl all seems to be functioning again.

The update I had installed was

xorg-x11-server - X server:7.2-30.4
ProcRenderAddGlyphs/ProcDbeGetVisualInfo/ProcDbeSwapBuffers Memory Corruption Vulnerabilities.

This update fixes memory corruptions in the ProcRenderAddGlyphs()/ ProcDbeGetVisualInfo()/ProcDbeSwapBuffers() functions (CVE-2006-6101/ CVE-2006-6102/CVE-2006-6103).

I rolled back to 7.2-30.

Has this been an issue for anyone else?