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

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

Oct. 9, 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 39808] New: either cmd || operator fails to evaluate exit codes or exit codes are incorrect
by wine-bugs＠winehq.org Oct. 9, 2019

Oct. 9, 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. 9, 2019

Oct. 9, 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 35876] New: Hard Reset renders incorrectly with GLSL enabled
by wine-bugs＠winehq.org Oct. 9, 2019

Oct. 9, 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 40378] New: Monitor AOC I-menu not running
by wine-bugs＠winehq.org Oct. 6, 2019

Oct. 6, 2019

https://bugs.winehq.org/show_bug.cgi?id=40378 Bug ID: 40378 Summary: Monitor AOC I-menu not running Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: fatihfawaz(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 54084 --> https://bugs.winehq.org/attachment.cgi?id=54084 Program error i can't running application from AOC, I-menu becouse i have a bug, a bug i attach the file. thank you... -- 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 21312] New: Sony Vegas Movie Studio Platinum 9.0b: Serious issues making video production impossible
by wine-bugs＠winehq.org Oct. 1, 2019

Oct. 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=21312 Summary: Sony Vegas Movie Studio Platinum 9.0b: Serious issues making video production impossible Product: Wine Version: 1.1.35 Platform: x86-64 URL: http://www.softpedia.com/get/Multimedia/Video/Video-Ed itors/Sony-Vegas-Movie-Studio-Platinum.shtml OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gaming4jc2(a)yahoo.com Created an attachment (id=25649) --> (http://bugs.winehq.org/attachment.cgi?id=25649) Numerous FixMes and some Errs... Well, I finally got it installed using winetrick's dontnet20 and wmp9 as suggested on my previous bug report for not being able to install it. It only works on Windows Vista and above compatibility modes, so the log attached was using Windows 7 which seems best. I'm not sure where to start on this bug report. Sony Vegas Movie Studio 9.0b Platinum has several serious issues, all of which we should be able to be determined from the short log attached. I'll list them below: * No plug-ins were found. (This includes the Media Generator, Transitions, and Video FX tabs making them totally unusable) This effects the majority of the application and the "Video Event FX..." window, making the program somewhat useless. * The Audio "Track FX..." and "Apply Non-Real Time Event FX..." windows are both totally unusable since nothing can be clicked in them. The audio plugins there are at least detected, just borked. * Video Preview Window doesn't show anything, and occasionally flickers a different color only when rendering. Terminal cycles a never ending "fixme:msvideo:DrawDibDraw" bug when attempting to play the movie. This also effects the "Video Event Pan/Crop..." window, making it nearly impossible to do animation effects since determining your current location in the window is simply a black screen. * All icons have a black rectangle around them (trivial and probably just a simple alpha transparency bug) Note: Keyword download can be added since Sony Vegas Movie Studio has a free trial. I made this log using the retail version, but it's using the same exe as the one on the softpedia link provided. -- 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.

2 3

[Bug 42316] New: Cannot play multiplayer in Gwent
by wine-bugs＠winehq.org Sept. 30, 2019

Sept. 30, 2019

https://bugs.winehq.org/show_bug.cgi?id=42316 Bug ID: 42316 Summary: Cannot play multiplayer in Gwent Product: Wine-staging Version: 2.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stas5978(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When tried to start Multiplayer's "Casual Math" and wait about 5 sec you will get wine fixme: fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported -- 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 21

[Bug 10130] New: Wine does not compile on x86_64
by wine-bugs＠winehq.org Sept. 29, 2019

Sept. 29, 2019

