Date: Wed, 16 May 2012 05:24:24 -0500 From: ajtiM <lumiwa@gmail.com> To: freebsd-x11@freebsd.org Subject: Re: Odd mouse issue with new xorg-server Message-ID: <201205160524.24623.lumiwa@gmail.com> In-Reply-To: <CAFHbX1LGaoWiWa0q-kJmvQhf_pLNspACcM1y3GPTRVZjs=8LOw@mail.gmail.com> References: <CAN6yY1sGJV4sbjbJZ_qwhwhmGewnb_AuAKkDCwCvTJAAU1vPHw@mail.gmail.com> <CAN6yY1s=OEU9%2BUvys4K2AJN2dwxXNz_ztBnVPyLsDonARSd2kg@mail.gmail.com> <CAFHbX1LGaoWiWa0q-kJmvQhf_pLNspACcM1y3GPTRVZjs=8LOw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 16 May 2012 03:35:14 Tom Evans wrote: > On Wed, May 16, 2012 at 12:51 AM, Kevin Oberman <kob6558@gmail.com> wrote: > > On Tue, May 15, 2012 at 11:57 AM, Tom Evans <tevans.uk@googlemail.com> wrote: > >> On Thu, Apr 26, 2012 at 3:30 AM, Kevin Oberman <rkoberman@gmail.com> wrote: > >>> I hit a weird one with the new xorg-server. I have previously been > >>> running the xorg-devel from about 4or 5 months ago, so it's something > >>> that has happened since then. > >> > >> This is just a 'me too'. In my case, it seems like restarting hald > >> allows X to start up and find the mouse. Full details and logs in the > >> "Strange keyboard/hald issues after upgrading to 9-STABLE and latest > >> ports" thread. > >> > >> I see the current solutions suggest to disable hald, either by > >> completely disabling it from X, or by "AutoAddDevices off". In my > >> case, these are not solutions, as I rely on hald noticing when new > >> keyboards and mice are added to the computer and making them available > >> to X - I often dock and undock my laptop, the dock has two keyboards > >> and two mice attached to it. > >> > >> I also don't fully understand what the problem is either. Earlier > >> versions of hald/Xorg were capable of finding my mouse every single > >> time they started up. These new versions do not seem fit for use. > > > > Out of curiosity, does the mouse show up in lshal(1) output before you > > restart hald? Is there a difference after the restart? > > I can check that, but I think restarting hald is not relevant. My > current approach, which seems to be working nicely, is to boot with > gdm disabled, and restart it 3 times. This gets me a working X with a > working hal 90% of the time. > > Hence I think that my idea that hald was behind this seems wrong, as > I'm now not restarting hald. > > I've had enough of fiddling with this right now (I need to do some > work!), but tonight I will make the gdm rc.d script record a copy of > lshal output when it starts up, perhaps there is a time delay in hald > presenting the right devices. > > Cheers > > Tom > _______________________________________________ > freebsd-x11@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" I have the same problem all the time after update (never had before) and I never restart hald but on the second try of 'startx" it works. BTW I use KDE and it is anoying. Mitja -------- http://jpgmag.com/people/lumiwa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201205160524.24623.lumiwa>