16 Feb
2012
16 Feb
'12
9:57 a.m.
On Wed, 15 Feb 2012 13:13:20 +0000
leee <leee(a)spatial.plus.com> wrote:
Hi,
I'm frequently experiencing a problem with kdm-trinity (V3.5.12) appearing to
time out on system start-up. The following two lines are put into my syslog
when this happens:
kdm[1966]: X server startup timeout, terminating
kdm[1966]: X server for display :0 can't be started, session disabled
This is an intermittant problem and doesn't happen every time I start my
system (I'd guess it occurs about 50% of the time). When it does I'm left
with just the basic console. However, all I need to do to get X up and
running is to log in on the console and restart kdm-trinity.
The system is running Debian Squeeze on amd64 with an nVidia graphics card
using the proprietary nVidia driver.
A similar bug seems to be filed against KDM in several distros (usually it's
against the KDE4 KDM, but I've found one mention that predates it). The
recommended fix is to open up kdmrc and add a line like
ServerTimeout=120
to the [X-*-Core] section. I don't know whether or not Trinity will
recognize that config option, but it might be worth trying.