Disablin xinput2 for now?
austinenglish at gmail.com
Thu Jun 23 14:24:21 CDT 2011
On Mon, Jun 20, 2011 at 23:26, Vitaliy Margolen <wine-devel at kievinfo.com> wrote:
> On 06/20/2011 02:31 PM, Austin English wrote:
>> On Mon, Jun 20, 2011 at 09:36, Alexandre Julliard<julliard at winehq.org>
>>> Vitaliy Margolen<wine-devel at kievinfo.com> writes:
>>>> On 06/20/2011 02:55 AM, Marcus Meissner wrote:
>>>>> As this might be a X.org issue, should we packagers turn off
>>>>> xinput2 support for the time being?
>>>> If that will fix all dinput regressions - absolutely. Or add a
>>>> registry option to disable xinput2.
>>> It will of course fix some regressions, and introduce new ones for
>>> things that have been fixed by the changes. Don't tell me that dinput
>>> was working perfectly before. And there is a registry option
>> I just did a quick test with today's git (wine-1.3.22-255-g4c0c0d3)
>> (which has
>> Using Duke Nukem Forever, which has the mouse jumping bug
>> plain wine: I can move normally, with occasional mouse jumps.
>> wine + GrabPointer=N: mouse spins around uncontrollably, a la bug
>> wine configured with --without-xinput2: mouse movement isn't fluid at
>> all. Instead, the only way the cursor will move is jumps in a random
>> direction (like bug 27156, except there is no normal behavior in
>> between the jumps).
> Can you check how well it works with wine-1.3.19 - before all xinput2
> related changes went in?
Mostly better now, wine-1.3.22-361-g0b2bd0c, though DNF is still
More information about the wine-devel