September 2019 - Wine-Bugs - list.winehq.org

[Bug 38699] New: Consortium Master Edition: intro scene empty/flickering
by wine-bugs＠winehq.org Oct. 10, 2019

Oct. 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=38699 Bug ID: 38699 Summary: Consortium Master Edition: intro scene empty/flickering Product: Wine Version: 1.7.44 Hardware: x86 URL: http://store.steampowered.com/app/264240 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 51624 --> https://bugs.winehq.org/attachment.cgi?id=51624 terminal output I tested this bug with the GOG.com version of the game. When starting a new game from the main menu, the game begins with an intro sequence, but only the HUD can be seen, the screen is filled with solid color and it's flickering. I can't get past the intro due to this bug. Tried with native d3dx9*, disabled GLSL and with the CSMT patchset, but none of them helped. The game developers are aware of the problem when running the game under Wine, one of them submitted a test result on Appdb: https://appdb.winehq.org/objectManager.php?sClass=version&iId=32193 According to him it's a problem on Wine side that it can't handle properly the shaders used by the game. He even posted a workaround to the problem: adding r_signal_fx "0" variable to the config file. To tell the truth it changed nothing for me... the screen is blank for me in the intro whether that variable is 1 or 0. wine-1.7.44-117-gb2aa984 Fedora 21 x86 Nvidia binary drivers 340.76 -- 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.

2 10

[Bug 47780] New: Error after opening WinAmp
by WineHQ Bugzilla Oct. 10, 2019

Oct. 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=47780 Bug ID: 47780 Summary: Error after opening WinAmp Product: Wine Version: 4.0.2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: emilyschulteslifkin(a)gmail.com Created attachment 65269 --> https://bugs.winehq.org/attachment.cgi?id=65269 Downloaded after error with winamp I open Winamp Installer for installation, and it goes to the first screen. After going forward to the next step, it goes to a blank window and then it says a serious error occurred -- 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.

1 2

[Bug 47744] New: Low FPS on few Games with a 16+ cores CPU
by wine-bugs＠winehq.org Oct. 10, 2019

Oct. 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=47744 Bug ID: 47744 Summary: Low FPS on few Games with a 16+ cores CPU Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: florian.richer(a)protonmail.com Distribution: --- On few games (GTAV, Star Citizen, ...) with DXVK. Games run with a low FPS. To resolve it, i must disable 48 cores on my CPU to keep only 16 cores active. I have already contacted DXVK for this bug but is not a bug on their sides but it's a bug caused either by wine or by the kernel. -- 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.

2 5

[Bug 39808] New: either cmd || operator fails to evaluate exit codes or exit codes are incorrect
by wine-bugs＠winehq.org Oct. 10, 2019

Oct. 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=39808 Bug ID: 39808 Summary: either cmd || operator fails to evaluate exit codes or exit codes are incorrect Product: Wine Version: 1.7.55 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: fiendishx(a)gmail.com Distribution: --- seen: echo 0 || echo fail 0 fail It should not be printing fail. It should only print 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.

2 4

[Bug 40531] New: Max Payne 3 : Smoke, plants, blood rendered incorrectly
by wine-bugs＠winehq.org Oct. 10, 2019

Oct. 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=40531 Bug ID: 40531 Summary: Max Payne 3 : Smoke, plants, blood rendered incorrectly Product: Wine-staging Version: 1.9.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 54354 --> https://bugs.winehq.org/attachment.cgi?id=54354 Smoke gun renderer black Hi, I create this bug report to wine-staging because the game runs only with this version of Wine. With the Vanilla version it crashes at launch. You can see on the differents screenshot, Smoke, plants, blood rendered incorrectly in-game. Smoke and blood rendered black while plants rendered white In the terminal output, the console shows continually this line : fixme:d3d:wined3d_texture_generate_mipmaps texture 0x4ee90140 stub! I uploaded to mediafire the +d3d WINEDEBUG : http://www.mediafire.com/download/64drxlxx8i3irxs/d3d_MaxPayne3.txt.tar.xz -- 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.

2 16

[Bug 47696] New: EverQuest Started Appearing Upside-Down After Working Fine for years
by wine-bugs＠winehq.org Oct. 10, 2019

Oct. 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=47696 Bug ID: 47696 Summary: EverQuest Started Appearing Upside-Down After Working Fine for years Product: Wine Version: 4.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq.machg(a)spamgourmet.com Distribution: --- The game EverQuest used to work great for me on Linux (for years I had no issue). Ever since my last system update however, the game's visuals appear inverted/flipped. What's interesting is that the game still behaves as if the video wasn't flipped: if I click where a button *should* be, it works. So it seems like the mouse input layer is working normally, and it's only the video output that has broken. -- 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.

