January 2018 - Wine-Bugs - list.winehq.org

[Bug 44371] New: Rising Kingdoms crashes on launch

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44371 Bug ID: 44371 Summary: Rising Kingdoms crashes on launch Product: Wine Version: 3.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isiraseneviratne(a)yahoo.com Distribution: --- Created attachment 60276 --> https://bugs.winehq.org/attachment.cgi?id=60276 The crash log. Running Rising Kingdoms results in the game menu displaying briefly before the game crashes, with the backtrace produced attached below. This occurs whether the game is run in a 64-bit or 32-bit wineprefix. -- 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.

Jan. 19, 2018

[Bug 44365] armel build fails: selected processor does not support `strd r4,[sp]' in ARM mode

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44365 --- Comment #2 from Jens Reyer <jre.winesim(a)gmail.com> --- Confirmed, with this commit it just built successfully on Debian armel. I'm not surprised, but really impressed by this quick fix in time for 3.0. Thanks. -- 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.

Jan. 18, 2018

[Bug 44370] World of Warcraft crashes with "Game initialization failed"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44370 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal -- 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.

Jan. 18, 2018

[Bug 44370] New: World of Warcraft crashes with " Game initialization failed"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44370 Bug ID: 44370 Summary: World of Warcraft crashes with "Game initialization failed" Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cybermax(a)dexter.no Distribution: --- World of warcraft 7.3.5 crashes with "Game initialization failed!" when using wine-3.0. -- 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.

Jan. 18, 2018

[Bug 29228] Airline Tycoon Evolution doesn't display any text in-game

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=29228 elicoten(a)live.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |elicoten(a)live.co.uk --- Comment #22 from elicoten(a)live.co.uk --- I also experienced this but in addition I found that at 32bpp Airline Tycoon wouldn't even start without the "emulate virtual desktop" option - I kept getting page faults. Emulate virtual desktop made the game run but as per the bug with missing texts, etc. The xinit command given here didn't work for me, it just hung with a black screen and I had to press CTRL + ALT + F2 to get back to my desktop. I managed to get it working properly using Xephyr to set 16-bit colour depth and then the texts showed correctly. This is on Ubuntu 17.10 with Wine 2.0.4. -- 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.

Jan. 18, 2018

[Bug 42000] Battle.net: invisible window elements with Win7+ mode

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42000 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaahaaap(a)gmail.com --- Comment #21 from Matteo Bruni <matteo.mystral(a)gmail.com> --- *** Bug 43901 has been marked as a duplicate of this bug. *** -- 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.

Jan. 18, 2018

[Bug 43901] battle.net login screen broken UI elements

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43901 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Matteo Bruni <matteo.mystral(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #3) > I think the issue is with CEF not working in win7 mode and not saving a > cookie. It does save the cookie in XP mode though, and its expiration time > is a few hours so it's still valid when restarting in win7 mode. I think this was pretty much spot on. Also fixed by the same staging patchset as bug 42000. *** This bug has been marked as a duplicate of bug 42000 *** -- 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.

Jan. 18, 2018

[Bug 42000] Battle.net: invisible window elements with Win7+ mode

by wine-bugs＠winehq.org

Jan. 18, 2018

[Bug 20456] Multiple installers: some serial numbers/CD-keys don' t fit into edit fields (FEAR, AoE 3, Supreme Commander)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=20456 alexandre.rozier(a)lilo.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexandre.rozier(a)lilo.org --- Comment #44 from alexandre.rozier(a)lilo.org --- Hi, This problem appears when one has not installed the correct windows fonts. By installing with winetricks the "all fonts" package, this problem goes away and one can enter 5 chars into each field. Took me a little bit to troubleshoot, now everything works ! -- 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.

Jan. 18, 2018

[Bug 44369] cmd's %0 path variables (e.g. %~dp0) wrong inside subroutine call

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44369 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |testcase Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Confirming issue. > FWIW: Wine CMD doesn't have the same %~dp0 bugginess as Windows CMD that > motivated the GitHub issue I linked to. Wine handles all of the example > command lines on that GitHub comment consistently (aside from case > differences in the drive letter or the filename extension). If Wine tries to > match Windows bug-for-bug, then maybe this too should change. Yeah, I guess that should change, too. Mind creating a bug report for that one, too? Including a small sample would be awesome. -- 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.

Jan. 18, 2018