http://bugs.winehq.org/show_bug.cgi?id=31406
Chiitoo escomk3@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |escomk3@hotmail.com
--- Comment #33 from Chiitoo escomk3@hotmail.com 2012-09-10 09:20:30 CDT --- Teegrins~
I was creating a new entry, but as I was getting finished, I noticed the same commit I ended up to with a bisect is mentioned here, so I'll rather add my findings here as well.
Occasionally launching the PlayOnline Viewer (polboot.exe/pol.exe/FINAL FANTASY XI) will result into a black box, with the background music playing. No graphics are rendered, and no sound is produced by moving the mouse around where the options would be (or using the game-pad to go through different options), so no interaction with the application is possible, except for being able to minimize/maximize the application by clicking the Task Manager entry, or from the window icons.
This would sometimes happen when logging out of FINAL FANTASY XI to return to the PlayOnline Viewer as well.
Sometimes there might not be music even, and the application doesn't respond in any way, not even when clicking the Task Manager entry. In any case, there doesn't seem to be any interesting terminal-output, at least not without d3d channel enabled.
Due to the more or less random nature of the issue, I can not be 100% certain that the following is indeed the first bad commit, but I did bisect it two times and I would end up with the same results each time:
8a95eb060449e93bc38af1cabc928f0a959e9e14 is the first bad commit commit 8a95eb060449e93bc38af1cabc928f0a959e9e14 Author: Henri Verbeet hverbeet@codeweavers.com Date: Wed Jul 18 21:32:33 2012 +0200
wined3d: Disable the X11 / GL lock.
:040000 040000 ffc792739741b2aa3999dc533803e600ace0b3fd c37d9d0fe4165e09a89c9e22066e3acc17537bbb M dlls
I wonder if it might be easier to debug with due to the fact that it happens right when launching the application, instead of in-game as it seems to happen for Borderlands. That is, if the real issue is the same in the first place.
Let me know if I should still open a dedicated bug for this, and/or if I should add a back trace or more, though it seems like it might be redundant at this point.
I'll at least add a link to it as it seems related?