2 7

[Bug 35876] New: Hard Reset renders incorrectly with GLSL enabled
by wine-bugs＠winehq.org Oct. 10, 2019

Oct. 10, 2019

http://bugs.winehq.org/show_bug.cgi?id=35876 Bug ID: 35876 Summary: Hard Reset renders incorrectly with GLSL enabled Product: Wine Version: 1.7.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: kmaterka(a)wp.pl Game renders incorrectly with GLSL enabled. Disabling GLSL lowers amount of video defects considerably, unfortunately it is not fixing all of them. Take a look at screenshots submitted here: http://appdb.winehq.org/screenshots.php?iAppId=13518&iVersionId=25131 Whatever GLSL is enabled or disabled in log you can find a LOT of such errors (this pack of messages in loop): fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. err:d3d:wined3d_debug_callback 0x2337b80: "GL_INVALID_VALUE error generated. Point size must not be negative.". err:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1568 err:d3d:wined3d_debug_callback 0x2337b80: "GL_INVALID_VALUE error generated. Point size must not be negative.". err:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1568 fixme:d3d:gl_stencil_op Unrecognized stencil op 0. fixme:d3d:gl_stencil_op Unrecognized stencil op 0. You can download demo using Steam: http://store.steampowered.com/app/98400/ or from: http://video.cloudfront.bit-tech.net/bitgamer-demo/hardresetdemo_en.exe -- 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.

2 19

[Bug 47789] New: Gameforge Client: Initialization fails due to SparkWebHelper.exe crashing
by WineHQ Bugzilla Oct. 10, 2019

Oct. 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=47789 Bug ID: 47789 Summary: Gameforge Client: Initialization fails due to SparkWebHelper.exe crashing Product: Wine Version: 4.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sickam(a)mail.ru Distribution: --- Created attachment 65278 --> https://bugs.winehq.org/attachment.cgi?id=65278 Wine's terminal output Hello everyone, as in the summary stated the Gameforge Client fails to initialize due to SparkWebHelper.exe crashing. I can click a "retry" symbol in the launcher afterwards, but it keeps failing again and again. You can find a terminal output and a backtrace in the attachments. My system: OS: Gentoo uname -a: Linux gen2 5.2.16-gentoo #1 SMP Sat Sep 21 14:14:44 CEST 2019 x86_64 AMD Ryzen 7 1800X Eight-Core Processor AuthenticAMD GNU/Linux GPU: AMD Vega 56 Window server: xorg-server-1.20.5 Window manager: i3-4.17.1 Mesa: mesa-19.2.0_rc4 LLVM: llvm-9.0.0 Download to the Gameforge Client: https://gameforge.com/en-US/download -- 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.

1 6

[Bug 47503] New: Problems with CreateProcess(CREATE_SUSPENDED) and later ResumeThread
by wine-bugs＠winehq.org Oct. 9, 2019

Oct. 9, 2019

https://bugs.winehq.org/show_bug.cgi?id=47503 Bug ID: 47503 Summary: Problems with CreateProcess(CREATE_SUSPENDED) and later ResumeThread Product: Wine Version: 4.0.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: ghotik2002(a)yahoo.com Distribution: --- I'm trying to port DxWnd ( https://sourceforge.net/p/dxwnd ) on Wine and it runs pretty out of the box for injection based on SetWindowsHook calls, but in many cases it is necessary to use code injection based on thread suspension / resume. An injection mode uses CreateProcess(CREATE_SUSPENDED) and some later ResumeThread call, but the result is an alive process (I can list it with Linux ps command) that is probably still suspended and can't take control of the desktop. If anyone may want to replicate the test, he/she may contact me on SourceForge DxWnd dedicated forum or write me at ghotik2002(a)yahoo.com. -- 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.

2 7

[Bug 45702] New: World of Final Fantasy crashes with page fault on read access to 0x0 at address (0x1409b111f)
by wine-bugs＠winehq.org Oct. 8, 2019

Oct. 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=45702 Bug ID: 45702 Summary: World of Final Fantasy crashes with page fault on read access to 0x0 at address (0x1409b111f) Product: Wine Version: 3.14 Hardware: x86-64 URL: https://store.steampowered.com/app/552700/WORLD_OF_FIN AL_FANTASY/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lockert.fredrick(a)gmail.com Distribution: Debian Created attachment 62129 --> https://bugs.winehq.org/attachment.cgi?id=62129 Backtrace When starting World of Final Fantasy, it crashes with: wine: Unhandled page fault on read access to 0x00000000 at address 0x1409b111f -- 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.

2 3