[Bug 34195] New: Starcraft II - doesn't start since patch 2.0.10
http://bugs.winehq.org/show_bug.cgi?id=34195 Bug #: 34195 Summary: Starcraft II - doesn't start since patch 2.0.10 Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: felipe.contreras(a)gmail.com Classification: Unclassified Created attachment 45489 --> http://bugs.winehq.org/attachment.cgi?id=45489 Console output Starcraft II has always worked fine for me, but since the latest patch 2.0.10, it just fails to start. I see up to the login screen, then crashes, and I'm greeted with the Blizzard error report tool. It's either that, or the newest version of wine (1.6), those are the only two things that have changed AFAIK. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #1 from Henri Verbeet <hverbeet(a)gmail.com> 2013-08-02 15:37:55 CDT --- For what it's worth, it still seems to work fine for me, although this isn't an entirely clean WINEPREFIX. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #2 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-03 18:24:52 CDT --- Tried on v1.7, still the same. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #3 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-04 05:38:39 CDT --- I tried on v1.5.31 (plus a couple of bison build fixes), still the same. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #4 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-04 05:41:01 CDT --- Henri Verbeet, can you try with a clean prefix? You don't need to reinstall StarCraft II; you can run the .exe from anywhere. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 Ken Sharp <kennybobs(a)o2.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal --- Comment #5 from Ken Sharp <kennybobs(a)o2.co.uk> 2013-08-04 10:45:24 CDT --- (In reply to comment #4)
You don't need to reinstall StarCraft II; you can run the .exe from anywhere.
That doesn't help at all. You need to install the application correctly for it to work correctly. Definitely NOT major. http://bugs.winehq.org/page.cgi?id=fields.html#severity (In reply to comment #0)
It's either that, or the newest version of wine (1.6)
So try it in a version that worked. If it works then it's a regression. http://wiki.winehq.org/RegressionTesting Please remember to attach bug reports to the AppDB. http://wiki.winehq.org/AppDB#BugLinks -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #6 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-04 11:47:33 CDT --- (In reply to comment #5)
(In reply to comment #4)
You don't need to reinstall StarCraft II; you can run the .exe from anywhere.
That doesn't help at all. You need to install the application correctly for it to work correctly.
It works correctly. It has always worked correctly, both in Linux, and in Windows.
Definitely NOT major. http://bugs.winehq.org/page.cgi?id=fields.html#severity
So what do you call a bug that makes a game totally unusable? More specifically, one of the most popular games of all time.
(In reply to comment #0)
It's either that, or the newest version of wine (1.6)
So try it in a version that worked. If it works then it's a regression. http://wiki.winehq.org/RegressionTesting
As I already said, I already did. It's not a regression, it's triggered by the latest version. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #7 from Henri Verbeet <hverbeet(a)gmail.com> 2013-08-04 12:55:03 CDT --- (In reply to comment #4)
Henri Verbeet, can you try with a clean prefix? You don't need to reinstall StarCraft II; you can run the .exe from anywhere. Yeah, that works as well here.
I don't see anything obvious in the log. Do you get a good backtrace from the game? There should be crash dumps under ~/StarCraft II/GameLogs/, unless you changed the desktop integration link for "My Documents". -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #8 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-04 18:05:56 CDT --- (In reply to comment #7)
(In reply to comment #4)
Henri Verbeet, can you try with a clean prefix? You don't need to reinstall StarCraft II; you can run the .exe from anywhere. Yeah, that works as well here.
I don't see anything obvious in the log. Do you get a good backtrace from the game? There should be crash dumps under ~/StarCraft II/GameLogs/, unless you changed the desktop integration link for "My Documents".
It doesn't seem that way. ---------------------------------------- DbgHelp Stack Trace (ID:75 Stack:0x06200000 + 8,388,608 "Main Thread") ---------------------------------------- DBG-ADDR<27353431>("") (069FB170,7F5F28F4,7F5F2908,7F5F000C) DBG-ADDR<3C968D2A>("Battle.net.dll") (7F5F000C,07685AD4,07685AD4,076280A4) DBG-ADDR<3C9692A0>("Battle.net.dll") (7F5F000C,07685AD4,07629164,076280B0) DBG-ADDR<3C9694C7>("Battle.net.dll") (076280A4,0762808C,007F525C,0F17AA74) DBG-ADDR<3C969627>("Battle.net.dll") (0F17AA74,069FB314,076280A4,0762808C) DBG-ADDR<3C969A23>("Battle.net.dll") (007F5624,007F56DC,0768FB4C,069FB768) DBG-ADDR<3C923F20>("Battle.net.dll") (000001BC,0768FB7C,0768FB94,00000000) DBG-ADDR<3C928F29>("Battle.net.dll") (069FB7E0,007F0250,00000010,02B1DCCB) DBG-ADDR<3C93D203>("Battle.net.dll") (00BA3FC3,02B1DCCB,007F01F4,016758F4) DBG-ADDR<00BA4B6A>("SC2.exe") (02B1DCCB,00000000,00000010,00000000) DBG-ADDR<00B771E0>("SC2.exe") (0000000A,00000BAD,7B810001,00000000) DBG-ADDR<00843F61>("SC2.exe") (00000BAD,008457D5,7B810000,00000000) DBG-ADDR<00844AF6>("SC2.exe") (057FEB84,0033FDB0,7B8B7000,00000004) DBG-ADDR<00845B4F>("SC2.exe") (0022073B,057FEB84,0033FD54,7B8B7000) Anyway, I had the feeling the crash happened when connecting to Battle.net, and the stack trace above seems to agree with that, so I started the game without Internet access and there's no crash. The screen kept flickering to black the whole time, but there was no crash. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #9 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-04 18:50:59 CDT --- (In reply to comment #6)
(In reply to comment #5)
(In reply to comment #4)
You don't need to reinstall StarCraft II; you can run the .exe from anywhere.
That doesn't help at all. You need to install the application correctly for it to work correctly.
It works correctly. It has always worked correctly, both in Linux, and in Windows.
BTW. I tried to run the installer in a clean prefix, and after 6% of the download you can run the game, I click PLAY, and it crashes just the same. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #10 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-04 23:33:34 CDT --- I found the problem; it's the latest Linux kernel; v3.10 works fine, but v3.11-rcX doesn't. I bisected the issue: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f... So I revert that patch and there's no crash. However, there's still the problem that the screen flicks black. It appears to happen each time I move the mouse. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM --- Comment #11 from Austin English <austinenglish(a)gmail.com> 2013-08-05 14:21:00 CDT --- (In reply to comment #10)
I found the problem; it's the latest Linux kernel; v3.10 works fine, but v3.11-rcX doesn't.
I bisected the issue:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f...
So I revert that patch and there's no crash.
However, there's still the problem that the screen flicks black. It appears to happen each time I move the mouse.
UPSTREAM then. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #12 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-05 14:49:50 CDT --- (In reply to comment #10)
However, there's still the problem that the screen flicks black. It appears to happen each time I move the mouse.
See bug #34210. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 Ken Sharp <kennybobs(a)o2.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #13 from Ken Sharp <kennybobs(a)o2.co.uk> 2013-08-08 08:43:09 CDT --- (In reply to comment #6)
Definitely NOT major. http://bugs.winehq.org/page.cgi?id=fields.html#severity
So what do you call a bug that makes a game totally unusable? More specifically, one of the most popular games of all time.
READ THE LINK Fixed upstream. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3... Given how quickly the commit has been reverted, it is unlikely to have any effect in the wild. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #14 from Felipe Contreras <felipe.contreras(a)gmail.com> 2013-08-08 15:26:54 CDT --- (In reply to comment #13)
Fixed upstream. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3...
Given how quickly the commit has been reverted, it is unlikely to have any effect in the wild.
Thanks to me. Reported-by: Felipe Contreras <felipe.contreras(a)gmail.com> -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #15 from Henri Verbeet <hverbeet(a)gmail.com> 2013-08-08 15:29:11 CDT --- (In reply to comment #13)
(In reply to comment #6)
Definitely NOT major. http://bugs.winehq.org/page.cgi?id=fields.html#severity
So what do you call a bug that makes a game totally unusable? More specifically, one of the most popular games of all time.
READ THE LINK
I think that's a bit uncalled for. Arguably the way severity works in Wine's bugzilla is a bit unintuitive for some people because it's intended to be set from Wine's point of view instead of the application's. I think the issue comes up often enough to call it a common mistake, but that's not a reason to be rude about it. Quite the contrary, I'd argue. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34195 --- Comment #16 from Austin English <austinenglish(a)gmail.com> 2013-08-08 16:17:43 CDT --- (In reply to comment #15)
(In reply to comment #13)
(In reply to comment #6)
Definitely NOT major. http://bugs.winehq.org/page.cgi?id=fields.html#severity
So what do you call a bug that makes a game totally unusable? More specifically, one of the most popular games of all time.
READ THE LINK
I think that's a bit uncalled for. Arguably the way severity works in Wine's bugzilla is a bit unintuitive for some people because it's intended to be set from Wine's point of view instead of the application's. I think the issue comes up often enough to call it a common mistake, but that's not a reason to be rude about it. Quite the contrary, I'd argue.
Agreed. Suggestions on how to reduce that mistake are welcome, of course. But no need to reprimand somewhat for what was a valid bug report, albeit in the wrong place (which wasn't immediately obvious). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org