Why can't I startx KDE?

bloodtie · 05-10-2007, 11:13 PM

Just installed Ubuntu server 7.04 [Feisty Fawn]. The reason I'm writing is that I'm a comparative newbie to Linux, having tolerated Windoze for years. I am in the process of setting up OTRS, so I've used the LAMP server setup. After doing the apt-get install KDE, I restarted and thought I could start KDE with startx. Unfortunately, the error messages:

xauth: Creating new authority file /home/warren/serverauth.4050
xauth: /home/warren/.Xauthority not writable, changes will be ignored
xauth: error in locking authority file /home/warren/.Xauthority
xauth: error in locking authority file /home/warren/.Xauthority
xauth: error in locking authority file /home/warren/.Xauthority
X: cannot read /etc/X11/X symbolic link (Invalid argument), aborting.giving up
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error
xauth: error in locking authority file /home/warren/.Xauthority

Then I go back to the command prompt. I tried doing it using sudo startx, but got the same results. What to do?

unknownmosquito · 05-10-2007, 11:17 PM

This can be for a number of reasons, check your permissions (paste the output of ls -l .Xauthority ) and your hard drive capacity (paste the output of df -h)

bloodtie · 05-28-2007, 04:24 PM

Quote:

Originally Posted by bloodtie

Just installed Ubuntu server 7.04 [Feisty Fawn]. The reason I'm writing is that I'm a comparative newbie to Linux, having tolerated Windoze for years. I am in the process of setting up OTRS, so I've used the LAMP server setup. After doing the apt-get install KDE, I restarted and thought I could start KDE with startx. Unfortunately, the error messages:

xauth: Creating new authority file /home/warren/serverauth.4050
xauth: /home/warren/.Xauthority not writable, changes will be ignored
xauth: error in locking authority file /home/warren/.Xauthority
xauth: error in locking authority file /home/warren/.Xauthority
xauth: error in locking authority file /home/warren/.Xauthority
X: cannot read /etc/X11/X symbolic link (Invalid argument), aborting.giving up
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error
xauth: error in locking authority file /home/warren/.Xauthority

Then I go back to the command prompt. I tried doing it using sudo startx, but got the same results. What to do?

Finally figured out what to do. Thanks to everyone for their suggestions. Maybe I took the easy way out, I switched to RedHat 9 (Shrike) Cool Name!

UhhMaybe · 10-10-2007, 12:54 AM

KDE has dependencies. Try here...http://kde.org/ Also here...http://kde.org/documentation/ Hope this helps YOU.

Wim Sturkenboom · 10-10-2007, 06:15 AM

Why did you pick an 'ancient' distro. Some reasons not to do so:

no longer supported, so your box might be at risk when connected to the internet
older versions of software
might not support newer hardware (I have an RH8 box that does not read my USB stick)

It does not seem to matter to you which distro you use (as this is the second one), so I would use a more recent distro. If you want to stick with a RedHat derivative, consider Centos.

Just a thought (the given points might not be of any importance for you).

cornish · 10-10-2007, 06:22 AM

Why do you want to run kde on the server, Ubuntu server is meant to run from shell/command.

You could have looked into webmin

upgrade not downgrade put ubuntu back on now!!!!

cornish · 10-10-2007, 06:27 AM

Also you could try

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install kubuntu-desktop

Kahless · 10-10-2007, 10:42 AM

If you want redhat:

USE: fedora core for bleeding edge, always reinstalling, always having the latest and gratest

USE: Centos for stable and slow upgrade cycle, lower maintmance

IMO ubuntu would have been a better match for you... but you probably would have been a better match for you if you get it working properly. Might be better to start off with the desktop install, and add servers as you get to know how to use them. Running servers you don't actually need/use is silly.