Weird fullscreen behavior with 0.9.57 and 0.9.58

[Syylk]

Hi all,

Since two WINE versions, I'm experiencing the same behavior reported in http://bugs.winehq.org/show_bug.cgi?id=10755 but related to two other fullscreen'ed programs:

• EVE Online v.4.10.51200 Premium
• World of Warcraft 2.3.3 w/Burning Crusade

Before starting a regression (I'm ready to do that but my machine isn't the fastest kid in town, so I want to be sure it's a needed task), or even post a bug report/comment on the above one, is this "new" behavior planned, wanted, expected or otherwise intended? Let me resume what happens:

• Upto WINE 0.9.56: in the two fullscreen applications I use, if I alt-tab out of them, the next window in the X11 window list is raised on top of the fullscreen'ed WINE app, receives focus, accepts HMI events, and I can interact with it. I can return to my fullscreen game with another alt-tab. Or I can browse other windows in the list, by keeping the alt key pressed and tapping the tab key multiple times.
  That's how both programs behave natively on the Windows machine next to my linux rig. That's how X11 generic fullscreen apps behave. That's how I'd expect WINE to work.
• From WINE 0.9.57 to 0.9.58 (current, AFAIK): if I press alt-tab and keep the alt key pressed from within one of the games, the WM shows me the window list, with the next window in list highlighted and ready to be raised. When I release the alt key, the selected window will briefly appear on top of the fullscreen'ed game, only to be immediately covered again by the fullscreen WINE app. The fullscreen WINE app retains the focus, and all X11 input goes to WINE.
  I could, however, try to "force the appearance" of the covered window by pointing at the window list while I keep alt-tab pressed. If I manage this weird keyboard/mouse combo, the sunken window stays on top till I release alt-tab; if I click on the raised window title bar, AT TIMES (but not always!) I can make the window stay on top, but at the same time the fullscreen app will minimize itself!
  Sometimes, trying to pull this trick, the X11 interface freezes completely (as if nothing had the focus anymore!) and I must VT-switch and kill the WINE app to regain control of the X server.

The rest of relevant info about my system:

• Athlon XP 2500+, 2GB RAM, linux kernel 2.6.24.4
• nvidia GeForce 6600GT, binary drivers 169.12
• Xorg 1.4.0.90, WindowMaker 0.92.0

Is there a known workaround to restore the old behavior? Or this seems like a bug with WINE I should further investigate and report in the appropriate place (bugzilla/appDB)?

Thank you all in advance.

[vitamin]

Is there a known workaround to restore the old behavior? Or this seems like a bug with WINE I should further investigate and report in the appropriate place (bugzilla/appDB)?

Could you try wine-0.9.59? There were few fixes/changes related to the fullscreen applications.

[Syylk]

Around one hour after I posted my message, I saw 0.9.59 being announced.

For sure I will try it, and post any relevant news about the issue.

[Syylk]

Got and recompiled 0.9.59 from the official Gentoo unstable arch repository.

No luck, unfortunately. The described behavior is still there. And I must add that it's very annoying. I'm basically stuck with a "single tasking" machine as long as I use a fullscreen WINE'd game.

Thanks in advance for help/suggestions/flames.

[vitamin]

Got and recompiled 0.9.59 from the official Gentoo unstable arch repository.

No luck, unfortunately. The described behavior is still there. And I must add that it's very annoying. I'm basically stuck with a "single tasking" machine as long as I use a fullscreen WINE'd game.

Thanks in advance for help/suggestions/flames.

Please open a new bug in bugzilla and perform regression testing. This is a new bug because it worked before. And the quoted bug is for much older version.
If you don't point to the commit that caused the problem - this bug most likely won't be fixed.

[Syylk]

Roger, boss.

I feared your answer, but it was the reason for this thread - whether I should start a regression and then a complete bug report, or if it was just my imagination playing tricks.

Going to work on it, then.

Thanks for everything.

[vitamin]

Roger, boss.

I feared your answer, but it was the reason for this thread - whether I should start a regression and then a complete bug report, or if it was just my imagination playing tricks.

Going to work on it, then.

Thanks for everything.

I'm sorry if I sounded negative. If you started having this problem in the last release or two (as you said yourself) this is something needs to be fixed ASAP before the code freeze (in less then a month).

However only you have reported this problem so far. And the next best thing you can do (after fixing the problem yourself <g>) is to find the change that caused the problem for you. So developer who made that change can fix it while the memory is still fresh.

If we wait for few more releases for more people to confirm the problem it would be too late and this issue might be present in wine-1.0.0

[Syylk]

*Sigh*

Had no time to perform a full regression yet (new daytime job, you know).

But I can confirm that the "broken" behavior (for any definition of "broken") is still present in 0.9.60.

I start suspecting that the problem may be related to WindowMaker - the minimalistic window manager I love and use and that is mostly abandonware in these days of Gnome/KDE *cough*andtheirbloat*cough*.

I should be able to install wine + EVE + WOW on an ubuntu 7.10 soon, and see how it behaves with a mainstream window manager.

Will keep you informed about my tests.

[roderick]

I am running Dungeon Siege, and have experienced similar on all of 0.9.57 - 0.9.60.

Earlier versions did allow ALT-TAB to work flawlessly (at least from the testing I had performed).

Now if I ALT-TAB I cannot get focus consistantly and have experienced locks.

[Syylk]

I'm bisecting like no tomorrow, and confirm that 0.9.56-212 shows no problem in this regard, while 0.9.56-105 does.

Slowly narrowing down to the culprit change... Please be patient. Today I bought a spanking new Phenom 9500 to overcome the abysmal speed of my 5 years old system.

[Syylk]

Ok, I finished to bisect. Found the change, and opened a bugzilla entry.

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

Stefan, have fun!