Bug#259786: xserver-xfree86: Mouse is blocking

[Alexandre Touret]

Hi adding the module psmouse in my /et/modules file seems to solve my problem....I am waiting a little time to be sure that is THE solution. Thanks for your help Alexandre Branden Robinson wrote: On Tue, Jul 27, 2004 at 10:15:14PM +0200, Alexandre Touret wrote: When I leave my mouse without do it anything, she is beeing blocked on my screen. Then, the only solution I haved found is to restart X :-( Furthermore, during kdm or gdm startup, when I don t touch the mouse, the mouse is blocked after gnome startup. This occured after my last upgrade of xfree Thanks for helping [...] OK I will try tonight. I have an other bug which are in the same way :-(. The keyboard is also blocking. The only failsafe way is to change the display manager. Maybe you're experiencing a problem described in the FAQ: http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ.xhtml#xdmdiffconsole How do I tell xdm to start the X server on a different virtual console? People who have customized /etc/inittab to add virtual consoles beyond the six that is the default Debian configuration often find that the xdm and getty programs "collide" and often leave the console in an unusable state. Debian's xdm program ships with a configuration that tells it to start one local X server on virtual console 7. This works fine with the default Debian /etc/inittab, but not so well for people who have changed inittab to start a getty on VC 7. If you have increased your number of virtual consoles, or otherwise require VC 7 for some purpose, simply edit /etc/X11/xdm/Xservers and change the "vt7" argument on the ":0" server line to whatever VC is appropriate for your machine (vt8, vt12, etc.). Note that while the XFree86 manual page says that if the "vt" argument is not specified, the X server will use the first available virtual console, it is not a good idea to omit this parameter when starting local X servers with xdm. This is because even though xdm starts at the very end of the init sequence, well after the getty processes that manage the virtual consoles, some machines get through the init sequence so quickly that getty has not yet claimed its VC's before xdm starts. This leads to exactly the same kind of console lockup you get as if you deliberately tell getty (via /etc/inittab) and xdm (via /etc/X11/xdm/Xservers) to use the same virtual console for their respective tasks. Does the above sound like a plausible explanation? You may want to check your /etc/inittab and configuration files for kdm and gdm. -- ______________________________ Alexandre Touret 62, avenue de Paris Bâtiment B 92320 CHATILLON tél: 06/16/57/29/74 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://alexandre.touret.free.fr/ ICQ: #96115847 Jabber: [EMAIL PROTECTED]