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

[Bug 43641] World of Warcraft crashes when liquid details are more than low

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43641 --- Comment #3 from Matteo Bruni <matteo.mystral(a)gmail.com> --- Can you also try to disable nvapi64.dll? If that doesn't make any difference, please attach a +tid,seh,d3d9,d3d,d3d_shader trace of the crash. -- 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.

Aug. 31, 2017

[Bug 43599] Engine Prime: application fails to launch

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43599 --- Comment #9 from Fabian Maurer <dark.shadow4(a)web.de> --- > Quick question: I am encountering various issues as I test the application. > Should each one be raised as an individual bug or appended to this bug? If the issues are not related it makes sense to report them separately. If you think they're related, I'd put them into the same bugreport. You can always split them off later - or have bug reports closed as duplicates. -- 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.

Aug. 31, 2017

[Bug 43599] Engine Prime: application fails to launch

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43599 --- Comment #8 from Adam Szmigin <smidge(a)xsco.net> --- Quick question: I am encountering various issues as I test the application. Should each one be raised as an individual bug or appended to this bug? (The reason for uncertainty is that this is a brand new application, and I get the feeling it is likely to experience many issues in functionality. So I want to strike the right balance between structured bug reporting and spamming bugzilla with potentially-related issues.) Thanks, Adam -- 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.

Aug. 31, 2017

[Bug 43642] Internet Download Manager TDI Driver 'idmtdi.sys' crashes on unimplemented function ntoskrnl.exe.IoReleaseRemoveLockAndWaitEx

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43642 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Wine Summary|Unhandled exception: |Internet Download Manager |unimplemented function |TDI Driver 'idmtdi.sys' |ntoskrnl.exe.IoReleaseRemov |crashes on unimplemented |eLockAndWaitEx called in |function |64-bit code |ntoskrnl.exe.IoReleaseRemov |(0x000000007b4500b7). |eLockAndWaitEx Component|-unknown |ntoskrnl CC| |focht(a)gmx.net --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, refining fields. Not a Wine-Staging problem. You appear to reuse/recycle the default WINEPREFIX (~/.wine) for multiple software installations. Don't do that unless you know the implications and can support/diagnose/repair problems yourself. The default prefix will be messed up at one point beyond repair. Your current problem is the result of this. Isolate each software installation into an own WINEPREFIX. https://wiki.winehq.org/FAQ#Wineprefixes https://wiki.winehq.org/FAQ#How_do_I_wipe_the_virtual_Windows_installation.… Regards -- 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.

Aug. 31, 2017

[Bug 31973] AppDB admins need spam control tools

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=31973 --- Comment #10 from Rosanne DiMesio <dimesio(a)earthlink.net> --- Maintainers already have the ability to delete spam; that's a key part of their responsibilities. Unfortunately, not all maintainers are doing their jobs. If you see spam, first report it to the maintainer, and if he/she doesn't respond in a reasonable amount of time, report it on https://forum.winehq.org/viewforum.php?f=11. -- 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.

Aug. 31, 2017

[Bug 43642] Unhandled exception: unimplemented function ntoskrnl.exe.IoReleaseRemoveLockAndWaitEx called in 64-bit code (0x000000007b4500b7).

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43642 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- The issue appears when you run winecfg in terminal? Did you try it in a fresh wineprefix? What dll-overrides are you using? -- 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.

Aug. 31, 2017

[Bug 43465] Unit Test: ComboBox Dropdown does not work if Style is set and no scrollbar required

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43465 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #58850|0 |1 is obsolete| | --- Comment #14 from Fabian Maurer <dark.shadow4(a)web.de> --- Created attachment 59068 --> https://bugs.winehq.org/attachment.cgi?id=59068 Updated hack Small update, a patch that helps bring this issue forward just got accepted: https://source.winehq.org/git/wine.git/commit/f7f7b89e2e9117811c91269643868… Referring to your updated test program from #Comment 7 here: The two bottom examples "3,6" and "5,6" now work. The top combobox "6,3" is still wrong though. Attached an updated hack for the current git tree, or wine-2.16 and up. Code is now simpler, still looks like an workaround though. I'll look into it when I have time. -- 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.

Aug. 31, 2017

[Bug 43314] Missing characters/models in d3d11 Unity 5 games

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43314 winehq(a)codingcatgirl.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq(a)codingcatgirl.de --- Comment #8 from winehq(a)codingcatgirl.de --- > To clarify, everything seems to work and render fine (terrain, scenarios, > menus, game gui), but moving characters/models do not show up. Sometimes some > props from characters can be seen. This also happens with the game “Life is Strange: Before The Storm” that was released today. With the default wine branch, the game only shows a pink screen with sound, so i could only observe this behaviour with wine-staging. The following lines are repeated all the time in the log output… presumably on each frame: fixme:d3d:context_check_fbo_status FBO status GL_FRAMEBUFFER_INCOMPLETE_LAYER_TARGETS (0x8da8) fixme:d3d:context_dump_fbo_attachment GL_DEPTH_ATTACHMENT: 2d texture 1138, 256x256, format 0x81a6. fixme:d3d:context_dump_fbo_attachment GL_STENCIL_ATTACHMENT: NONE. err:d3d:wined3d_debug_callback 0x62bb70: "GL_INVALID_OPERATION in glBindTexture(target mismatch)". fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT0: 2d-array texture 1125, 256x256, format 0x822e. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT1: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT2: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT3: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT4: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT5: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT6: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT7: NONE. err:d3d:wined3d_debug_callback 0x62bb70: "GL_INVALID_FRAMEBUFFER_OPERATION in glDrawElements(incomplete framebuffer)". -- 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.

Aug. 31, 2017

[Bug 43625] Crysis 3: Blank screen for a 32 bit application in 32 bit WINEPREFIX, 64 bit WINEPREFIX works (WoW64) - native d3dcompiler_46.dll/ 3dcompiler_43.dll needed

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43625 Johannes <jojos_band(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Crysis 3: Blank screen for |Crysis 3: Blank screen for |a 32 bit application in 32 |a 32 bit application in 32 |bit WINEPREFIX, 64 bit |bit WINEPREFIX, 64 bit |WINEPREFIX works (WoW64) |WINEPREFIX works (WoW64) - | |native | |d3dcompiler_46.dll/3dcompil | |er_43.dll needed -- 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.

Aug. 31, 2017

[Bug 43625] Crysis 3: Blank screen for a 32 bit application in 32 bit WINEPREFIX, 64 bit WINEPREFIX works (WoW64)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43625 --- Comment #2 from Johannes <jojos_band(a)gmx.net> --- (In reply to Sebastian Lackner from comment #1) > Could you please attach terminal output? My guess would be that you are > either > > - missing 32-bit graphic drivers or other graphic driver related components. > On most distributions they have to be installed separately because they are > not a dependency of Wine. > > - or the game runs out of memory before it can display anything. Taking a > look at the memory usage and terminal output could also help here. I was able to workaround this issue by just looking into the terminal output of both installations - thanks for pointing me to the console output (and shame on me for not looking there first). Observation: "err:d3dcompiler:compile_shader HLSL shader parsing failed." Solution: Copy d3dcompiler_{43.46}.dll to windos/system32 in the 32 bit wineprefix, set d3dcompiler_{43,46}.dll to "native", then it 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.

Aug. 31, 2017