Version:            (using KDE KDE 3.2.2)
Installed from:    Debian testing/unstable Packages

Note: this is a forward of the following Debian bug report:
	http://bugs.debian.org/242641

The original text of the report follows, along with a pretty interesting comment by someone else:
Original report:
	Pam really restricts login with these settings, that means I cannot 	
	open 2 console sessions and I cannot open one samba session + one
	console session. But KDM does seem to respond to the code returned by
	pam.  I am not a PAM expert but I believe that pam returns a session
	failure code and then KDM should respond showing something like
	"access denied". A while ago I also tried XDM and GDM and only one of
	those two reacted as expected. 
Interesting comment:
	I checked kdebase-3.2.1/kdm/backend/client.c and, at line 1142, there 
	are two function calls whose return value is not used : 
 
	 	pam_set_item (pamh, PAM_CONV, &pconv); /* XXX this can fail */ 
		pam_open_session (pamh, 0); /* XXX this can fail, too */ 
 
	(if I judge by the XXX comments, the author seems aware that something 
	remains to be done) 
 
	I changed these two lines to : 
		if ((pretc=pam_set_item (pamh, PAM_CONV, &pconv) != PAM_SUCCESS) 
		|| (pretc=pam_open_session (pamh, 0) != PAM_SUCCESS )) { 
		LogError ("Unable to open session for user %s : %s", curuser, 
		pam_strerror (pamh, pretc)); 
		return 0; 
		} 
 
	Then, kdm complies with the settings in limits.conf (actually, i've 
	done only one test with maxlogins). Although there is no warning 
	window to inform the user (something to add later, imho), user login 
	is denied as expected. 
 
	The LogError line doesn't seem to work and I'm not familiar enough 
	with KDE internals to know why (I've just copied and modified a 
	similar line earlier in the file). 

I hope this is enough information for you to fix this.

Thanks
domi