Bug 71399

Summary: kdm: KDM fails to redisplay login screen after session ends
Product: [Unmaintained] kdm Reporter: Dominique Devriese <devriese>
Component: generalAssignee: kdm bugs tracker <kdm-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: crash    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Dominique Devriese 2003-12-29 00:40:38 UTC 
Version:            (using KDE KDE 3.1.4)
Installed from:    Debian testing/unstable Packages

Hi,

This is a forward of the following Debian bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=225285

Package: kdm
Version: 4:3.1.3-1
Severity: important

KDM will start normally when invoked and lets one log in. After the user
logs out of his current X session (doesn't matter which window manager),
kdm fails to redisplay the login screen. Instead, the user is dumped
back into a virtual console. KDM doesn't crash as such - a lone kdm
process is still shown by ps, although sleeping (strace shows it's
waiting on a select() call). The kdm process needs to be killed and KDM
restartet to obtain a new login screen.

This is the output I got in /var/log/debug after editing /etc/init.d/kdm
to use the --debug 1 argument:

Dec 28 12:28:20 minastirith kdm[5481]: Ping server
Dec 28 12:28:20 minastirith kdm[5481]: Server alive
Dec 28 12:28:20 minastirith kdm[5481]: Source reset program /etc/kde3/kdm/Xreset
Dec 28 12:28:20 minastirith kdm[5481]: source /etc/kde3/kdm/Xreset
Dec 28 12:28:20 minastirith kdm[5552]: execute: /etc/kde3/kdm/Xreset ; USER=rada
gast LOGNAME=radagast HOME=/home/radagast DISPLAY=:0 PATH=/sbin:/usr/sbin:/bin:/
usr/bin:/usr/X11R6/bin:/usr/local/bin SHELL=/bin/sh XAUTHORITY=/var/lib/kdm/A:0-
4g9S9g
Dec 28 12:28:20 minastirith kdm[5477]: select returns -1.  Rescan: 0  ChildReady
: 1  ChkUtmp: 0
Dec 28 12:28:20 minastirith kdm[5477]: signals blocked
Dec 28 12:28:20 minastirith kdm[5477]: Manager wait returns  pid 5481  sig 6  co
re 0  code 0
Dec 28 12:28:20 minastirith kdm[5477]: ScanServers
Dec 28 12:28:20 minastirith kdm[5477]: ScanAccessDatabase
Dec 28 12:28:20 minastirith kdm[5477]: ExitDisplay :0, endState = 3, forceReserv
er = 0, GoodExit = 1
Dec 28 12:28:20 minastirith kdm[5477]: Stopping display :0 to state 3
Dec 28 12:28:20 minastirith kdm[5477]:  zombiefied
Dec 28 12:28:20 minastirith kdm[5477]: Getter closed
Dec 28 12:28:20 minastirith kdm[5477]: WaitForSomething
Dec 28 12:28:20 minastirith kdm[5477]: select returns -1.  Rescan: 0  ChildReady
: 1  ChkUtmp: 0
Dec 28 12:28:20 minastirith kdm[5477]: signals blocked
Dec 28 12:28:20 minastirith kdm[5477]: Manager wait returns  pid 5478  sig 0  co
re 0  code 0
Dec 28 12:28:20 minastirith kdm[5477]: ScanServers
Dec 28 12:28:20 minastirith kdm[5477]: ScanAccessDatabase
Dec 28 12:28:20 minastirith kdm[5477]: Zombie server reaped, attempting removing
 display :0
Dec 28 12:28:20 minastirith kdm[5477]: Stopping display :0 to state 3
Dec 28 12:28:20 minastirith kdm[5477]: Removing display :0
Dec 28 12:28:20 minastirith kdm[5477]: Getter closed

at which point I'm back in the console and kdm goes fishing... :)
Comment 1 Dominique Devriese 2004-01-01 20:07:25 UTC 
I have received more info from the reporter, and it seems this is really an libpam-ldap bug, to be precise, this bug: http://www.debian.org/214900

( He found this in his kdm logs:
/home/roland/debian/openldap/build/2.1.23-1/openldap2-2.1.23/libraries/libldap/unbind.c:40:
ldap_unbind_ext: Assertion `( (ld)->ld_options.ldo_valid == 0x2 )'
failed.
)

I'm therefore closing this bug as invalid.
cheers
domi