http://bugs.winehq.org/show_bug.cgi?id=32014
Bug #: 32014 Summary: Borderlands 2 starts with black screen Product: Wine Version: 1.5.15 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: spamzooi1@gmail.com Classification: Unclassified
Created attachment 42196 --> http://bugs.winehq.org/attachment.cgi?id=42196 Output when running Borderlands2.exe
Overview:
Borderlands 2 cannot be started due to unknown graphics issues.
Steps to reproduce:
1. Create 32-bit wineprefix on 64-bit OS. (Optional: Set VideoMemorySize to actual value) 2. Install and update Steam (with winetricks) 3. Create "./drive_c/Program Files/Steam/SteamApps/common/Borderlands 2/Binaries/Win32/steam_appid.txt" with content: 49520 4. Run: wine start /unix ./drive_c/Program\ Files/Steam/SteamApps/common/Borderlands\ 2/Binaries/Win32/Borderlands2.exe
Actual Results:
The game runs (I can hear the intro sounds), but the screen is black. After the intro movies the sounds stops and the window becomes transparent. Other windows on the background cannot be clicked because Borderlands 2 still has focus.
Expected Results:
Visible intro movies and a playable game.
Build date & Platform:
wine-1.5.15 on Gentoo Linux x64 Intel i7-3700k, 16GB RAM, Nvidia GeForce GTX680 Nvidia proprietary drivers, version 310.14
Additional information:
See attached log.
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #1 from BitMaster spamzooi1@gmail.com 2012-10-19 19:44:03 CDT --- Of course, Step 2a should be install Borderlands. The steam installer already includes vcrun2008, vcrun2010 and d3dx9.
http://bugs.winehq.org/show_bug.cgi?id=32014
BitMaster spamzooi1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spamzooi1@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32014
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #2 from Jerome Leclanche adys.wh@gmail.com 2012-10-20 05:06:26 CDT --- Works fine here on a gtx 580 and nvidia 304.51-4.
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #3 from BitMaster spamzooi1@gmail.com 2012-10-20 05:33:57 CDT --- Jerome, which wine version do you use and did you do anything special to get it running?
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #4 from Jerome Leclanche adys.wh@gmail.com 2012-10-20 05:38:34 CDT --- wine-1.5.15-204-g673617e. Nothing special, just what was mentioned on the appdb (skipping the launcher). I do have a lot of crap installed on that prefix though, I'll try on a clean one at some point.
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #5 from BitMaster spamzooi1@gmail.com 2012-10-20 05:47:00 CDT --- Created attachment 42199 --> http://bugs.winehq.org/attachment.cgi?id=42199 Memory dump generated by Borderlands2 itself
I've just noticed Borderlands2 generates a mdmp file upon crash. Maybe this will add some useful input.
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #6 from Jerome Leclanche adys.wh@gmail.com 2012-10-20 05:48:40 CDT --- This is the backtrace from it, mostly empty:
... 17 0x7bc7795e in ntdll (+0x6795d) (0x0233ffc8) 18 0x7bc4e1ce in ntdll (+0x3e1cd) (0x0233ffe8) 19 0xf75df0dd strspnW+0x1c(str=0x0(nil), accept=0x0(nil)) [/home/adys/src/wine/build32/libs/wine/../../../include/wine/unicode.h:255] in libwine.so.1 (0x00000000)
Could you install debug symbols? (wine-dbg on ubuntu)
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #7 from Jerome Leclanche adys.wh@gmail.com 2012-10-20 05:49:34 CDT --- Sorry, you're on gentoo; just recompile without stripping them.
http://bugs.winehq.org/show_bug.cgi?id=32014
BitMaster spamzooi1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #42199|0 |1 is obsolete| |
--- Comment #8 from BitMaster spamzooi1@gmail.com 2012-10-20 07:25:00 CDT --- Created attachment 42201 --> http://bugs.winehq.org/attachment.cgi?id=42201 Memory dump generated by BL2 with wine debug symbols
This one should be with wine debug symbols. I'm actually not sure in which case this dump is generated. Is there any proper guide on how to debug this?
I tried WINEDEBUG=+relay and it generates a HUGE log with on the end only calls about critical sections and sleeps. Does this mean some kind of deadlock?
Also, the result is not everytime the same when running Borderlands2.exe. Sometimes Steam complaints about currently not being able to handle the request and sometimes the game stops/crashes in the middle of the intro videos (indentifyable by the interruption of the audio). Furthermore, if I adjust the resolution to the resolution BL2 uses, there is no black screen at all. I can't really recognize a pattern.
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #9 from Rico kgbricola@web.de 2012-10-21 09:47:39 CDT --- Is this a regression? Does it work with wine 1.5.9? Does it work with older nvidia drivers?
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #10 from BitMaster spamzooi1@gmail.com 2012-10-24 16:50:14 CDT --- You're right! It DOES work with wine 1.5.9!! I didn't change anything else, it just worked as soon as i downgraded to 1.5.9. Still using the latest nvidia drivers.
How do i find out why it doesn't run with the latest wine?
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #11 from Austin English austinenglish@gmail.com 2012-10-24 18:51:13 CDT --- (In reply to comment #10)
You're right! It DOES work with wine 1.5.9!! I didn't change anything else, it just worked as soon as i downgraded to 1.5.9. Still using the latest nvidia drivers.
How do i find out why it doesn't run with the latest wine?
By running a regression test :) http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=32014
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=32014
--- Comment #12 from Rico kgbricola@web.de 2012-10-25 02:03:05 CDT --- It may be related to bug 31882 (or bug 31406). Gentoo ships an really old version of libxcb (the one wine needs is in emul-linux-x86-xlibs). You may try if one of the commits from the other bug reports broke it for you.
http://bugs.winehq.org/show_bug.cgi?id=32014
BitMaster spamzooi1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #13 from BitMaster spamzooi1@gmail.com 2012-10-26 17:31:39 CDT --- Rico, you are right again. This is a duplicate of bug #31406 and I have confirmed it by reverse applying this patch: http://www.winehq.org/pipermail/wine-patches/2012-July/116361.html.
After confirmation i have worked around it by following up the instructions in this topic: http://forum.winehq.org/viewtopic.php?f=2&t=17203#p80890
Am i missing something about a permanent fix for this or do i just have to wait until xcb supports python 3 and gentoo releases it in portage? Judging from the amount of chatter about this bug i presume the necessary triggers are already set off at xcb and gentoo?
*** This bug has been marked as a duplicate of bug 31406 ***
http://bugs.winehq.org/show_bug.cgi?id=32014
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Austin English austinenglish@gmail.com 2012-10-31 14:53:23 CDT --- Closing.
-
wine-bugs＠winehq.org