You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Monday, March 22nd 2004, 2:07pm

Users can't login when using kdm

Hello,

I have Slackware 9.1 with the 2.6.3 kernel installed. I have now upgraded KDE to version 3.2.1 and have some trouble with the kdm login. I use runlevel 4 with kdm as default, and before the upgrade everything worked out fine (never try to repair what's not broken right?). Now when I try to login as an user, I get bounced back to the login screen before KDE starts loading. However, when I login as root it works. Also, when I switch to runlevel 3 and write startx as a user, KDE works fine. So, I guess there's some permission problem with kdm that I can't solve. Is there someone out there that might be able to explain for me what may be wrong?

A file is being created in the user's home directory called .xsession-errors and that one contain the following error messages:

stderr is not a tty - where are you?
/opt/kde/share/config/kdm/Xsession: line 1: /home/anders/LD_LIBRARY_PATH=/lib:: No such file or directory
/opt/kde/share/config/kdm/Xsession: line 1: exec: /home/anders/LD_LIBRARY_PATH=/lib:: cannot execute: No such file or directory

2

Wednesday, March 24th 2004, 2:02pm

please? :oops:

3

Wednesday, March 24th 2004, 3:41pm

Re: Users can't login when using kdm

Quoted

Original von ZenIT

stderr is not a tty - where are you?
/opt/kde/share/config/kdm/Xsession: line 1: /home/anders/LD_LIBRARY_PATH=/lib:: No such file or directory
/opt/kde/share/config/kdm/Xsession: line 1: exec: /home/anders/LD_LIBRARY_PATH=/lib:: cannot execute: No such file or directory


That looks very strange. What does your
/opt/kde/share/config/kdm/Xsession look like?
Seems like it tries to use a variable that is set to
a nonsensical value.

You might also want to check
/etc/profile
/home/anders/.bash_profile
or
/home/anders/.bashrc

There might be a line like
HOME=/home/anders/LD_LIBRARY_PATH=/lib:
that should probably be two lines:
HOME=/home/anders/
LD_LIBRARY_PATH=/lib:

or some such...