wine-bugs November 2022

wine-bugs@winehq.org

1 participants
3244 discussions

[Bug 48911] New: Check for compilation warnings
by WineHQ Bugzilla 09 Jan '23

09 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=48911 Bug ID: 48911 Summary: Check for compilation warnings Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Compiling Wine with -Werror is troublesome because it applies blindly to both wine-devel patches and patches submitted manually via the website. The sole purpose of the latter is often to just clarify some point for the development of another patch and are not meant to be submitted. Thus failing on warnings just makes running these quick tests more cumbersome. So the best way forward would be for the TestBot to identify and report warnings but not fail the compilation and abort the tests when they occur. So: 1. The builds should happen without -Werror. 2. GetLogLineCategory() should identify the warnings and add them to LogInfo but distinguish them from errors (replace IsNew with a Category field?). 3. Compare task.log to the reference build log to distinguish new warnings from old ones. This is necessary in case the compiler used by the TestBot produces warnings on the unpatched Wine tree. It will require storing the build logs in latest/ just like the TestBot already does for the reference WineTest reports. 4. LogInfo's will need to keep track of the number of new warnings which really means renaming the 'NewCount' field to avoid confusion. 5. The warnings should be saved in the errors files. The new line types could be 'w' and 'W' for old and new warnings respectively (then it would make sense to use e and E for errors). 6. This will let the WineRun*() scripts know about both warnings and errors. They can then decide what to do depending on the type of job and whether the warnings are new or not. - Old warnings would always be ignored. - If a build task has new warnings, instead of marking it as 'badbuild' it could be marked as 'completed' as usual but with a non-zero number of failures. This would probably allow running the tests on Windows but the patch would still be considered bad since the job would end up with a non-zero number of failures. - For Wine tasks the number of warnings would be added to the Failures field for the same overall result. - So in both cases the non-zero number of failures would only impact wine-devel patches. 7. The JobDetails page should show the warnings in summary mode and highlight them in the full build log. That would make it easy for developers to see the warnings on web-submitted jobs, and thus fix them before submitting the patch to wine-devel. -- 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 43653] New: Waves Central: install vst plugins issue
by wine-bugs＠winehq.org 09 Jan '23

09 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=43653 Bug ID: 43653 Summary: Waves Central: install vst plugins issue Product: Wine Version: 2.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: viking991(a)gmx.de Distribution: --- Created attachment 59080 --> https://bugs.winehq.org/attachment.cgi?id=59080 waves central error message Hi! Waves Central (license manager / installer from waves.com) does not install vst plugins in Wine. installation aborts with this message box, also see attachment ### Sorry An error has occurred during installation Please follow the steps in this troubleshooter ### - System: winehq-staging 2.16 debian stretch - Steps to re-produce: 1) Download Waves Central installer http://www.waves.com/downloads/central Direct download link: http://www.waves.com/dlrdr?id=central-win Tested Waves Central Version: V1.3.3.4 sha1sum Install_Waves_Central.exe 0f90b9333855a8713e3f9ced767369364a46aa33 Install_Waves_Central.exe 2) Run Installer wine64 Install_Waves_Central.exe 3) Run Waves Central wine64 Waves\ Central.exe 4) Log in unfortunately this needs an account with waves.com: -> Log in -> create account -> web browser opens to create account user user/pass in Waves Central to log in. 5) install any VST: -> install products -> install from online -> choose products to install -> All Waves products -> select any product, for example H-Reverb Hybrid Reverb 9 -> click install, message box as attached appears. also check bug 43648 Thanks! -- 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 42588] New: Vietcong - graphics glitches since Wine 2.1
by wine-bugs＠winehq.org 09 Jan '23

