Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone. I am very new to linux, and have installed Slackware 10.1 on a new system and I'm having a lot of difficulty starting KDE. when I type startkde I get a lot of the following.
xsetroot: unable to open display
xset: unable to open display
xset: unable to open display
xset: unable to open display
xsetroot: unable to open display
startkde: starting up
startkde: running kpersonalizer
kwin: cannot connect to x server
kpersonalizer: cannot connect to x server
and that last line continues to repeat.
What am I doing wrong here?
I am logged in as root and slackware is installed on /dev/hda1.
Firstly, don't login as root - create a normal user account and log in as that. You may mess up your system if you do something accidental and wrong as root.
To get KDE running: first run "xwmconfig" as your normal user (minus the quotes) and select KDE as your window manager. Then run "startx" (again, as the user and without the quotes).
ok, I did that, and went through all of the prompts, all of this while logged in a new user not root, and it saved the file and then I typed startx and it gave me the same fatal error.
Originally posted by conner19 ok, I did that, and went through all of the prompts, all of this while logged in a new user not root, and it saved the file and then I typed startx and it gave me the same fatal error.
Where did you save the file ? The file has to be saved as /etc/X11/xorg.conf
A non-root user cannot write to the /etc directory.
You ran the command xorgconfig as a non-root user, right !
Then in the end it would have asked you where to save the file and by what name. By default (if you were non-root) it would have saved the file in the current directory as xorg.conf
You have two options at hand :
1) run xorgconfig as a root user and save the file as /etc/X11/xorg.conf or,
2) run xorgconfig as a non-root user, save the file as xorg.conf in your current directory. Then as root replace the original /etc/X11/xorg.conf by the one you just created.
Also, I would like to point out that the file has to be saved as /etc/X11/xorg.conf and not /etc/x11/xorg.conf ( I think that was a typo )
Linux is case sensitive !
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/Linux:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.4.29 i686 [ELF]
Current Operating System: Linux Linux 2.4.29 #6 Thu Jan 20 16:30:37 PST 2005 i686
Build Date: 23 January 2005
Before reporting problems, check http://wiki.X.Org
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: Thu Sep 22 20:35:59 2005
(==) Using config file: "/etc/X11/xorg.conf"
(EE) VGA(0): Driver can't support depth 24
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
I don't understand. I choose just a generic VGA compatible adapter with the lowest settings and it still doesn't work.
Originally posted by conner19 ok, here it is when I type startx at the prompt.
Code:
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/Linux:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.4.29 i686 [ELF]
Current Operating System: Linux Linux 2.4.29 #6 Thu Jan 20 16:30:37 PST 2005 i686
Build Date: 23 January 2005
Before reporting problems, check http://wiki.X.Org
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: Thu Sep 22 20:35:59 2005
(==) Using config file: "/etc/X11/xorg.conf"
(EE) VGA(0): Driver can't support depth 24
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
Hey Conner19,
the problem is coz somehow your graphics card doesn't like the default depth of 24
Reduce the default depth to some lower no. like 16. Here do this :
Open up your xorg.conf file.
Go to the monitor section
Change the default depth there, i.e reduce it to some lower value. Note that, the value that is uncommented (without # sign), is the one that is being used. Save the file and startx again.
Try this with different depths. Tell us what happened.
Some examples of this are :
Code:
# DefaultDepth 8
DefaultDepth 16
# DefaultDepth 24
# DefaultDepth 32
Here depth of 16 is being used
To use depth of, say 8
Code:
DefaultDepth 8
# DefaultDepth 16
# DefaultDepth 24
# DefaultDepth 32
Here depth of 8 is in use
Also take a look at this thread. It also deals with a similar problem.
Ok, something you'll have to understand about me. I'm a complete Windows guy, who is learning linux. I have a Linux + study book to help me, but I still do not completely know how to do these things. I checked the file and it's saying
In linux much information is stored in configuration files. In these files usually '#' is used to indicate a comment. like // or /* */ in C/C++
Suppose, you wanted to state what changes you made to get your X running. You could add a comment like :
Code:
Section "Screen"
Identifier "Screen 1"
Device "diamond stealth"
Monitor "dell828fs"
# Changed the default depth to 16 and it worked !
DefaultDepth 16
The whole point is that commented lines i.e. lines beginning with a # sign are ignored by whatever program, that reads that particular file. Therefore, when a program encounters this :
ok, I understand that I need to edit the 24 to 16, but how do I actually do that from the command line? I know how to display the contents of the file, but how do I edit it? do I have to go through xorgconfig again? and if so, at what point to I set it to default on 16?
type "vi /etc/X11/xorg.conf" and vi should load up the configuration file. vi works either in command mode or insert mode. press esc for command mode and type i for insert mode. the bottom right of the screen should tell you what mode youre in. then just go down to the monitor section and edit the file. then go back to command mode and type ":wq" and press enter. this writes the file and quits vi.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.