[pkg-nvidia-devel] Bug#583312: since update to initscripts, sysv... to version 2.88.dfs-5 -- kdm "fails" to load

[Andreas Beckmann]

Hi Hans,

On 2010-07-21 23:02, Hans-J. Ullrich wrote:
> I do not think, the problem is caused by by nvidia-glx-driver. I checked it 
> out, and got the same results by using gdm, xdm or kdm, and as well as with 
> the vesa driver and xserver-xorg-nv. In all cases I got the same efect: the 
> login-manager did not start, the x-server did not start, exactly as the first 
> bugreport described this behaviour. 

since you can reproduce the problem without the proprietary nvidia
driver, can you "solve" it by increasing the timeouts used by
kdm/gdm/xdm? What values do you need for reliable operation?
What about gdm3?

Can you give a short list of the components in your system (CPU, RAM,
disks, ...), eventually someone can identify something particular "slow"
in your machine - the reason why this problem is so hard to reproduce on
other systems. Do you use anything "exotic" in hard- or software?


Andreas

PS, the timeout variables for gdm/kdm are here (from
nvidia-graphics-drivers NEWS.Debian):

 For 'kdm' edit /etc/kde4/kdm/kdmrc and set  (see #583312)
    [X-*-Core]
    ServerTimeout=120

  For 'gdm' edit /etc/gdm/gdm.conf and set  (see #521699)
    [daemon]
    GdmXserverTimeout=30

  For 'gdm3' the default timeout setting seems to be sufficient.