09 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=42588 Bug ID: 42588 Summary: Vietcong - graphics glitches since Wine 2.1 Product: Wine Version: 2.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: havran.jan(a)email.cz Distribution: ArchLinux Created attachment 57517 --> https://bugs.winehq.org/attachment.cgi?id=57517 Vietcong - terminal log In version 2.1 was introduced new bug that causes graphical glitches like flickering soldiers. I can confirm this bug in wine versions 2.1, 2.2 and 2.3. In versions 2.0 and below it worked probably fine - this bug is not 100% reproducible - sometimes soldiers are flickering and glitches are shown very often, sometimes just for few milisecond, but i am pretty sure that this was introduced in version 2.1 Tested on Intel and AMD GPUs, Vietcong 1.60 with VCStarter 1.7 Beta -- 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 22

[Bug 50218] New: Unable to finish the installation of Lego Staunt rallye: request for indeo codec
by WineHQ Bugzilla 08 Jan '23

08 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=50218 Bug ID: 50218 Summary: Unable to finish the installation of Lego Staunt rallye: request for indeo codec Product: Wine Version: 5.22 Hardware: x86 URL: https://www.myabandonware.com/game/lego-stunt-rally-bd 5#download OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeremielapuree(a)yahoo.fr Distribution: Ubuntu Created attachment 68723 --> https://bugs.winehq.org/attachment.cgi?id=68723 screenshot of the error At the end of the stage of install, setup complains about indeo codecs. -- 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 4

[Bug 53619] New: World of Warcraft Shadowlands randomly crashes
by WineHQ Bugzilla 08 Jan '23

08 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53619 Bug ID: 53619 Summary: World of Warcraft Shadowlands randomly crashes Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cianuro2036(a)protonmail.com Distribution: --- This is something that has happened on multiple hardware, platforms and OS distros. This is also something that has been happening for a while, I just decided to report it because It can affect some parts of the game, such as rated PVP. The particular error logs as follows: 05f4:err:seh:dispatch_exception unknown exception (code=c0000420) raised wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. How to reproduce: This feels 'random' but makes me _think_ it could be a memory leak issue. If you're in highly populated areas _or_ highly demanding zones, it can trigger itself. Two recent scenarios I can recall - First, doing multiple arena matches and waiting for the queue in Oribos. The crash happened specifically during arena. - Second, doing the Ashran Brawl Battleground. This battleground is very, very long and has a lot of people around. In both scenarios there is a slowdown in FPS in both areas. -- 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 8

[Bug 53403] New: winegstreamer "flush" removal breaks radio in fallout 3
by WineHQ Bugzilla 07 Jan '23

07 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53403 Bug ID: 53403 Summary: winegstreamer "flush" removal breaks radio in fallout 3 Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)dflies.us Distribution: --- https://gitlab.winehq.org/wine/wine/-/merge_requests/105#note_4805 https://gitlab.winehq.org/wine/wine/-/commit/5144b27661fcd6705353d832e03830… In Wine 7.2 or 7.3 there was a removal of "flush" in wg_parser. This makes some audio (in particular Fallout 3 Radio) chuggy and slows down the entire game. Reintroducing flushing fixes the issue but devs think the problem should be fixed elsewhere. -- 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 8

[Bug 44230] New: SlingPlayer 1.5 crashes during configuration
by wine-bugs＠winehq.org 07 Jan '23

