Results 1 to 7 of 7
Hello everyone,
I have tried to configuring x windows by using xf86config but I keep getting the following messages when I start it. I think that KDE is all buggered ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 06-02-2007 #1Just Joined!
- Join Date
- Jun 2007
- Posts
- 3
Please help - KDE not starting up in Slackware
Hello everyone,
I have tried to configuring x windows by using xf86config but I keep getting the following messages when I start it. I think that KDE is all buggered up.
This is what I get when I type in startx. Just to warn you, I am a complete noob when it comes to Linux
root@bombay:~# startx
xauth: creating new authority file /root/.serverauth.2025
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/bombay:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 6.9.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 6.9
Build Operating System: Linux 2.4.33.3 i686 [ELF]
Current Operating System: Linux bombay 2.4.33.3 #1 Fri Sep 1 01:48:52 CDT 2006 i686
Build Date: 16 September 2006
Before reporting problems, check X.Org Wiki - Home
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 1 22:55:48 2007
(==) Using config file: "/etc/X11/xorg.conf"
(EE) I810(0): [agp] Unable to allocate system texture memory. Disabling DRI.
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
kde-config: error while loading shared libraries: libexpat.so.1: cannot open shared object file: No such file or directory
xset: bad font path element (#6
, possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
xset: bad font path element (#6
, possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
startkde: Starting up...
kdeinit: error while loading shared libraries: libexpat.so.1: cannot open shared object file: No such file or directory
startkde: Could not start kdeinit. Check your installation.
- 06-02-2007 #2
It seems like X cannot find the expat library. Is it installed on your system?
- 06-02-2007 #3Just Joined!
- Join Date
- Jun 2007
- Posts
- 3
xpat library? I am not sure, how would I check that?
- 06-02-2007 #4
What is the output of running
Code:#find /usr -name "libexpat*"
- 06-02-2007 #5Just Joined!
- Join Date
- Jun 2007
- Posts
- 3
root@bombay:~# find /usr -name "libexpat*"
/usr/lib/libexpat.so.0
/usr/lib/libexpat.a
/usr/lib/libexpat.so.0.5.0
/usr/lib/libexpat.la
/usr/lib/libexpat.so
One thing I forgot to mention is that this is a fresh out of the box installation of Slackware. I did a full install of slackware
- 06-02-2007 #6Linux is not only an operating system, it's a philosophy.
Archost.
- 06-06-2007 #7Oh oh... Why? Did you brake it?
Originally Posted by desiguy
With a fresh install of Slack KDE should work just fine. It's just that Slack doesn't boot into graphics mode by default. This can be changed of course. Have you gotten KDE to work once on your system? If not, I guess a reinstall might be fastest.


Reply With Quote

