Login...again?

pete_bogg · 07-10-2007, 07:10 AM

[I've seen this before, but I cannot find the post to fix it.]

I have a new 'clean' install of Slackware 12. I have seen several times where I login from the kdm screen, and end up back at the kdm screen. I put the correct username and password in, but for some reason, I have to re-enter the information.

I saw this with Slackware 11.0, and found a post to correct this, but I could not find that post again. (Unfortunately, I did not write the 'fix' in my 'administrator's notebook'.)

stress_junkie · 07-10-2007, 08:06 AM

If the normal user account could never log in then I would suspect that its home directory is not accessible. Incorrect permissions will cause this.

Your post seems to imply that the second attempt to log in is successful. Is that correct?

Do you use a second partition mounted at /home for user account home directories? It is possible that the user account partition is not mounted.

Does this affect normal user accounts and the root account? If it affects all accounts then maybe there is a problem with the kdm configuration. Here again I would look at file permissions.

Create a new user account and see if this happens on the new account.

briealeida · 07-10-2007, 12:18 PM

Do you have this issue if you log in to the CLI with that un/pw combo?

pete_bogg · 07-11-2007, 07:45 AM

stress_junkie: Typically, the second try is successful. This can occur when logging out as one user and logging in as another, or can occur from a cold boot.

briealeida: I am using runlevel 4 with kdm, so I really don't use the command line to log my users in.

all: I saw this behavior in the past when using gdm on Slackware 11.0, so I don't think it is a kdm issue.

Also, last night after logging in, I did see kdm get 'stuck' while trying to load peripherals, and reset to the login screen.

This is only a small issue among larger issues, however, it is annoying to my users.

adriv · 11-27-2007, 02:01 PM

Just wondering if pete_bogg solved the issue (and how), because I'm experiencing the same thing...
Sometimes there's nothing wrong and sometimes you have to log in twice. And indeed, sometimes stuck while trying to load peripherals.
Am using runlevel 4.

adriv · 11-28-2007, 08:38 AM

After a little experimenting I found out that the problem only persists in KDE and Xfce (not in Fluxbox) and only in runlevel 4 (in 3 everything is fine).

Alien_Hominid · 11-28-2007, 08:46 AM

Is there anything is syslog?

adriv · 11-28-2007, 09:02 AM

Xorg.0.log and Xorg.1.log don't show any errors or warnings.
The latest kdm.log (=rl3=OK) is this:

Code:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Slackware 12.0 Slackware Linux Project
Current Operating System: Linux Slackware 2.6.22.9-smp #1 SMP PREEMPT Tue Oct 9 00:16:09 CEST 2007 i686
Build Date: 09 May 2007
	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.1.log", Time: Wed Nov 28 12:47:39 2007
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
QImage::convertDepth: Image is a null image
QImage::smoothScale: Image is a null image
SetClientVersion: 0 9
SetGrabKeysState - disabled
QImage::convertDepth: Image is a null image
QImage::smoothScale: Image is a null image
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
nvClipLock: client timed out, taking the lock

The previous kdm.log (=rl4=notOK) is this:

Code:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Slackware 12.0 Slackware Linux Project
Current Operating System: Linux Slackware 2.6.22.9-smp #1 SMP PREEMPT Tue Oct 9 00:16:09 CEST 2007 i686
Build Date: 09 May 2007
	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: Wed Nov 28 09:49:30 2007
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
QImage::convertDepth: Image is a null image
QImage::smoothScale: Image is a null image
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
QImage::convertDepth: Image is a null image
QImage::smoothScale: Image is a null image

adriv · 11-28-2007, 04:15 PM

/var/log/syslog shows this error:

Code:

Nov 27 05:47:24 Slackware kdm[2699]: X server for display :0 terminated unexpectedly
Nov 27 05:47:27 Slackware kdm_greet[3104]: Can't open default user face
Nov 27 05:58:54 Slackware kdm[2699]: X server for display :0 terminated unexpectedly
Nov 27 05:58:57 Slackware kdm_greet[3221]: Can't open default user face

Alien_Hominid · 11-28-2007, 04:17 PM

This looks like X crashes, but you said that Xorg logs are normal. Strange

adriv · 11-28-2007, 04:46 PM

Indeed strange...
No errors whatsoever in xorg.*.log files.

Searching a bit further I found several postings on the web, but they are practically all about crashing (or not-starting) X-servers, which is hardly the case here.
Anyways, according to some of these posts, it might have to do with the Nvidia-driver (I do use Nvidia-drivers), like this one on LQ.org (Mandriva-forum): http://www.linuxquestions.org/questi...8/#post1598872
But what is the Slackware equivalent of /etc/modprobe.preload?

rg3 · 11-28-2007, 06:17 PM

There is no real equivalent. You could edit /etc/rc.d/rc.modules and add "/sbin/modprobe nvidia" without the quotes, or do the same to /etc/rc.d/rc.local, for example.

Alien_Hominid · 11-29-2007, 12:41 AM

But that thread is very old (i believe, it should have been fixed). I myself have nvidia and never ever experienced such problem.

adriv · 11-29-2007, 06:25 AM

I only have it on one SW-box, the other one is fine.

I'll try the "nvidia" line in /etc/rc.d/rc.local, let you know in a couple of days if it worked or not.
Thanks for the replies so far.

adriv · 11-30-2007, 06:30 AM

Quote:

Originally Posted by adriv

I'll try the "nvidia" line in /etc/rc.d/rc.local, let you know in a couple of days if it worked or not.

Unfortunately, it doesn't work...
Anyone an idea?