07 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=44230 Bug ID: 44230 Summary: SlingPlayer 1.5 crashes during configuration Product: Wine Version: 2.22 Hardware: x86 URL: http://download.slingmedia.com/player/pc/SlingPlayer-S etup-EU-1.5.1.343.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: julliard(a)winehq.org Regression SHA1: 01676c5dd6f9fb61b9c4e52595f6e75e21050009 Distribution: Ubuntu Created attachment 60025 --> https://bugs.winehq.org/attachment.cgi?id=60025 Wine 3.0-rc3 console output SlingPlayer 1.5 crashes when attempting to configure the Slingbox (Alt+E --> Slingbox Configuration --> Change...) (Slingbox needed) Native qcap causes a new problem so can't try that as a workaround. Native quartz needed to get this far. The crash does not occur in Staging 2.21. I compiled Wine 3.0-rc3 with -O0 and the crash does not occur. Compiling again with -O1 or -O2 and the problem returns (did not try -O3). I also receive the following warning during compilation, but further testing suggests it is not related: cc1: warning: unrecognized command line option ‘-Wno-packed-not-aligned’ I tried reverting 6864803f1ab70f9f9e90903b13e67da40973d12a but it did no make any difference. https://source.winehq.org/git/wine.git/commitdiff/6864803f1ab70f9f9e90903b1… I also tried compiling with the following, which the man page claims GCC sets with -O1, but the crash still didn't occur: -fomit-frame-pointer -ftree-phiprop -ftree-sink -ftree-slsr -ftree-sra -ftree-pta -ftree-ter -funit-at-a-time -ftree-copy-prop -ftree-copyrename -ftree-dce -ftree-dominator-opts -ftree-dse -ftree-forwprop -ftree-fre -fmove-loop-invariants -fshrink-wrap -fsplit-wide-types -ftree-bit-ccp -ftree-ccp -fssa-phiopt -ftree-ch -finline-functions-called-once -fipa-pure-const -fipa-profile -fipa-reference -fmerge-constants -fdelayed-branch -fdse -fforward-propagate -fguess-branch-probability -fif-conversion2 -fif-conversion -fauto-inc-dec -fbranch-count-reg -fcombine-stack-adjustments -fcompare-elim -fcprop-registers -fdce -fdefer-pop The crash goes away when reverting commit 01676c5dd6f9fb61b9c4e52595f6e75e21050009 and recompiling. 01676c5dd6f9fb61b9c4e52595f6e75e21050009 is the first bad commit commit 01676c5dd6f9fb61b9c4e52595f6e75e21050009 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Sat Nov 25 11:48:02 2017 +0100 user32: Use the magic format string prefix for relay traces. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 c075dd76fd2d86e2cb8e14a300f4f8a7a8952bf4 ab6d49e1c18eae5208a19b0be062ffbf7abc8518 M dlls Staging 2.21 does have this commit, but the binary packages do, beginning with release 3.0-rc1. Workaround unknown. -- 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 13

[Bug 54023] New: d3d11:d3d11 - test_dynamic_map_synchronization() fails on w11pro64_nv
by WineHQ Bugzilla 07 Jan '23

07 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54023 Bug ID: 54023 Summary: d3d11:d3d11 - test_dynamic_map_synchronization() fails on w11pro64_nv Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d11:d3d11 - test_dynamic_map_synchronization() fails on w11pro64_nv: d3d11.c:34427: Test failed: Got 0xff0000ff, expected 0xff00ff00 at (3, 5, 0), sub-resource 0. See https://test.winehq.org/data/patterns.html#d3d11:d3d11 Note: w11pro64_nv is the TestBot's NVIDIA RTX3050 PCI passthrough Windows 11 21H2 VM. The plain QXL (QEmu), and AMD PCI passthrough test configurations have d3d11:d3d11 failures too but in other test functions. -- 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 4

[Bug 53995] New: d2d1:d2d1 runs out of GL memory and crashes on the debian 11 VM
by WineHQ Bugzilla 07 Jan '23

