[Bug 12962] New: Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

Summary: Diablo 2: left-control ignored after mouse click
           Product: Wine
           Version: 0.9.61.
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

While playing Diablo 2 (Ubuntu Hardy + Compiz):
- Hold down mouse button to walk in a direction
- Hold down left-control to start running
- Release mouse button, and re-press
* The character should continue running toward the pointer, but instead returns
to walking until/unless left-control is re-pressed.
The game behaves as expected if the right-control key is used instead.

I suspect this regression is related to the now resolved bug #12343, but this
specific behaviour is still exhibited in 0.9.61.

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

--- Comment #1 from Mel   2008-05-10 04:28:49 ---
As an addendum, I don't have this problem with KDE 3.5.9 + Compiz, only when I
use Gnome + Compiz.
Ctrl is not used for moving windows with the mouse in the Gnome settings, nor
does it occur with button1 in any Compiz config.

The problem is still present in 1.0-rc1

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

--- Comment #2 from Vitaliy Margolen   2008-05-11 13:45:52 ---
Do you have any mouse emulators running? Or some other input altering programs?
If it works with one config and not with another the X-server is still the
same. And this is where Wine gets it's mouse & keyboard events from.

Also do you have that problem without compiz all together?

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

--- Comment #3 from Mel   2008-05-11 15:55:54 ---
(In reply to comment #2)
> Do you have any mouse emulators running? Or some other input altering programs?

I use an input remapper (Pystromo) with Diablo 2, but turning it off was one
of the first things that I checked before I filed the report. It doesn't appear
to make any difference to the behaviour whether it is running or not.
 Other than that, there is nothing affecting input that I know of - it was a
fresh Ubuntu Hardy install.
> If it works with one config and not with another the X-server is still the
> same. And this is where Wine gets it's mouse & keyboard events from.
>
> Also do you have that problem without compiz all together?

Without compiz it works as it should. Indeed, switching compiz on and off
while Diablo 2 is running will also trigger the erroneous behaviour on and off.
 I've just tried Urban Terror (native client), and the ctrl+click behaviour is
as it should be, with or without compiz running.

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

--- Comment #4 from Vitaliy Margolen   2008-05-12 08:57:49 ---
This means it's acompiz bug and not Wine's. You should probably file bug there.
If it messing with mouse & keyboard input in anyway it will for sure break
Wine. The input is really picky about lots of things.

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

--- Comment #5 from Mel   2008-05-16 07:55:00 ---
I thought it might be a bug in Compiz, which is why I tested the ctrl-click
behaviour in a game which *didn't* use wine.
The fact that compiz affects wine's input-handling behaviour does indeed point
to a bug in compiz. However the fact that compiz *doesn't* affect non-wine
games points to a bug in wine. Wine should surely handle receiving input just
as any other linux application does, no?

I've just tested the Dungeon Siege 2 demo, and it has the same ctrl-click
problem (just so I know it's not only the one game).

Posted a message in the compiz-fusion forums (basically replicating this bug
report so far). Maybe someone there can shine some light:
http://forum.compiz-fusion.org/showthread.php?t=8365

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]        |

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

haarp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

Sven Dack  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from Sven Dack   2009-07-02 10:00:48 ---
I can confirm the problem, but AFAIK is this not a bug. GNOME uses CTRL+"Left
Mouse" for dragging windows. Try reassigning the short cut with the tool
'gnome-keybinding-properties'.

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

--- Comment #7 from Mel   2009-08-14 04:26:15 ---
After experiencing the same thing with EVE Online (thus being unable to target
objects with the left control + click), I noticed that using my caps-lock key
instead worked just fine - I have caps-lock mapped as "an additional control".
Indeed, turning this caps-lock remap off causes the normal left-control to work
as expected.

Using xev I see that when caps-lock is so mapped, both it and left control
output the same keysym (0xffe3, Control_L). Perhaps there is something within
either wine or compiz which expects a keysym to only be associated with a
single keycode...?

And Sven; no, you're thinking of Alt+Click, which is one of the first things I
change on any new set up.

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

--- Comment #8 from Austin English   2010-04-30 17:11:20 ---
This is your friendly reminder  that there has been no bug activity for 6
months. Is this still an issue in current (1.1.43 or newer) wine?

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

Xavier Vachon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Xavier Vachon   2010-07-19 18:35:38 ---
(In reply to comment #8)
> This is your friendly reminder  that there has been no bug activity for 6
> months. Is this still an issue in current (1.1.43 or newer) wine?

In current git (1.2), I do not experience this issue. Can Mel test again and
confirm?

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[e-mail]
         Resolution|                            |FIXED

--- Comment #10 from Anastasius Focht  2012-04-07 12:44:18 CDT ---
Hello,

--- quote ---
In current git (1.2), I do not experience this issue. Can Mel test again and
confirm?
--- quote ---

Original reporter didn't respond for long time, marking fixed as per comment #9

Regards

[Bug 12962] Diablo 2: left-control ignored after mouse click

http://bugs.winehq.org/show_bug.cgi?id=12962

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #11 from Alexandre Julliard  2012-04-13 13:29:12 CDT ---
Closing bugs fixed in 1.5.2.