May 2017 - Wine-Bugs - list.winehq.org

[Bug 42845] Hearthstone crashes at loading screen

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42845 --- Comment #22 from winetest(a)luukku.com --- Those of you who are able to play this game, could you comment on bug 37111? More activity on bugs means that we can solve them faster. -- 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.

May 16, 2017

[Bug 43037] New: Drops the game's Wow/WoT

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43037 Bug ID: 43037 Summary: Drops the game's Wow/WoT Product: Wine Version: 2.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: connaissant(a)mail.ru Distribution: --- Created attachment 58192 --> https://bugs.winehq.org/attachment.cgi?id=58192 After entering the game world Hello everyone, guys. I have: Wine-2.6 3.0 Mesa 17.2.0-devel Gallium 0.4 on AMD ARUBA (DRM 2.43.0 / 4.4.0-75-generic, LLVM 4.0.1) 00: 01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD / ATI] Trinity [Radeon HD 7640G] Sorry, the problem is that when you enter the game you can see the lines and you can not play. The problem with wine or with a video driver? Any ideas how to solve the problem? The screenshot shows the lines (If you can call it a line) The screenshot is made in Wow. In WoT the same thing Any ideas? -- 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.

May 16, 2017

[Bug 42806] I got this core dump playing hearthstone

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42806 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx(a)gmail.com, | |austinenglish(a)gmail.com, | |dimesio(a)earthlink.net, | |xerox_xerox2000(a)yahoo.co.uk --- Comment #5 from winetest(a)luukku.com --- (In reply to Gijs Vermeulen from comment #4) > (In reply to Gijs Vermeulen from comment #3) > > (In reply to sylvain.meunier from comment #2) > > > I can't reproduce this bug anymore. I updated ubuntu, wine and the nvidia > > > driver since... Next time I open a bug. I will provide the console log. > > > > Can you mark this > > *Can you mark this fixed? I would solve this as worksfome since it's not clear what fixed it. But definitely this bug needs to be closed if it's not reproducible anymore. -- 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.

May 16, 2017

[Bug 42985] Rise of the Tomb Raider needs unimplemented function USER32.dll.GetPhysicalCursorPos

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42985 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- (In reply to Fincer from comment #3) > The game launches with commit 133835 ([PATCH] user32: add > GetPhysicalCursorPos/SetPhysicalCursorPos stubs (try 2)) > > but get's stuck immediately. The main window is invisible and stays like > that until it's killed. Terminal output is printing one single message > (truly, nothing else): > > ... > fixme:win:GetPhysicalCursorPos (0x6f2e2c0) semi-stub: forwarding to > GetCursorPos > fixme:win:GetPhysicalCursorPos (0x6f2e2c0) semi-stub: forwarding to > GetCursorPos > fixme:win:GetPhysicalCursorPos (0x6f2e2c0) semi-stub: forwarding to > GetCursorPos > ... > > Size of the output log file was several gigabytes until I decided to kill > ROTTR.exe process after several minutes of waiting. > > Commit link: > > https://source.winehq.org/patches/data/133835 > > Wine Staging Git 2.8, compiled from source. A cut/paste error causes and infinite loop. Try https://source.winehq.org/patches/data/133879 instead -- 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.

May 16, 2017

[Bug 42985] Rise of the Tomb Raider needs unimplemented function USER32.dll.GetPhysicalCursorPos

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42985 --- Comment #3 from Fincer <fincer89(a)hotmail.com> --- The game launches with commit 133835 ([PATCH] user32: add GetPhysicalCursorPos/SetPhysicalCursorPos stubs (try 2)) but get's stuck immediately. The main window is invisible and stays like that until it's killed. Terminal output is printing one single message (truly, nothing else): ... fixme:win:GetPhysicalCursorPos (0x6f2e2c0) semi-stub: forwarding to GetCursorPos fixme:win:GetPhysicalCursorPos (0x6f2e2c0) semi-stub: forwarding to GetCursorPos fixme:win:GetPhysicalCursorPos (0x6f2e2c0) semi-stub: forwarding to GetCursorPos ... Size of the output log file was several gigabytes until I decided to kill ROTTR.exe process after several minutes of waiting. Commit link: https://source.winehq.org/patches/data/133835 Wine Staging Git 2.8, compiled from source. -- 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.

May 16, 2017

[Bug 42673] Battle.net no longer runs after Wow Legion update

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42673 Grigorii <connaissant(a)mail.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #11 from Grigorii <connaissant(a)mail.ru> --- The problem was solved, I do not know how. Renewed the fault, I guess. Thank you But now another problem, not related to wine -- 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.

May 16, 2017

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

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42000 --- Comment #10 from winetest(a)luukku.com --- (In reply to winetest from comment #9) > (In reply to wow_on_wine from comment #8) > > Created attachment 57503 [details] > > acceleration disabled > > I get exactly this looking battle.net with wine-staging 2.8 all defaults. winetricks -q ie8 is a workaround for this bug. with 32bit prefix, ie8 installed via winetricks and using wine-staging 2.8 I don't see this issue anymore. -- 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.

May 16, 2017

[Bug 42845] Hearthstone crashes at loading screen

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42845 volerig(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volerig(a)gmail.com --- Comment #21 from volerig(a)gmail.com --- (In reply to evilny0 from comment #20) > (In reply to Yehia Hafez from comment #19) > > Disabling dbghelp seemed to have fixed the same problem for me. > > This was enough to fix the problem for me as well with wine staging 2.7. Same here, all the other workarounds did not work for me. But one have to know that disabling dbghelp will prevent the Blizzard app from displaying the "login" button on the login window. -- 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.

May 16, 2017

[Bug 42673] Battle.net no longer runs after Wow Legion update

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42673 --- Comment #10 from winetest(a)luukku.com --- (In reply to Grigorii from comment #9) > Sorry, I have not figured this out bugzilla yet. I wanted to edit, I added a > new post Well I could be wrong, I don't know how to proof this. I think it's the Battle.net that has somehow regressed with wine. I tried 1st wine-staging 2.8 64 bit prefix and Downloaded the base files for wow I was able to launch the game but it was non working condition. I wasnt able to get into game. I quess the game defaulted 64bit version and didnt work because work in progress of dx11 implemention. The screen content after some animation was almost all black. Then I made new prefix with wine 2.8-git-nonstaging and it crashes everytime with some game ID code. But staging doesn't have this issue. You can login with staging with no issues. ACTUALLY. Now I looked at your attachment comment 0 and I get the same crash thing at every login attempt. I also used and tried winetricks -q corefonts. Staging has some patch or patches that fix this login issue. I doubt it's WOW's fault. Well if someone would want to help here he should somehow figure out what staging patches prevents the crash seen at comment 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.

May 16, 2017

[Bug 35142] Lara Croft and the Guardian of Light: screen filled with artefacts when StrictDrawOrdering disabled

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=35142 --- Comment #8 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Still present in wine-2.8-25-gbe12c5bc4f. Enabling CSMT makes the problem go away. OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 381.22 -- 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.

May 16, 2017