I can confirm this issue also occurs with me. 
The only difference I have from Comment1 is that I am totally unable to click - but this could be because I failed to clink where I should have had.

Again, no crash or anything occurs - it is just the menu that is invisible.


==== System Information ====
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
Video card: nVidia NVS 5200M
Drivers:    304.88 nVidia proprietary drivers
Resolution: 1920x1080
Desktop Env: Gnome3
FPS: 50 - 60 (Steady 50)
WineArch: Win7
Wine 1.7.13 (also present in 1.7.12 and 1.7.11)

Is this still an issue?

If so please attach debug.log

you can do it with "wine game.exe >> debug.log 2>&1", without quates and game.exe being the launcher which starts lol.

So we get forward with this.

Nothing visible in the debug output...
The menu "just" doesn't show - with no error.

I am going to recompile wine and test again soon.
Will provide info if this is there - the effect is there for sure - i.e. the menu is not visible, but the bug...

Same bug here with wine 1.7.18, do you need additional logs ?

There is a workaround for this bug:
Press Right Button
Press Left Button
Release Left Button
Release Right Button

(In reply to a.metaphysical.drama from comment #5)
> There is a workaround for this bug:
> Press Right Button
> Press Left Button
> Release Left Button
> Release Right Button

Very strange but your workaround works for me too !

(In reply to Someone from comment #6)
> (In reply to a.metaphysical.drama from comment #5)
> > There is a workaround for this bug:
> > Press Right Button
> > Press Left Button
> > Release Left Button
> > Release Right Button
> 
> Very strange but your workaround works for me too !

I confirm this, and, fun fact, the official Mac client suffers the same bug.

(In reply to a.metaphysical.drama from comment #5)
> There is a workaround for this bug:
> Press Right Button
> Press Left Button
> Release Left Button
> Release Right Button7

I can also confirm that this workaround works on: 
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 x86_64 GNU/Linux
Debian Wheezy 
Wine 1.7.17
Latest nVidia Drivers

I think we should use some additional debug channels, but I have no idea what...

That workaround sounds really odd. Like playing some computer game puzzle.

This issue could be related to the following bug at my opinion.
http://bugs.winehq.org/show_bug.cgi?id=29871

If this is the case, then reverting the commit (see other bug report for more details) should solve the issue.

Also feel free to test my patch attached there, which unfortunately didn't seem to solve the issue for the original app it was written for:
http://bugs.winehq.org/attachment.cgi?id=49000

(In reply to Sebastian Lackner from comment #10)
> This issue could be related to the following bug at my opinion.
> http://bugs.winehq.org/show_bug.cgi?id=29871
> 
> If this is the case, then reverting the commit (see other bug report for
> more details) should solve the issue.
> 
> Also feel free to test my patch attached there, which unfortunately didn't
> seem to solve the issue for the original app it was written for:
> http://bugs.winehq.org/attachment.cgi?id=49000


The patch didn't solve the issue for me (wine 1.7.23 patched with http://pastebin.com/xSNJjkMY)

Using WINEDEBUG=+cursor I got this information:
"Simple right click" : 
  trace:cursor:X11DRV_ButtonPress hwnd 0x1006c/2200002 button 2 pos 881,170
  trace:cursor:X11DRV_ButtonRelease hwnd 0x10098/220000e button 2 pos 0,0

"Press Right/ Press Left/ Release Left / Release Right manipulation" : 
  trace:cursor:X11DRV_ButtonPress hwnd 0x30096/2200014 button 2 pos 0,0
  trace:cursor:X11DRV_ButtonPress hwnd 0x40096/2200015 button 0 pos 0,0
  trace:cursor:X11DRV_ButtonRelease hwnd 0x1006c/2200002 button 0 pos 887,172
  trace:cursor:X11DRV_ButtonRelease hwnd 0x1006c/2200002 button 2 pos 887,172

Anybody knowledgeable enough to try to fix this ? :)

Did you also apply one of the patches I mentioned? If yes, which one? Your link points to a patch which tries to fix a completely different problem.

Yes, sorry for the confusion, I meant that I applied your patch (http://bugs.winehq.org/attachment.cgi?id=49000) to that version (1.7.23 + the other patch).
Also, I made a mistake, it's

"Simple right click" : 
  trace:cursor:X11DRV_ButtonPress hwnd 0x1006c/2200002 button 2 pos 0,0
  trace:cursor:X11DRV_ButtonRelease hwnd 0x10098/220000e button 2 pos 0,0

"Press Right/ Press Left/ Release Left / Release Right manipulation" : 
  trace:cursor:X11DRV_ButtonPress hwnd 0x30096/2200014 button 2 pos 0,0
  trace:cursor:X11DRV_ButtonPress hwnd 0x40096/2200015 button 0 pos 0,0
  trace:cursor:X11DRV_ButtonRelease hwnd 0x1006c/2200002 button 0 pos 887,172
  trace:cursor:X11DRV_ButtonRelease hwnd 0x1006c/2200002 button 2 pos 887,172

DId you also try this?

> If this is the case, then reverting the commit (see other bug report for
> more details) should solve the issue.

I reverted the commit cb3b7237925a24ba4c5696dd079fdc5d99a48577 on wine 1.7.23 and nothing changed, the bug is still here and the workaround too

Also pressing right click, pressing and releasing a key (e.g. space) and releasing right click" seems to do the trick.

I am not sure if that is related but looking at the walkaround it seems so.
If you right click anywhere in the launcher. It will "freeze". All animations still work, but it stops accepting mouse input until you leftckick in the window. A good example is the masteries window. If you right click to remove a mastery the onHover description will no longer hide, no onHover efects work until left clicked. Same happens if you right click anywhere inside the launcher window.

This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine?

(In reply to Austin English from comment #18)
> This is your friendly reminder that there has been no bug activity for over
> a year. Is this still an issue in current (1.7.51 or newer) wine?

Still an issue.

Bug still happening with wine-1.7.51

yep, wine-1.7.51 - even with the workaround

The bug seems solved with wine-staging 1.9.11

Didn't try with standard wine yet.

Problem is resolved w/ `wine-development` package on Debian Sid:

$ wine-development --version
wine-1.9.17 (Debian 1.9.17-1)

Regular wine package still shows the problem:

$ wine --version
wine-1.8.3 (Debian 1.8.3-3)

I was thinking the patch from bug 33943 would help but it was added after wine-staging 1.9.11. It would help a lot if someone could bisect which patch fixed this bug in staging.