Can't determine DISPLAY. Aborting.

seashell11 · 05-16-2006, 03:33 PM

After I installed some upgrades, and new packages on my ubuntu Dapper computer it will not start up a desktop session. I previously was running breezy, but I upgraded to dapper. Everything ran fine for a month before now. When I switch to a terminal and try starting kde by running the folloing command

Code:

kdesktop

I get this error

Code:

ERROR: KUniqueApplication: Can't determine DISPLAY. Aborting.

Then the computer goes back to command line.

When I am in the kdm login manager, it starts up fine. Thin when I type in the user name and password, everything goes blank for a little bit, and then the computer goes back to the log-in manager.

reddazz · 05-16-2006, 03:45 PM

Try running "startx" instead of "kdesktop".

fragos · 05-16-2006, 09:16 PM

FYI -- if you update the display driver and it fails in some way. Your system will only boot to level 3, command line. If you update included a kernel update, you will need to re-install 3D support such as that from Nvidia. I wouldn't be surprised if the same wasn't true for ATI cards.

seashell11 · 05-17-2006, 09:59 AM

Ok, I tried running startx from the command line and this is the error that it popped up.

dlopen: /usr/lib/xorg/modules/extensions/libGLcore.so: undefined symbol: __glXLastContext

(EE) Failed to load /usr/lib/xorg/modules/extensions/libGLcore.so

(EE) Failed to load module "GLcore" (loader failed, 7)

waiting for X server to shut down FreeFontPath: FPE "/usr/share/X11/fonts/misc/" refcount is 2, should be 1: fixing.

reddazz · 05-17-2006, 10:20 AM

There is a problem with your glx settings. You can disable glx in /etc/X11/xorg by changing

Code:

Load         "glx"

to

Code:

#Load         "glx"

You will be able to log into X, but you will have no 3d acceleration. What graphics card are you using. If its nvidia, try reinstalling the driver and then enabling glx.

seashell11 · 05-18-2006, 09:53 AM

I tried doing a complete removal of all the xserver stuff and then reinstalling it. Now I get this error when I run startx from the command line.

Code:

       (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: May 18 10:31:50 2006
(==) Using config file: "/etc/X11/xorg.conf"
(EE)xf86OpenSerial: Cannot open device /dev/wacom
       No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE)xf86OpenSerial: Cannot open device /dev/wacom
       No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE)xf86OpenSerial: Cannot open device /dev/wacom
       No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE)xf86OpenSerial: Cannot open device /dev/wacom
       No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE)xf86OpenSerial: Cannot open device /dev/wacom
       No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE)xf86OpenSerial: Cannot open device /dev/wacom
       No such file or directory.
Error opening /dev/wacom : No such file or directory

waiting for X server to shut down FreeFontPath: FPE "/usr/share/X11/fonts/misc" refcount is 2, should be 1; fixing.

fragos · 05-18-2006, 01:48 PM

Wacom pads are a special case and we don't know if you have one. X thinks you do and can't find the mount point for it. Odds are you don't actually have one and installing X out of context gave this result. Probably fixable by editing wacom out of "/etc/X11/xorg.conf".

reddazz · 05-18-2006, 02:15 PM

I don't think there was any need to remove and reinstall xorg. You could have resolved your problem by following what I said above. Anyway, you now need to reconfigure X using xorgconfig or "dpkg-reconfigure xorg-x11".

seashell11 · 05-18-2006, 02:45 PM

reddaz: I did try what you said, but it still wouldn't work.

Here is a link to a copy of my xorg.conf file.

I tried running dpkg-reconfigure xserver-xorg, and that didn't do any good either. I do not have a wacom pad.

So what should I change in my xorg.conf file?

seashell11 · 05-18-2006, 02:53 PM

Ok, here is a link to what I changed my xorg.conf file to

Now when I try to run startx it still won't start, and this is the message it has:

Code:

waiting for X server to shut down FreeFontPath: FPE "/usr/share/X11/fonts/misc refcount is 2, should be 1; fixing.

fragos · 05-18-2006, 02:56 PM

I found a wacom tablet specified 3 times in your xorg.conf. Delete the following lines from xorg.conf and it may now work:

-<start of delete>-
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
-<end>-

seashell11 · 05-18-2006, 02:58 PM

fragos: yea, I did get that figured out, I just put # in front of those lines, and that error is no more. but it still doesn't work.

fragos · 05-18-2006, 03:07 PM

seashell11: Perhaps someone wiser than I can help you repair this. I'm primarily a SuSE user that has tried Ubuntu 6.06 a few weeks back. I had none of your problems. If it was me, I'd first verify the install disk and then re-install. It may not make a difference but I tried the Ubuntu live 6.06. It has an icon on the desktop to install from the live CD.

seashell11 · 05-18-2006, 03:42 PM

Ok, found out how to make it work. I was using the kdm login manager, before. Now from the command line I just typed in gdm, loaded the gdm login manager, I chose kde for the session type and everything works fine. So it must be something wrong with kdm.

reddazz · 05-18-2006, 03:46 PM

The first error was about GLX and thats the one I was referring to in my previous post. Since you managed to solve the wacom stuff, whats the exact problem that you are currently facing. Saying "it doesn't work" is not helpful since it lacks any detailed info about the problem.