Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Feb 2009 21:46:38 +0100
From:      "Paul B. Mahol" <onemda@gmail.com>
To:        Kevin Oberman <oberman@es.net>
Cc:        x11@freebsd.org
Subject:   Re: New xorg and fvwm2 have mouse issues
Message-ID:  <3a142e750902241246m2f73099n6bd32e193f33775@mail.gmail.com>
In-Reply-To: <20090222214926.54C281CC0B@ptavv.es.net>
References:  <20090222214926.54C281CC0B@ptavv.es.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2/22/09, Kevin Oberman <oberman@es.net> wrote:
> This may be similar to other reported problems with mouse HAL, and Xorg
> inter-operation, but it seems different enough that I thought I'd report
> it in hopes that someone else has seen it.
>
> The problem occurs when doing a cut and paste. The selection works fine,
> but, when the mouse is moved to a new window to paste, the mouse locks
> up. If the process owning the cut window is killed, the mouse returns to
> normal operation.
>
> I have only seen this a co-worker's system. It is running DBUS, HAL, and
> has "AllowEmptyInput" "off". The only thing different from other systems
> is that it is not running metacity and Gnome. It is running fvwm2. It
> appears that something fvwm2 does with X in the cut and paste operation
> is hanging.
>
> Any ideas of what to look at and how to approach debugging it. It amy be
> that the problem is in fvwm2. I know that Tk required an update to work
> properly with the new Xorg.

It is highly unlikely to be fvwm2 problem. Did you tested with other wm?
Does it happen with any application?

-- 
Paul



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750902241246m2f73099n6bd32e193f33775>