From owner-freebsd-questions@FreeBSD.ORG Sun Feb 3 18:36:32 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 46FC2454 for ; Sun, 3 Feb 2013 18:36:32 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id ECD93687 for ; Sun, 3 Feb 2013 18:36:31 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id k10so4966963iea.33 for ; Sun, 03 Feb 2013 10:36:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=o5nlNGWRzWq4VZH4Oeo+FE331mKy8Shp8P0FU5jdeOE=; b=cTuuXQ4PB8LU55kZG8c/KNOrjI0kdEw8z16cKQtFnxFWnDNodNnNezbmQp2FMC+Lg/ fdaLFwuPK702emdD2IdvzXuHjezOzw3042BmHwk9/K4jjzVQZrXtcvqOVIgRJo6uCOg6 depm+VoPOlO24iXDQrIiOHgQmOJZyFtpMZvU5mxkTYwl3xTLUw7+Rf13SypJ4zkvo8AC 2pnI7eSnadz5TLJPMv9FlUOxfD/LGWPSdsDfzZGkofeTes1P3VQa38zlITVejYHv6yYl OZKgOcJwu4ZO4I2uR6BZwvxfXg4aTzMRaxjZlIDgJ8jDLwO3zZStsDgvutXIsmMNmYeh 0RmA== MIME-Version: 1.0 X-Received: by 10.50.140.104 with SMTP id rf8mr3381725igb.21.1359916591629; Sun, 03 Feb 2013 10:36:31 -0800 (PST) Received: by 10.64.5.70 with HTTP; Sun, 3 Feb 2013 10:36:31 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Feb 2013 13:36:31 -0500 Message-ID: Subject: Re: Mouse stopped working on quit fvwm From: "illoai@gmail.com" To: Roger Marsh Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 18:36:32 -0000 On 3 February 2013 04:23, Roger Marsh wrote: > The problem was encountered when upgrading to FreeBSD 9.1-RELEASE and a 18 > January 2013 portsnap. > > Steps were: > > Upgrade to FreeBSD 9.1-RELEASE > pkg_delete -a > rm -r /usr/local/* > Install ports using portmaster > Turn on the ttyv8 xdm and reboot > Login via the xdm dialog using the user .xsession file containing just > /usr/local/bin/fvwm2 > Do whatever and quit from fvwm back to the xdm dialogue > > Usually, but not always, the pointer does not move in response to pointer > device. But it is still possible to login and get the fvwm display back, > but pointless because the pointer still does not move. > > Only recovery option found was reboot. For me the most convenient work > around is turn xdm off and login at a terminal and use the command 'startx > && exit'. > > It was quite a while before it occurred to me that the absence of xorg.conf > from all the usual locations might be the problem. > > It is not a surprise now if X just works without any manual configuration. > > The Xorg -configure and X -config /root/xorg.conf.new dance gives a black > screen on the hardware. > > For both reasons I did not bother with the dance when doing the upgrade. > > After generating and copying xorg.conf.new to /etc/X11/xorg.conf the pointer > was mobile after quitting from fvwm. > > Although it works I did not quite trust the generated xorg.conf because of > the black screen and wondered if any of the information in the file was > needed. So I deleted it and replaced it by 'touch /etc/X11/xorg.conf'. The > pointer is mobile after quitting from fvwm. > > Maybe the problem was my sloppy configuration management in losing, I > assume, an existing xorg.conf file. > > But maybe it is a bug because it is not a surprise if X just works without > any manual configuration and the problem occurs possibly after hours of > successful and varied use of applications via fvwm. > Is your Xorg built with HAL support? You might have to kick HAL. I've not had problems using moused (& Xorg with HAL disabled) & an old-fashioned xorg.conf. -- --