From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 27 13:03:25 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0AC716A420; Mon, 27 Mar 2006 13:03:25 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1791543D5A; Mon, 27 Mar 2006 13:03:24 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms075.mailsrvcs.net ([192.168.1.4]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IWS006C4EXNACT2@vms046.mailsrvcs.net>; Mon, 27 Mar 2006 07:03:23 -0600 (CST) Date: Mon, 27 Mar 2006 07:03:23 -0600 (CST) From: Sergey Babkin To: Greg 'groggy' Lehey , "Rick C. Petty" Message-id: <19770339.131791143464603498.JavaMail.root@vms075.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Wed, 05 Apr 2006 12:22:00 +0000 Cc: FreeBSD Hackers Subject: Re: Re: Programs not accepting input? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 13:03:25 -0000 >Same here. As mentioned in the original message, I can use the mouse >to open a new window under firefox. The new window will accept >keyboard input, the old one won't. It's almost as if it's deadlocking >on input. > >Reminder: my final question was "how do I go about debugging this >problem?". Does it happen with any kind of programs? If yes, can you reproduce it with "xev"? If yes, it would probably be something focus-related (and you'd be able to see that the Focus event is not coming in). The focus management and the highlighting of the window manager decoration are not physically connected in any way, so a bug in the window manager might cause it to do the highlighting but forget to give the focus to the application. To debug that you can add debugging printout to the WM. Or I've had a script that sort of decoded the X protocol, so if you can get the dump of these (maybe with ktrace), you can decode the dump and see what happens with the focus. I'll look for it in my archives. If no, it might be something with the keyboard event translation to keysyms/text. You can debug this by writing a test program that would do it own dispatch loop - i.e. call XEvent() and then XtDispatchEvent() (or some close names - I might not remember them right), and print the debugging messages. So if you see that XEvent() is getting events but then nothing comes out of dispatching them, then the translation is broken somewhere. I might be able to find this kind of a program in my archives too, I'll look around. BTW, one place where the keyboard events might disappear is the Input Method handling code. But I don't think that you run any Input Methods. -SB