December 2021 - Wine-Bugs - list.winehq.org

[Bug 29503] New: Stucuk's Setup System patcher often fails with 'Canvas does not allow drawing' error message
by wine-bugs＠winehq.org Dec. 13, 2021

Dec. 13, 2021

http://bugs.winehq.org/show_bug.cgi?id=29503 Bug #: 29503 Summary: Stucuk's Setup System patcher often fails with 'Canvas does not allow drawing' error message Product: Wine Version: 1.3.36 Platform: x86 URL: http://www.fileplanet.com/207230/200000/fileinfo/Dark- Horizon-Patch-v1.0.6.1 OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 38206 --> http://bugs.winehq.org/attachment.cgi?id=38206 screenshot (patcher running in virtual desktop) The installer of the patch made for Dark Horizon uses a Stucuk's Setup System according to the file properties. The installer of the community patch made for Original War also uses this kind of patcher, sharing the same problem. The patcher for Dark Horizon consists of nearly 3000 small files. The installation process doesn't take long (15-20 seconds). At some point during the install process, the patcher is interrupted with an error message: 'Setup Thread Error: Canvas does not allow drawing', and the installer quits prematurely. This happens fairly often (maybe 8 times out of 10 attempts), but sometimes the patcher finishes the job without erroring out. Before the error message pops up, text which normally appears inside the installer window also printed and overwritten several hundreds of times in the upper left corner of the screen (see attached screenshot). This happens both in virtual desktop mode and in full-screen. To reproduce the problem with the patcher made for Dark Horizon you don't have to download the demo for the game; the patch can be installed alone in a selected directory anywhere inside a wineprefix. -- 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 5

[Bug 41615] New: Max Payne 1 and 2 crash using glsl=enabled
by wine-bugs＠winehq.org Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=41615 Bug ID: 41615 Summary: Max Payne 1 and 2 crash using glsl=enabled Product: Wine Version: 1.9.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Created attachment 55965 --> https://bugs.winehq.org/attachment.cgi?id=55965 backtrace-max-payne-1-glsl Max Payne 1 and 2 crash using glsl=enabled during 1st chapter Both crash during 1st chapter however if use glsl=disabled in wine register works stable both games pass 1st chapter with crashes System Specs Using in Tests Nvidia Drivers 375.10 (run package from nvidia drivers homepage) Xubuntu 16.04 64Bit - Kernel 4.4.0-44 generic (ubuntu mainline) - CPUFreq: Performance CPU: INTEL Pentium G3258 (Haswell 22nm) 4.1Ghz + Artic Cooling Alpine 11 Plus MEMORY: 8GB DDR3 1333 (2x4) Patriot value (dual channel: 21.3 gb/s) GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz 64Bit (14.4Gb/s) MAINBOARD: MSI H81M E33 -- 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 17