07 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53995 Bug ID: 53995 Summary: d2d1:d2d1 runs out of GL memory and crashes on the debian 11 VM Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d2d1:d2d1 runs out of GL memory and crashes on the debian 11 VM: d2d1.c:7145: Test marked todo: Figure does not match. Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x6ab30fe4). [...] Backtrace: =>0 0x6ab30fe4 memset+0x24(dst=0x000000000, c=0, n=0x12c000) [Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3205] in ucrtbase (0x0685f908) 1 0x008a9073 wined3d_texture_load_location+0x423(texture=002CB990, sub_resource_idx=0, context=00289F90, location=0x8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:862] in wined3d (0x0685f9a8) 2 0x00897fce surface_cpu_blt+0x9ee(dst_texture=002CB990, dst_sub_resource_idx=0, dst_box=0685FB38, src_texture=0028D170, src_sub_resource_idx=0, src_box=0685FB50, flags=0x20000000, fx=0685FB68, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:752] in wined3d (0x0685faf8) 3 0x00899ac2 cpu_blitter_blit+0xc2(blitter=002BB820, op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170, src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10, dst_texture=002CB990, dst_sub_resource_idx=<is not available>, dst_location=0x8, dst_rect=0685FE20, color_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1328] in wined3d (0x0685fb98) 4 0x008b7622 ffp_blitter_blit+0xa2(blitter=002BB838, op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170, src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10, dst_texture=002CB990, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=0685FE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:6190] in wined3d (0x0685fc58) 5 0x0085d36d glsl_blitter_blit+0x1ad(blitter=002BB850, op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170, src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10, dst_texture=002CB990, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=0685FE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\glsl_shader.c:13270] in wined3d (0x0685fd78) 6 0x0089ada1 texture2d_blt+0x3c1(dst_texture=002CB990, dst_sub_resource_idx=0, dst_box=05B678B4, src_texture=0028D170, src_sub_resource_idx=0, src_box=05B678D4, flags=0x20000000, fx=05B678F0, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1639] in wined3d (0x0685fe48) 7 0x0081b8ad wined3d_cs_exec_blt_sub_resource+0xcd(cs=05B50020, data=05B678A8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:2579] in wined3d (0x0685fec8) 8 0x0081d37b wined3d_cs_command_unlock(queue=<internal error>, cs=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3310] in wined3d (0x0685ff28) 9 0x0081d37b wined3d_cs_execute_next+0x53(ctx=<couldn't compute location>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3309] in wined3d (0x0685ff28) 10 0x0081d37b wined3d_cs_run+0x13b(ctx=<couldn't compute location>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3376] in wined3d (0x0685ff28) [...] 7145 is the most common last trace seen, though 7033 also appears at least once, but running with WINETEST_REPORT_SUCCESS I get different locations. See https://test.winehq.org/data/patterns.html#d2d1:d2d1 Furthermore when reproducing this I saw out-of-memory traces right before the crash. For instance: d2d1.c:601: Test succeeded 01d8:err:d3d:wined3d_debug_callback 00291C38: "GL_OUT_OF_MEMORY in glBufferStorage". 01d8:err:d3d:wined3d_debug_callback 00291C38: "GL_INVALID_VALUE in glMapBufferRange(offset 0 + length 67108864 > buffer_size 0)". 01d8:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory. 01d8:err:d3d:wined3d_bo_gl_map Failed to map chunk. 01d8:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo. wine: Unhandled page fault on write access to 00000000 at address 6AB30FE4 (thread 01d8), starting debugger... It's not clear why only the debian11 VM is impacted: it has a dual-screen configuration but so does debiant so it does not appear to be a multi-monitor thing, and this does not happen on fgtb-debian11 or debian11b so it's not a Debian version issue. -- 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 7

[Bug 53752] New: Rayman 3: glitched graphics (black textures)
by WineHQ Bugzilla 07 Jan '23

07 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53752 Bug ID: 53752 Summary: Rayman 3: glitched graphics (black textures) Product: Wine Version: 7.3 Hardware: x86-64 URL: https://archive.org/download/rayman-3-pc-demo/Rayman3_ PC-Demo.zip OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 1b1b03055db8bf03c6783d4fcb19abf670d53338 Distribution: --- There are lots of black textures in Rayman 3 thus not so much of the game can be seen. Can be reproduced with the demo: the issue is already present in the main menu. According to my testing the problem appeared with commit 1b1b03055db8bf03c6783d4fcb19abf670d53338 wined3d: Try to allocate new OpenGL BOs from the client thread for DISCARD maps. With the previous commit in-game scenery looks good. Workaround: disable hardware TnL in the video settings utility called R3_Setup_DX8.exe in the demo. Rayman3_PC-Demo.zip (184M) md5: d6d3c2d76931feff73f56295a0dee6a3 Still present in wine-7.18-120-g001665d7354. OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03 OpenGL core profile shading language version string: 4.60 NVIDIA -- 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 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs November 2022