| View previous topic :: View next topic |
| Author |
Message |
iRET
n00b
Joined: 28 Sep 2003
Posts: 17
Location: Spain
|
 Posted: Fri Dec 26, 2003 1:22 pm Post subject: kdm fails to start KDE |
 |
|
Some change on my system has made kdm fail to start kde, though /etc/rc.conf seems to be fine.
KDE starts perfectly when I do 'startx' from the console or use xdm as the display manager, so I guess it is a failure on some kdm config. Right now, I only get a blank console: typing 'startkde' on it makes KDE start.
/var/log/kdm.log seems to be fine, apart from lots of font renderer errors I still haven't have time to solve.
Might / might not be related to this, but I can't seem to 'su root' on KDE
 |
|
| Back to top |
|
 |
iRET
n00b
Joined: 28 Sep 2003
Posts: 17
Location: Spain
|
| Posted: Fri Dec 26, 2003 2:15 pm Post subject: |
|
|
I switched to gdm + full-screen ksplash, wich makes a rather nice combo and bypasses the kdm problem even if it doesn't solve it. It would still be good where the problem was coming from, though...
The 'su' problem is definetely not related to this, as I'm having same permission denial on the vt's. Any clues about this? |
|
| Back to top |
|
|
iRET
n00b
Joined: 28 Sep 2003
Posts: 17
Location: Spain
|
| Posted: Sat Dec 27, 2003 3:54 pm Post subject: |
|
|
Ok, 'permission denied' problem solved... I had removed myself from the wheel group, the users that can 'su root'.
This is clearly stated in the Gentoo FAQ http://www.gentoo.org/doc/en/faq.xml#doc_chap3_sect7.
Silly me  |
|
| Back to top |
|
|
g-man
n00b
Joined: 19 Jan 2003
Posts: 42
Location: Fort Collins CO
|
| Posted: Sun Mar 21, 2004 11:59 pm Post subject: Same problem |
|
|
| I am having the same problem after compiling kde 3.2.1. Anyone have a clue why kdm is failing. I am not really interested in bypassing the problem. |
|
| Back to top |
|
|
Kileak
n00b
Joined: 12 Jun 2003
Posts: 37
Location: Giessen, Germany
|
| Posted: Mon Mar 22, 2004 1:02 am Post subject: |
|
|
Hmm, does KDEDIR points to the right path?
Perhaps you should try to start kdm from the console with
/usr/kde/3.2/bin/kdm
If this helps, it could perhaps be a problem with KDEDIR... |
|
| Back to top |
|
|
g-man
n00b
Joined: 19 Jan 2003
Posts: 42
Location: Fort Collins CO
|
| Posted: Fri Mar 26, 2004 1:31 am Post subject: KDM Fails |
|
|
I tried
| Quote: |
Perhaps you should try to start kdm from the console with
/usr/kde/3.2/bin/kdm
|
and it did nothing but return to the prompt  |
|
| Back to top |
|
|
eSinner
Tux's lil' helper
Joined: 13 Mar 2004
Posts: 89
Location: Australia
|
| Posted: Fri Mar 26, 2004 6:22 am Post subject: Give this a shot. |
|
|
I was having this same problem. After sitting down for the better part of the day scanning through X and KDE config files a friend of mine came to a remedy that worked for my box:
You see, after emerging from KDE 3.2.0 to 3.2.1 I was unable to get kdm working for a graphical login even though my /etc/rc.conf file was setup correctly with:
| Quote: | DISPLAYMANAGER="kdm"
XSESSION="kde-3.2.1" |
and i had also run a
| Code: | | rc-update add xdm default |
It would just dump me to a console prompt after startup  . What needed to be done to fix this problem with my system was to edit /usr/kde/3.2/share/config/kdm/Xservers like so:
| Code: | | nano /usr/kde/3.2/share/config/kdm/Xservers |
to add the line:
| Quote: | | :0 local@tty1 /usr/X11R6/bin/X :0 -nolisten tcp vt7 |
as this line had somehow been removed in the process of emerging to 3.2.1.
After rebooting kdm was nice enough to start working again. Hope this helps some of you guys experiencing this same problem. 
_________________
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://www.esinner.com/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
|
| Back to top |
|
|
thomasando
Tux's lil' helper
Joined: 05 Apr 2003
Posts: 94
|
| Posted: Fri Mar 26, 2004 6:44 am Post subject: |
|
|
As Josh was saying, edit your /usr/kde/3.2/share/config/kdm/Xservers file, and make it look like this:
| Code: |
# Xservers - local X-server list
#
# This file should contain an entry to start the server on the
# local display; if you have more than one display (not screen),
# you can add entries to the list (one per line).
# If you also have some X terminals connected which do not support XDMCP,
# you can add them here as well; you will want to leave those terminals
# on and connected to the network, else kdm will have a tougher time
# managing them. Each X terminal line should look like:
# XTerminalName:0 foreign
#
:0 local@tty1 /usr/X11R6/bin/X -nolisten tcp vt7
#:1 local@tty2 reserve /usr/X11R6/bin/X -nolisten tcp :1 vt8
#:2 local@tty3 reserve /usr/X11R6/bin/X -nolisten tcp :2 vt9
#:3 local@tty4 reserve /usr/X11R6/bin/X -nolisten tcp :3 vt10
#:4 local@tty5 reserve /usr/X11R6/bin/X -nolisten tcp :4 vt11
|
this seems to be the default setup from my kde 3.2 screen, and yes, after I modified josh's one (which stopped before it defined the X servers), it worked straight away. Just type 'kdm' from the console and it will start again... |
|
| Back to top |
|
|
g-man
n00b
Joined: 19 Jan 2003
Posts: 42
Location: Fort Collins CO
|
| Posted: Fri Mar 26, 2004 11:13 pm Post subject: That did the trick |
|
|
| Thank thomasandos! The edit to /usr/kde/3.2/share/config/kdm/Xservers file corrected the problem. My wife is now speaking to me again since she can again login properly. |
|
| Back to top |
|
|
|
Desktop Environments