[Bug 41653] New: The Banner Saga 2 GOG (adobe air) flickering on Wine-staging
by wine-bugs＠winehq.org Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=41653 Bug ID: 41653 Summary: The Banner Saga 2 GOG (adobe air) flickering on Wine-staging Product: Wine-staging Version: 1.9.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: donanykey(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 56035 --> https://bugs.winehq.org/attachment.cgi?id=56035 Video of flickering picture Dedicating separate bug from https://bugs.winehq.org/show_bug.cgi?id=41635 for Wine-staging. The game works in plain Wine (1.9.21), but with very poor frame rate performance, while with staging - it's much more responsive, but the picture is flickering. Video and log to be attached -- 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 25

[Bug 33309] New: No keyboard input in Slender: The Arrival
by wine-bugs＠winehq.org Dec. 12, 2021

Dec. 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=33309 Bug #: 33309 Summary: No keyboard input in Slender: The Arrival Product: Wine Version: 1.5.27 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: 6tsukiyami9(a)gmail.com Classification: Unclassified The title says all about it: the keyboard doesn't work at all in Slender: The Arrival. I can't even try the game itself because I can't get enter the license key and get to the main menu. I guess this may be a clue: fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterDeviceNotificationW (hwnd=0x1006a, filter=0x33fc6c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. I'm attaching a full log with WINEDEBUG=-all,+keyboard,+key,+dinput,+message -- 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 15

[Bug 39305] New: Sanitarium
by wine-bugs＠winehq.org Dec. 12, 2021

Dec. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=39305 Bug ID: 39305 Summary: Sanitarium Product: Wine Version: 1.7.50 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: i30817(a)gmail.com Distribution: --- There are plenty of bugs with sanitarum that are closed 'FIXED' that i'm still experiencing, except if running with the game windowed mode command line switch (-w). For example the game doesn't show graphics with the native fullscreen here (with the open source radeon drivers) unless i specify : wine reg add "HKCU\\Software\\Wine\\Direct3D" /v "OffscreenRenderingMode" /t REG_SZ /d "backbuffer" before running the game (instead of default "fbo") Bug #28625 is also still a problem. In fact, it appears more of a problem because with native fullscreen and that registry setting just moving the mouse at all is liable to freeze the screen and every animation on it, no just pause while moving (the game is still running because i can press ESC to go to the settings menu). This seems like a regression, since bug #28625 is marked as fixed. -- 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 8

[Bug 41681] New: King's Bounty crossworlds: DirectX call failed
by wine-bugs＠winehq.org Dec. 12, 2021

Dec. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=41681 Bug ID: 41681 Summary: King's Bounty crossworlds: DirectX call failed Product: Wine Version: 1.6.1 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lior.inbar(a)sharecare.com Created attachment 56071 --> https://bugs.winehq.org/attachment.cgi?id=56071 terminal Hi, I'me running the game on: Model Name: MacBook Pro Model Identifier: MacBookPro11,4 Processor Name: Intel Core i7 Processor Speed: 2.2 GHz Graphics Intel Iris Pro 1536 MB The games launches fine but in some parts of the map it quits with error: http://i63.tinypic.com/oixkli.png when not running from terminal this game doesn't crash but the graphics are distorted like this: http://tinypic.com/view.php?pic=2iazrb8&s=9#.WCG--eErLGI attached is the terminal output -- 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 9

[Bug 38553] New: Die by the Sword: menus don't drawn unless mouse is moving (Mac OS X only)
by wine-bugs＠winehq.org Dec. 12, 2021

Dec. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=38553 Bug ID: 38553 Summary: Die by the Sword: menus don't drawn unless mouse is moving (Mac OS X only) Product: Wine Version: 1.7.34 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs140(a)gmail.com A similar issue (Bug 27814) has already been fixed in Wine for Linux. But the problem still exists when running Wine in OS X. Important comments from the Linux bug report: "Béla Gyebrószki (In reply to Ken Thomases from comment #12) > This problem still exists for me on OS X, too. Plain Wine. (If you're > using the tip from this morning, you'll need > <http://source.winehq.org/patches/data/108886> to fix a crash.) Affects > both the Mac driver and the X11 driver. > > In my testing, it was often the case that moving the mouse was not enough to > cause the menu animation to proceed. When this happened, switching away > with Command-Tab would allow the animation to complete. This happened more > often with the Mac driver than the X11 driver, but did affect both. > > Béla, would you be willing to do a "reverse" bisect, where you hunt which > commit fixed it for you? It's hard to tell exactly which commit fixed the problem for me because the game behaves differently between 1.7.13 and .15. The problem is definitely there in 1.7.13. After this patch menus are opened but without that "pull-down animation" and screen refreshing, mouse movement is so sluggish that it makes the game unplayable: http://source.winehq.org/git/wine.git/commit/4c4552c5a1910a9d5adf8eccff0ac6… Finally this commit resolves the previous problem and menus work as intended: http://source.winehq.org/git/wine.git/commit/eef81f5ecc27cac8bc2bf4eacdc093…" -- 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 9

[Bug 50864] New: Incompatibility with Mesa 21 with several games
by WineHQ Bugzilla Dec. 12, 2021

Dec. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=50864 Bug ID: 50864 Summary: Incompatibility with Mesa 21 with several games Product: Wine Version: 6.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bastian.beischer(a)rwth-aachen.de Distribution: --- Arch Linux recently updated mesa to 21, after which I was unable to start most of the games I play through Steams proton (Through the Ages, Race for the Galaxy, Galaxy Trucker, ...). Since proton is based on wine I later found a command line reproducer for the problem by just running "wine game.exe" with the appropriate wine prefix. After noticing that the issues appeared with Mesa 21 I found this on the Mesa gitlab: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 My issues are exactly the same. Apparently Mesa added an OpenGL error in this commit / line: https://gitlab.freedesktop.org/mesa/mesa/-/commit/f39fd3dce72eaef59ab39a23b… And it appears that wine fails to correctly handle / catch that error. I can play games again after reverting that change in mesa and recompiling mesa 21. While it was mesa that introduced this regression it appears that it is correct to issue the error, so the mesa developers seem to think that wine should be patched instead (they even made an attempt). Thanks for any help! -- 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 17

[Bug 44989] New: disciples 3 crashing on start
by wine-bugs＠winehq.org Dec. 12, 2021

Dec. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=44989 Bug ID: 44989 Summary: disciples 3 crashing on start Product: Wine Version: 3.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimonych85(a)ukr.net Distribution: --- Created attachment 61123 --> https://bugs.winehq.org/attachment.cgi?id=61123 Disciples 3 not working when starting the game it shows me a picture in game but no menu, its stucked -- 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 6

[Bug 38173] New: Juiced Dont Start
by wine-bugs＠winehq.org Dec. 12, 2021

Dec. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=38173 Bug ID: 38173 Summary: Juiced Dont Start Product: Wine Version: 1.7.37 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Created attachment 50923 --> https://bugs.winehq.org/attachment.cgi?id=50923 backtrace juiced Juiced dont start, unable validate settings Wine 1.7.37 Nvidia Drivers 346.47 Linux Mint 17 XFCE Edition 64Bit - Kernel 3.18.0.31 CPU: INTEL Pentium G3220 3.0Ghz MEM: 8GB DDR3 1333 (2x4) Patriot value (128 bit dual channel: 21.3 gb/s) GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz 64Bit (14.4Gb/s) BOARD: MSI H81M E33 -- 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