[sisyphus] валится сеанс kde при запуске 2-го аккаунта

[Alexandr Isaev]

пользую kdm для входа в систему. Регистрируюсь под одним аккаунтом в vt7 
display :0, загружается kde.
Запускаю второй сеанс (другой аккаунт) в vt8 display :1 по завершении 
загрузки второго сеанса вылетает первый. Кто в этом виноват (xorg, kde 
или kdm) четко понять не могу. В логах вот-такая дрянь:
=== ~/.xsession-errors:0 ===
SIM-IM: 14/01/2007 10:00:54 [DBG] Level: 1770 [07D0 0050]
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kicker: sighandler called
*** kdesktop got signal 1 (Exiting)
klauncher: Exiting on signal 1
klauncher: Fatal IO error: client killed
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
kicker: sighandler called
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
       after 34 requests (32 known processed) with 0 events remaining.
kicker: sighandler called
kicker: Fatal IO error: client killed
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kicker: sighandler called
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
KWrited - Слушает устройство /dev/pts/0
=== endlog ====

=== /ver/log/messages ===
Jan 14 10:00:54 monstr gconfd (sveta-4609): Received signal 15, shutting 
down cleanly
Jan 14 10:00:54 monstr gconfd (sveta-4609): Exiting
Jan 14 10:00:55 monstr kdm[3811]: X server for display :0 terminated 
unexpectedly
Jan 14 10:01:02 monstr crond[6498]: (root) CMD (run-parts /etc/cron.hourly)
....
=== endlog ===

== /var/log/Xorg.0.log.old ==
Backtrace:
0: X(xf86SigHandler+0x81) [0x80d5c45]
1: [0xa7fd7420]
2: /usr/lib/X11/modules//libfb.so(fbCopyNtoN+0x1ff) [0xa7253aa7]
3: /usr/lib/X11/modules//libfb.so(fbCopyRegion+0xbd) [0xa7252a0d]
4: /usr/lib/X11/modules//libfb.so(fbDoCopy+0x465) [0xa7253057]
5: /usr/lib/X11/modules//libfb.so(fbCopyArea+0x78) [0xa7253210]
6: /usr/lib/X11/modules/drivers//nvidia_drv.so [0xa7312731]

Fatal server error:
Caught signal 11.  Server aborting
=== endlog ===

Как вычислить кто посылает консоли kill и как это дело победить?