http://bugs.winehq.org/show_bug.cgi?id=10130 Summary: Wine does not compile on x86_64 Product: Wine Version: CVS/GIT Platform: PC-x86-64 OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: garry.hurley.jr(a)gmail.com CC: posta10100(a)yahoo.it, garry.hurley.jr(a)gmail.com +++ This bug was initially created as a clone of Bug #4594 +++ gcc -c -I. -I. -I../include -I../include -Wall -pipe -fno-strict-aliasing -gstabs+ -Wdeclaration-after-statement -Wpointer-arith -g -O2 -o preloader.o preloader.c preloader.c: In function ‘wld_mmap’: preloader.c:259: warning: cast to pointer from integer of different size preloader.c: In function ‘map_so_lib’: preloader.c:680: warning: cast to pointer from integer of different size preloader.c: In function ‘wld_start’: preloader.c:910: warning: cast from pointer to integer of different size preloader.c:910: warning: cast to pointer from integer of different size {standard input}: Assembler messages: {standard input}:434: Error: suffix or operands invalid for `push' {standard input}:435: Error: suffix or operands invalid for `push' {standard input}:437: Error: suffix or operands invalid for `pop' {standard input}:438: Error: suffix or operands invalid for `pop' {standard input}:439: Error: suffix or operands invalid for `push' {standard input}:524: Error: suffix or operands invalid for `push' {standard input}:524: Error: suffix or operands invalid for `mov' {standard input}:524: Error: suffix or operands invalid for `pop' {standard input}:927: Error: suffix or operands invalid for `push' {standard input}:927: Error: suffix or operands invalid for `pop' {standard input}:1016: Error: suffix or operands invalid for `push' {standard input}:1016: Error: suffix or operands invalid for `pop' {standard input}:1030: Error: suffix or operands invalid for `push' {standard input}:1030: Error: suffix or operands invalid for `pop' {standard input}:1130: Error: suffix or operands invalid for `push' {standard input}:1130: Error: suffix or operands invalid for `mov' {standard input}:1130: Error: suffix or operands invalid for `pop' {standard input}:1153: Error: suffix or operands invalid for `push' {standard input}:1153: Error: suffix or operands invalid for `pop' {standard input}:1356: Error: suffix or operands invalid for `push' {standard input}:1356: Error: suffix or operands invalid for `pop' {standard input}:1550: Error: suffix or operands invalid for `push' {standard input}:1550: Error: suffix or operands invalid for `mov' {standard input}:1550: Error: suffix or operands invalid for `pop' {standard input}:1585: Error: suffix or operands invalid for `push' {standard input}:1585: Error: suffix or operands invalid for `mov' {standard input}:1585: Error: suffix or operands invalid for `pop' {standard input}:1668: Error: suffix or operands invalid for `push' {standard input}:1668: Error: suffix or operands invalid for `mov' {standard input}:1668: Error: suffix or operands invalid for `pop' make[1]: *** [preloader.o] Error 1 make[1]: Leaving directory `/files/awjb/BUILD/wine-0.9.8-fe/loader' make: *** [loader] Error 2 Additional information: As I stated in bug 4594, which was ignored, the current git tree refused to build WITHOUT using the --enable-win64 option. configure --with-x fails. Bug is valid regardless of the --enable-win64 switch. Actual output is similar to the following: /usr/lib64/gcc/x86_64-slamd64-linux/4.1.2/../../../../x86_64-slamd64-linux/bin/ld: i386:x86-64 architecture of input file `c_28606.o' is incompatible with i386 output make[2]: *** [libwine.so.1.0] Error 1 make[2]: Leaving directory `/wine-current/wine/libs/wine' make[1]: *** [wine] Error 2 make[1]: Leaving directory `/wine-current/wine/libs' make: *** [libs] Error 2 This is only the last of such messages. This also occurs when doing ./configure with no options, make depend, and then make. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 6

[Bug 19297] New: MS Office Access Runtime 2007 don't work
by wine-bugs＠winehq.org Sept. 29, 2019

Sept. 29, 2019

http://bugs.winehq.org/show_bug.cgi?id=19297 Summary: MS Office Access Runtime 2007 don't work Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: js-box(a)nm.ru CC: js-box(a)nm.ru MS Office Access Runtime 2007 don't work -- 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.

2 37

[Bug 43270] New: Exact Audio Copy does not detect plugins
by wine-bugs＠winehq.org Sept. 29, 2019

Sept. 29, 2019

https://bugs.winehq.org/show_bug.cgi?id=43270 Bug ID: 43270 Summary: Exact Audio Copy does not detect plugins Product: Wine Version: 2.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: redstone(a)gmail.com Distribution: --- With a clean wine 2.11 (inited with "WINEARCH=win32 wine wineboot"), on Ubuntu 17.04 Zesty: After installing Exact Audio Copy 1.3 (http://www.exactaudiocopy.de/en/index.php/resources/download/) EAC does not detect the plugins that it comes bundled with. Specifically, it does not detect CUE Tools DB Plugin, or the AcoustID Plugin. It looks like this problem existed on older versions of wine/EAC, see comments in https://appdb.winehq.org/objectManager.php?sClass=version&iId=24705. To reproduce: 1. Install EAC 1.3 2. Start EAC 3. Go to menu -> EAC -> EAC Options -> Audio Plugins The list there is empty. It should have CUETools and AcoustID listed (which is what I see when I install EAC 1.3 on my Windows 7 machine) I tried getting some debug info: WINEDEBUG=+relay wine ~/.wine/drive_c/Program\ Files/Exact\ Audio\ Copy/EAC.exe > /tmp/foo 2>&1 but it didn't have anything helpful. Specifically, the DLLs for the plugins don't appear (e.g., CUETools*.dll), nor does PluginHandler.dll appear, so it's like it's not even trying to access them. Any suggestions on how to debug? -- 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 35