From owner-freebsd-questions@FreeBSD.ORG Mon May 16 17:55:31 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCE1216A4CE for ; Mon, 16 May 2005 17:55:31 +0000 (GMT) Received: from vsmtp2.tin.it (vsmtp2alice.tin.it [212.216.176.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DEC343DCF for ; Mon, 16 May 2005 17:55:31 +0000 (GMT) (envelope-from vdm.fbsd@virgilio.it) Received: from [192.168.10.8] (62.211.198.35) by vsmtp2.tin.it (7.0.027) id 4288B9D100019489 for freebsd-questions@freebsd.org; Mon, 16 May 2005 19:55:26 +0200 From: Vittorio De Martino To: freebsd-questions@freebsd.org Date: Mon, 16 May 2005 19:55:15 +0200 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200505161955.15328.vdm.fbsd@virgilio.it> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: kde & kdm & mouse - AGAIN X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2005 17:55:31 -0000 I have the latest installation of freebsd 5.4 on my laptop, kde & kdm 3.4. The laptop has a synaptic mousepad endowed of two buttons that in normal conditions are not used at all being enough to double-hit on the pad to ha= ve the same effect as that of pressing the left button. Now at boot time I enabled moused # ps ax|grep moused 493 ?? Ss 0:00.54 /usr/sbin/moused -p /dev/psm0 -t auto And the following in /etc/X11/xorg.conf =2E............................................... Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5" EndSection =2E................................................ Now it happens that: 1) If I start kde as a user by means of the command startx (having put startkde into .xinitrc) the mouse(-pad) works as expected: I can move around the screen and select and launch programs just moving on the pad and double hitting the pad . No problems! In a nutshell no need to press the left button. 2) If at boot time I start kde by means of kdm having put in /etc/ttys: ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure and modified /etc/pam.d as required to autologin, I immediatedly and automagically login into kde as a user and the mouse works BUT... with the pad I can only move around the screen and the double-hit doesn't work anymo= re so that I have to use the left button cumpulsorily (and annoyingly). My feeling is that moused is both somewhat slow and one of the last services to be executed. Therefore I highly suspect that the execution of moused in some way overlaps with the execution of autologin kdm at boot time causing the malfunctioning mousepad behaviour. Now I'm trying to delay a bit the execution of kdm by adding something like ttyv8 =A0 "/bin/sleep 2;/usr/local/bin/kdm -nodaemon" =A0xterm =A0 on =A0se= cure ttyv8 =A0 "/bin/sleep 2 && /usr/local/bin/kdm -nodaemon" =A0xterm =A0 on = =A0secure but FreeBSD doesn't seem to like either: it doesn't execute kdm and issue a warning about a delay of 60 seconds?????? =A0 How could I delay a bit the autologin kdm? Ciao Vittorio =2D------------------------------------------------------