From owner-freebsd-questions@FreeBSD.ORG Sat Jun 9 04:16:09 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 24CE4106564A for ; Sat, 9 Jun 2012 04:16:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id D65928FC0C for ; Sat, 9 Jun 2012 04:16:08 +0000 (UTC) Received: from r56.edvax.de (port-92-195-32-177.dynamic.qsc.de [92.195.32.177]) by mx02.qsc.de (Postfix) with ESMTP id 9C70A27834; Sat, 9 Jun 2012 06:16:00 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id q594G0Qs004179; Sat, 9 Jun 2012 06:16:00 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 9 Jun 2012 06:16:00 +0200 From: Polytropon To: Bernt Hansson Message-Id: <20120609061600.55d6d972.freebsd@edvax.de> In-Reply-To: <4FD2CBD9.8080001@bananmonarki.se> References: <201205181149.q4IBndvU028665@hera.homer.att.com> <4FB64022.6010206@bananmonarki.se> <4FBB4B8C.3000806@bananmonarki.se> <20120522104441.f05a2f88.freebsd@edvax.de> <4FD2CBD9.8080001@bananmonarki.se> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Mouse stopped working in X X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 04:16:09 -0000 On Sat, 09 Jun 2012 06:06:49 +0200, Bernt Hansson wrote: > > > 2012-05-22 10:44, Polytropon skrev: > > On Tue, 22 May 2012 10:17:16 +0200, Bernt Hansson wrote: > >> There is a second way of doing this stunt. > >> > >> Start X > >> When X is up and running press CTRL+ALT+F3 or any F* frpm F3 up to F8 > >> then you get to the console > >> Su to root in the console and type in > >> > >> /usr/local/etc/rc.d/dbus restart&& /usr/local/etc/rc.d/hald restart > >> > >> Then press ALT+F9 to get back to X > > > > So if that is the _solution_ > > It is not near any solution. > > I do not think this issue have anything to do with hal or dbus. I didn't claim it was a solution, I just wanted to make the therapy "more elegant"; see the difference between therapy (treating symptoms) and the actual cure of a disease (removing the cause). As I'm only running old-fashioned stuff here, I can't be more specific regarding the newest inventions of why X stopped acting as expected. In the past, simply removing HAL and DBUS altogether and using a xorg.conf file to make the required settings has worked at least for me. My idea of automating the manual step of restarting HAL and DBUS (which _seems_ to have treated the symptoms of a non-working mouse) was to put that into the X initialisation file: "sudo /usr/local/etc/rc.d/dbus restart && sudo /usr/local/etc/rc.d/hald restart". Of couse that doesn't even remotely touch a possible problem caused elsewhere. And does it look totally stupid? Sure it does. It looks so wrong, but sometimes the wrongest thing "just works" (TM). :-) > My machine at the office running the same hal and X as the one at home > does not have this kind of problems. That might be a good indicator that there actually is something different in those machines, and this difference causes the problem. Maybe it's something simple, and really not related to HAL. As I said, I'm not sure, as I'm not using it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...