From owner-freebsd-hackers Thu Aug 24 11:29:46 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA01881 for hackers-outgoing; Thu, 24 Aug 1995 11:29:46 -0700 Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id LAA01875 for ; Thu, 24 Aug 1995 11:29:43 -0700 From: Frank Nobis Message-Id: <199508241829.UAA06410@trinity.radio-do.de> Received: by trinity.radio-do.de (8.6.11/TRINITY-1.2.0-a) via EUnet for freebsd.org id UAA06410; Thu, 24 Aug 1995 20:29:36 +0200 Subject: Re: Odd X behaviour To: mnewell@lupine.nsi.nasa.gov (Michael C. Newell) Date: Thu, 24 Aug 1995 20:29:36 +0200 (MET DST) Cc: hackers@freebsd.org In-Reply-To: from "Michael C. Newell" at Aug 24, 95 09:24:02 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1372 Sender: hackers-owner@freebsd.org Precedence: bulk > From: "Michael C. Newell" > > I just upgraded to 2.0.5-Release from 1.1.5.1 on my main home system > ("FBSD"). This system is connected via Ethernet to another system > ("TEST1") running 2.0.5-Stable (as of about 2 weeks ago). The -Stable > system (test1) does not have a keyboard or monitor attached. Before the > upgrade I'd been using FBSD as an X terminal for access to TEST1 with no > problems. > > Since upgrading I'm getting strange behaviour of X applications running > on TEST1 displaying on FBSD. In specific some applications don't respond > to button presses, while others do. For example, the sd utility runs > just fine; I can double click sessions and/or press buttons and all works > well. On the other hand the vmix utility does not respond at all to > pressing any buttons - the buttons do change colour when the mouse > focueses on them, but clicking on the buttons has no effect. The same is > true of vat. > > Has anyone seen this problem? Can anyone give me some hints? > I have seen this some time before, when switched from 1.1 to 2.0.5; Check wether the numlock is active or not. If You have numlock pressed, xterm and many other clients don't respond to mouse events as one would expect. This seems to be a generall X problem. This behaviour is reproducable on Sun workstations too. -fn-