wine-bugs August 2023

wine-bugs@winehq.org

1 participants
3065 discussions

[Bug 55241] New: The 64-bit winmm:capture & winmm:wave crash on Windows 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55241 Bug ID: 55241 Summary: The 64-bit winmm:capture & winmm:wave crash on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit winmm:capture & winmm:wave crash on Windows 8: capture.c:171: this is the last test seen before the exception 07d0:capture: unhandled exception c0000005 at 00007FFDC66DCF38 wave.c:686: this is the last test seen before the exception 0b14:wave: unhandled exception c0000005 at 00007FFDC66DCF38 See https://test.winehq.org/data/patterns.html#winmm:capture https://test.winehq.org/data/patterns.html#winmm:wave This started with the GitLab CI's switch to Debian 12 (bookworm) for the build system: * The winmm_test.exe binary produced by the TestBot's Debian 11-based build VM produces no failures when run on Windows while GitLab CI's binary for the same Wine version produces this set of failures. * And the TestBot runs the official WineTest builds on its Windows VMs which is why the failures appeared on 2023-07-10 which corresponds to this commit: commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Jul 10 17:18:49 2023 +0200 gitlab: Upgrade the Debian image to bookworm. Now the question is whether the new build environment revealed a preexisting bug in Wine, or if the new build environment itself is broken, or if the bug is elsewhere such as in the MinGW compiler. This is also likely the same issue as bug 55240. -- 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 3

[Bug 54744] New: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54744 Bug ID: 54744 Summary: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows: taskbarlist.c:61: Test failed: Got hr 0x80004001. taskbarlist.c:66: Test failed: Got hr 0x80004001. See https://test.winehq.org/data/patterns.html#explorerframe:taskbarlist Where 0x80004001 == E_NOTIMPL On average this happens about once every other month on recent Windows 10 versions: * 2022-08-31 on w1064-tsign-64 (21h2) * 2022-11-14 on w1064-tsign-32 (21h2) * 2023-01-10 on fgtb-w10pro64-rx550-64 (22h2) * 2023-02-06 on w10pro64-rx550-64 (22h2) * 2023-03-27 on w10pro64-ar-64 (21h1) -- 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 3

[Bug 54069] New: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54069 Bug ID: 54069 Summary: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+ 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 ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+. ddraw7.c:18954: Test failed: Got unexpected color 0x00000040. and ddraw7.c:18972: Test failed: Got unexpected color 0x00ff00ff. See https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Notes: * There is no evidence of this happening on Windows 11. * This seems to only happen with Microsoft's "Microsoft Basic Display Adapter" driver: the "-1qxl" and "-2qxl" (dual-monitor) configuration use the "Red Hat QXL controller" driver and are are not affected. Neither are the AMD / NVIDIA PCI passthrough configurations. * The 0x00000040 result mostly happens on Windows 8 to Windows 10 1607 but it also happened a couple of times on Windows 10 21H2. Meanwhile the 0x00ff00ff result seems to only happen on Windows 10 2004+. * ddraw:ddraw1, ddraw:ddraw2 and ddraw:ddraw4 have a similar test function but don't have this failure. -- 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 3

[Bug 43017] New: Unreal Tournament 2004/UT2004.exe crashes due to " intel_do_flush_locked failed: Cannot allocate memory"
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43017 Bug ID: 43017 Summary: Unreal Tournament 2004/UT2004.exe crashes due to "intel_do_flush_locked failed: Cannot allocate memory" Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Unreal Tournament 2004/UT2004.exe crashes due to `intel_do_flush_locked failed: Cannot allocate memory` the debug output of PlayOnLinux reads ``` [05/12/17 23:55:35] - Running wine-2.7 UT2004.exe (Working directory : /home/richter/.PlayOnLinux/wineprefix/UnrealT2004/drive_c/Program Files/Unreal Tournament 2004/System) err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142 fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32e540,0x32e53c): stub fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:create_server class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject no class object {96749377-3391-11d2-9ee3-00c04f797396} could be created for context 0x7 fixme:win:EnumDisplayDevicesW ((null),0,0x32bc98,0x00000000), stub! fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:imm:ImmReleaseContext (0x1007c, 0x2165e0): stub fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x6404c88, 0x32ccc4 err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1042267284)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1082643741)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129305379)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1017464658)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106373278)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1061644189)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103102115)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102202262)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127878391)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1133393126)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064431753)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056334452)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103590910)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1128011843)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1012511863)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129177136)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064579615)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107545964)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127492263)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1131588260)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1009667614)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064940315)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102388947)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107645235)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127352012)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106599611)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065065837)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056114040)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1104285584)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127422744)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1029644321)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1126051816)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065075311)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". intel_do_flush_locked failed: Cannot allocate memory ``` -- 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 55273] New: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55273 Bug ID: 55273 Summary: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709: wow64.c:783: Test failed: 0:0: wrong offset 4 wow64.c:783: Test failed: 0:1: wrong offset 6 wow64.c:783: Test failed: 0:2: wrong offset 4 wow64.c:783: Test failed: 0:3: wrong offset 6 wow64.c:783: Test failed: 0:4: wrong offset 4 wow64.c:783: Test failed: 0:5: wrong offset 6 wow64.c:783: Test failed: 0:6: wrong offset 4 wow64.c:783: Test failed: 0:7: wrong offset 6 wow64.c:783: Test failed: 1:0: wrong offset 16 wow64.c:783: Test failed: 1:1: wrong offset 14 wow64.c:783: Test failed: 1:2: wrong offset 12 wow64.c:783: Test failed: 1:3: wrong offset 10 wow64.c:783: Test failed: 1:4: wrong offset 8 wow64.c:783: Test failed: 1:5: wrong offset 6 wow64.c:783: Test failed: 1:6: wrong offset 4 wow64.c:783: Test failed: 1:7: wrong offset 18 wow64.c:783: Test failed: 2:0: wrong offset 8 wow64.c:783: Test failed: 2:1: wrong offset 6 wow64.c:783: Test failed: 2:2: wrong offset 4 wow64.c:783: Test failed: 2:3: wrong offset 10 wow64.c:783: Test failed: 2:4: wrong offset 8 wow64.c:783: Test failed: 2:5: wrong offset 6 wow64.c:783: Test failed: 2:6: wrong offset 4 wow64.c:783: Test failed: 2:7: wrong offset 10 wow64.c:783: Test failed: 3:0: wrong offset 16 wow64.c:783: Test failed: 3:1: wrong offset 14 wow64.c:783: Test failed: 3:2: wrong offset 12 wow64.c:783: Test failed: 3:3: wrong offset 10 wow64.c:783: Test failed: 3:4: wrong offset 8 wow64.c:783: Test failed: 3:5: wrong offset 6 wow64.c:783: Test failed: 3:6: wrong offset 4 wow64.c:783: Test failed: 3:7: wrong offset 18 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The failures started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 so in this case it is just a coincidence. See also bug 55272 for ntdll:exception crashes that started at the same time on the same set of machines. -- 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 55211] New: Print file not truncated when printing to file in FrameMaker 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55211 Bug ID: 55211 Summary: Print file not truncated when printing to file in FrameMaker 8 Product: Wine Version: 8.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- A existing print file ist not truncated when printing to the same file again. So when printing a smaller document to the print file which was generated for a larger file, the resultung file contains garbage at its end. This happens in Framemaker 8 and may happen in other apps too. To reproduce - Install Framemaker from the given URL - Print the attached Document Large.fm to a file (select print to file in the printer dialog). Check the size of the generated file. - Print the attached Document Small.fm to the same file generated in the previous step. Check again the size of the file - its the same. Depending on the used Postscript interpreter reading the file fails because of the garbage at the files end. This is simple to see when using different documents as descibed above. When printing existing documents again after (even small) changes the resulting print file may be garbage without notice. -- 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 13

[Bug 43185] New: "Battle Bugs" game in unresponsive once game starts
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43185 Bug ID: 43185 Summary: "Battle Bugs" game in unresponsive once game starts Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matt(a)nightrealms.com Distribution: --- Created attachment 58457 --> https://bugs.winehq.org/attachment.cgi?id=58457 Wine output from before starting the game When playing the free game "Battle Bugs" (https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game start screen loads just fine, and pressing an indicated key starts the game just fine, but once the game starts nothing is moving and the game doesn't respond to any keys. Got the same results with both versions of the executable, and both WINEARCH unspecified or set to win32 -- 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 55236] New: scrrun:dictionary - test_hash_value() gets bad hashes on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55236 Bug ID: 55236 Summary: scrrun:dictionary - test_hash_value() gets bad hashes on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com scrrun:dictionary - test_hash_value() gets bad hashes on Windows: dictionary.c:676: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:686: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:695: Test failed: got hash 0x2db, expected 0x2da dictionary.c:721: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:732: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:742: Test failed: got hash 0x2db, expected 0x2da See https://test.winehq.org/data/patterns.html#scrrun:dictionary Note that the hash values change with every run causing false positives. -- 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 54791] New: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54791 Bug ID: 54791 Summary: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7. This can either be a single event but it can also happen multiple times for multiple events: nstc.c:2265: Test failed: Got event 4, count 1 or nstc.c:1906: Test failed: Got event 7, count 0 nstc.c:1908: Test failed: Got event 4, count 0 nstc.c:1912: Test failed: Got event 4, count 1 nstc.c:1912: Test failed: Got event 7, count 1 nstc.c:1912: Test failed: Got event 12, count 8 See https://test.winehq.org/data/patterns.html#explorerframe:nstc This first happened on 2022-12-07 and has been happening roughly once every three week since. So it's probably caused by a commit in the fall of 2022. -- 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 3

[Bug 54441] New: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54441 Bug ID: 54441 Summary: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10: speech.c:1775: Test failed: recog_state was 0. See https://test.winehq.org/data/patterns.html#windows.media.speech:speech This failure started on 2023-01-25. -- 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 9

[Bug 54156] New: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54156 Bug ID: 54156 Summary: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:edit - test_paste() sometimes gets an empty string on Windows edit.c:3238: Test failed: got 0 See https://test.winehq.org/data/patterns.html#comctl32:edit This happens on Windows 10 1809 to 21H2 a bit less than 3 times per month. Where 0 is the length of the string in the field we pasted to. So that field is empty instead of having received the string we pasted. We can also get this failure in user32:edit (2022-11-15 w10pro64v1809): edit.c:3211: Test failed: got 0 See https://test.winehq.org/data/patterns.html#user32:edit But the case above is for the single-line to single-line case and there is also the same issue happening in the multi-line to multi-line case (2022-10-25 w11pro64-amd): edit.c:3240: Test failed: got 0 So it's a pretty general, if rare (only 4 known instances in 6 months), problem. Note that while one could expect this to be caused by yet another OpenClipboard() failure, like in bug 53276, there is no failure message indicating this to be the case. -- 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 3

[Bug 53276] New: user32:edit - test_paste() sometimes fails to access the clipboard on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=53276 Bug ID: 53276 Summary: user32:edit - test_paste() sometimes fails to access the clipboard on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:edit - test_paste() sometimes fails to access the clipboard on Windows: edit.c:3222: Test failed: expected 1, got 0 le=5 edit.c:3224: Test failed: expected 1, got 0 edit.c:3226: Test failed: expected 00000000008500A8, got 0000000000000000 edit.c:3228: Test failed: expected 1, got 0 edit.c:3234: Test failed: got 21 edit.c:3240: Test failed: got 21 https://test.winehq.org/data/patterns.html#user32:edit Where 5 is ERROR_ACCESS_DENIED and indicates that the clipboard has already been opened in another thread, process, etc. This happens a lot on machines with an AMD GPU due to known interference from the Radeon driver (see bug 47888). But it also happens sometimes on machines with an Nvidia GPU (cw-gtx560) and even on pure QEmu VMs such as w1064-1qxl (or fgtb-w10pro64). So there is either some other source of interference, maybe from some Windows component, or an issue (a race condition?) in the test itself. It would be nice to identify the source of interference, if any, to see if it can be neutralized. But maybe the only solution is to work around the issue as in user32:clipboard (see commit 316eec8f6658). -- 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 5

[Bug 55272] New: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55272 Bug ID: 55272 Summary: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709: exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 ntdll:exception:0dd8 done (-1073741819) in 0s 6581B See https://test.winehq.org/data/patterns.html#ntdll:exception Where -1073741819 == 0xC0000005 == STATUS_ACCESS_VIOLATION The crashes started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 in this case it is just a coincidence. Note that before that ntdll:exception was exiting silently on Windows 8 & 10 <= 1809, see bug 55111. These two issues may be one and the same, just producing different results due to changes in the binary layout. -- 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 3

[Bug 55108] New: xaudio2_8:xaudio2 fails on Windows 10+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55108 Bug ID: 55108 Summary: xaudio2_8:xaudio2 fails on Windows 10+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com xaudio2_8:xaudio2 fails on Windows 10+: xaudio2.c:1218: Test failed: Got hr 0x80004002. See https://test.winehq.org/data/patterns.html#xaudio2_8:xaudio2 Note that this is the same failure as what happened on Windows 8 in the late stages described in bug 55016. A bisect shows that this failure started with the commit below: commit e8b0e7c1fcf090ba80c543f68b0bdae185316327 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Fri Jun 16 15:13:14 2023 -0500 xaudio2/tests: Fix the IID_IXAudio28 declaration. This was accidentally copied from the 2.9 version instead in 14c44d0b0. -- 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 5

[Bug 54699] New: Motorola Ready For Assistant does not start, RoOriginateLanguageException in Windows.Networking
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54699 Bug ID: 54699 Summary: Motorola Ready For Assistant does not start, RoOriginateLanguageException in Windows.Networking Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lischak(a)gmail.com Distribution: --- Created attachment 74209 --> https://bugs.winehq.org/attachment.cgi?id=74209 install+run of v04.0.0.010.000 on Wine 8.4 Motorola Ready For Assistant is a software for interfacing with Motorola smartphones from desktop, allowing either phone screen mirror or a full-sized Android-powered desktop similar to Samsung DeX. The installer appears to finish successfully, but the application will not start. This is a continuation of Bug 54495 in which two previous issues were fixed (thanks!). The installation file is freely downloadable: https://web.archive.org/web/20230214220515/https://download.lenovo.com/leno… cd ~/Downloads WINEPREFIX=~/.wine_readyfor wine ReadyFor_setup_04.0.0.010.000.exe cd ~/.wine_readyfor/drive_c/Program\ Files/Lenovo/Ready\ For\ Assistant WINEPREFIX=~/.wine_readyfor wine ReadyFor.exe Attaching log from installation and from a follow-up run. Env: Fedora 37, using the appropriate official WineHQ repo. Note: The software is apparently only available via MS Store nowadays, but the Store install just downloads a normal Win32 .exe from Motorola/Lenovo's servers in the background. -- 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 12

[Bug 52641] New: dsdmo has missing implementation causing game crash on loaded
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=52641 Bug ID: 52641 Summary: dsdmo has missing implementation causing game crash on loaded Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- log has shown a missing implementation on dsdmo dll this cause game crash when loading Affect game: Feeding Frenzy 2 Log: 0290:warn:dsdmo:effect_inner_QueryInterface {6d6cbb60-a223-44aa-842f-a2f06750be6d} not implemented; returning E_NOINTERFACE. -- 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 41645] New: recursive invokation of __clone+0x6d() in libc.so.6 ( 0x00000000) in start_thread+0xe4() in libpthread.so.0 (0x0608f428)
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=41645 Bug ID: 41645 Summary: recursive invokation of __clone+0x6d() in libc.so.6 (0x00000000) in start_thread+0xe4() in libpthread.so.0 (0x0608f428) Product: Wine Version: 1.9.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Created attachment 56020 --> https://bugs.winehq.org/attachment.cgi?id=56020 Backtrace created by wine crash handler There seems to be a recursive invokation inside `__clone+0x6d()` in `start_thread+0xe4() in libpthread.so.0 (0x0608f428)`, see attached backtrace. -- 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 55245] New: ntdll:om - The 32-bit test_all_kernel_objects() gets an access violation on the w8 VM
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55245 Bug ID: 55245 Summary: ntdll:om - The 32-bit test_all_kernel_objects() gets an access violation on the w8 VM Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:om - The 32-bit test_all_kernel_objects() gets an access violation on Windows 8: om.c:553: Test failed: 751: NtCreateSymbolicLinkObject failed c0000005 om.c:565: Test failed: 751: NtCreateSymbolicLinkObject failed c0000005 om.c:553: Test failed: 752: NtCreateSymbolicLinkObject failed c0000005 om.c:565: Test failed: 752: NtCreateSymbolicLinkObject failed c0000005 See https://test.winehq.org/data/patterns.html#ntdll:om Where c0000005 == STATUS_ACCESS_VIOLATION This started on 2023-07-10 which corresponds to the GitLab CI switch to Debian 12 for builds which means it is caused by the commit below: commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Jul 10 17:18:49 2023 +0200 gitlab: Upgrade the Debian image to bookworm. However unlike other failures related to that switch, this one only happens on the 32-bit Windows 8 VM, aka w8. So running the same 32-bit binary on the 64-bit Windows 8 VM, aka w864, produces no failure. -- 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 3

[Bug 54783] New: cryptowinrt:crypto - test_Credentials_Statics() sometimes gets unexpectedly high refcount in Wine
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54783 Bug ID: 54783 Summary: cryptowinrt:crypto - test_Credentials_Statics() sometimes gets unexpectedly high refcount in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- cryptowinrt:crypto - test_Credentials_Statics() sometimes gets unexpectedly high refcount in Wine: crypto.c:321: Test failed: got ref 3. crypto.c:323: Test failed: got ref 2. See https://test.winehq.org/data/patterns.html#cryptowinrt:crypto Where 2 and 1 was expected respectively. There are 4 known instances so far but this test has only been running since 2023-02-23: * 2023-02-27 on MR2262 * 2023-03-15 on fg-deb64-wow64 * 2023-03-23 on fg-deb64-wow32 * 2023-04-04 on MR2576 -- 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 54430] New: user32:menu - test_menu_input()'s test 0 sometimes fails on Windows 7
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54430 Bug ID: 54430 Summary: user32:menu - test_menu_input()'s test 0 sometimes fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:menu - test_menu_input()'s test 0 fails randomly on Windows 7: menu.c:2324: Test failed: test 0 See https://test.winehq.org/data/patterns.html#user32:menu This failure started on 2023-01-24 (no instance in the previous 5.5 months) and only happens in about 20% of the WineTest runs. This happened in English (w7u-2qxl, dual screen) and in the other Windows 7 locales (de, el, es, pt-PT). So it does not seem to be related to the locale. -- 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 3

[Bug 54420] New: preloader warning "failed to reserve range" macOS Ventura
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54420 Bug ID: 54420 Summary: preloader warning "failed to reserve range" macOS Ventura Product: Wine Version: 8.0 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gcenx83(a)gmail.com CC: bshanks(a)codeweavers.com The usual Apple made changes that affects macOS Ventura preloader: Warning: failed to reserve range 0000000000010000-0000000000110000 -- 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 44275] New: Shadow of Memories demo hangs at graphic setting screen
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=44275 Bug ID: 44275 Summary: Shadow of Memories demo hangs at graphic setting screen Product: Wine Version: 3.0-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: --- Created attachment 60097 --> https://bugs.winehq.org/attachment.cgi?id=60097 Default Wine log from launch to graphic setting screen hang Clicking on the Graphic Setting button on the main menu brings up the screen. Game stops responding shortly thereafter. If you're quick enough you can move the mouse cursor a bit and change button focus on the screen before it hangs. a.k.a. Shadow of Destiny Install notes (demo download link on same page): https://appdb.winehq.org/objectManager.php?sClass=version&iId=31628#notes -- 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 12

[Bug 32574] New: Patrician 4 fails to start (Error in 'App::Initialize')
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

http://bugs.winehq.org/show_bug.cgi?id=32574 Bug #: 32574 Summary: Patrician 4 fails to start (Error in 'App::Initialize') Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 42991 --> http://bugs.winehq.org/attachment.cgi?id=42991 plain terminal output Both the Steam and Gamersgate versions of the game have this bug. Only the base game is affected, the expansion (Patrician 4: Rise of a Dynasty) which requires the base game to be installed, doesn't have the problem. After starting the game with Patrician4.exe, an error message is shown: "D:\GMProjects\Patrician3\App\App.cpp(732): Error in 'App::Initialize' . . Installation corrupt: 2:0xffffffff" This error message comes up in this forum thread @Kalypso: http://forum.kalypsomedia.com/showthread.php?tid=11896&pid=113448#pid113448 The answer was that the user had to update root certificates in Windows XP. A +loaddll log reveals that crypt32.dll and wintrust.dll are indeed loaded when I start the game. Appdata.dll in the installed game directory contains a certification (the file properties dialog under Windows shows it). I wonder if a +crypt or +wintrust debug log would be of any help. The game should start with a launcher asking you for registering the game @Kalypso. I tried with native crypt32 and received a crash along with a backtrace somewhere in Wine's wintrust component. -- 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 16

[Bug 48905] New: Inner Chains Launches to Black Screen With Mouse Cursor
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=48905 Bug ID: 48905 Summary: Inner Chains Launches to Black Screen With Mouse Cursor Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matthewcboyd(a)tutanota.com Distribution: --- Created attachment 66859 --> https://bugs.winehq.org/attachment.cgi?id=66859 Debugging Log When I try to launch the game it only launches to a black screen with a mouse cursor. I have tried this on a Windows 10 system where it launches without issue. I've attached pictures of the issue and the terminal output. I am using the GOG version 2.2 of the game. My system: AMD Ryzen 5 2600X | 16GB DDR4-3000 CL15 | MSI RX 5700 XT 8GB Gaming X | Mesa 20.0.4 | Manjaro 19.0.2 | Mate 1.24 | Kernel 5.6.2-1-MANJARO | Wine 5.5 Windows System: AMD FX-9590 | 16GB DDR3-2133 | MSI RX 580 8GB Gaming X | Driver 20.2.2 | Windows 10 Pro 1909 -- 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 3

[Bug 48075] New: Star Wars Battlefront 2 (from 2017) does not start/run properly.
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=48075 Bug ID: 48075 Summary: Star Wars Battlefront 2 (from 2017) does not start/run properly. Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skybuck2000(a)hotmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Sparky Linux Game Over edition was used on Toshiba Laptop L670 to try and start Star Wars Battlefront 2 from 2017, game does not start/run properly (Lutris was used) I suspect wine issue. Big log, small logs and json system information file are available at the folder web folder: http://www.skybuck.org/Games/Battlefront2/Lutris/ Small log example: Running /usr/bin/wine /media/skybuck/06FAAE82FAAE6E1D/Games/Star Wars - Battlefront 2/starwarsbattlefrontii.exe 000b:fixme:winediag:start_process Wine Staging 4.19 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 002a:fixme:ver:GetCurrentPackageId (0x22d9f0 (nil)): stub 002a:fixme:ntdll:NtQuerySystemInformation returning fake driver list 002a:fixme:heap:RtlSetHeapInformation 0xb50000 0 0x22d8a0 4 stub Waiting on children All children gone Exit with returncode 91 System information: { "comment": "Star Wars Battlefront 2 from 2017 does not start.", "system": { "gpus": [ { "DRIVER": "radeon", "PCI_ID": "1002:68C1", "PCI_SUBSYS_ID": "1179:FD00", "PCI_CLASS": "30000", "PCI_SLOT_NAME": "0000:01:00.0", "MODALIAS": "pci:v00001002d000068C1sv00001179sd0000FD00bc03sc00i00" } ], "env": { "USER": "skybuck", "LC_TIME": "nl_NL.UTF-8", "XDG_SEAT": "seat0", "XDG_SESSION_TYPE": "x11", "SSH_AGENT_PID": "1019", "HOME": "/home/skybuck", "DESKTOP_SESSION": "xfce", "XDG_SEAT_PATH": "/org/freedesktop/DisplayManager/Seat0", "LC_MONETARY": "nl_NL.UTF-8", "DBUS_SESSION_BUS_ADDRESS": "unix:path=/run/user/1000/bus", "QT_QPA_PLATFORMTHEME": "gtk2", "LOGNAME": "skybuck", "XDG_SESSION_CLASS": "user", "XDG_SESSION_ID": "1", "PATH": "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games", "LC_ADDRESS": "nl_NL.UTF-8", "XDG_SESSION_PATH": "/org/freedesktop/DisplayManager/Session0", "XDG_RUNTIME_DIR": "/run/user/1000", "XDG_MENU_PREFIX": "xfce-", "LC_TELEPHONE": "nl_NL.UTF-8", "LANG": "en_US.UTF-8", "XDG_CURRENT_DESKTOP": "XFCE", "XDG_SESSION_DESKTOP": "xfce", "XAUTHORITY": "/home/skybuck/.Xauthority", "XDG_GREETER_DATA_DIR": "/var/lib/lightdm/data/skybuck", "SSH_AUTH_SOCK": "/tmp/ssh-HKhz6gKNBr4H/agent.990", "SHELL": "/bin/bash", "LC_NAME": "nl_NL.UTF-8", "GDMSESSION": "xfce", "QT_ACCESSIBILITY": "1", "LC_MEASUREMENT": "nl_NL.UTF-8", "LC_IDENTIFICATION": "nl_NL.UTF-8", "XDG_VTNR": "7", "PWD": "/home/skybuck", "XDG_DATA_DIRS": "/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share", "XDG_CONFIG_DIRS": "/etc/xdg", "LC_NUMERIC": "nl_NL.UTF-8", "LC_PAPER": "nl_NL.UTF-8", "SESSION_MANAGER": "local/USBStick:@/tmp/.ICE-unix/990,unix/USBStick:/tmp/.ICE-unix/990", "PANEL_GDK_CORE_DEVICE_EVENTS": "0", "DISPLAY": ":0.0" }, "missing_libs": { "OPENGL": [ [], [] ], "VULKAN": [ [], [] ], "WINE": [ [], [] ], "GAMEMODE": [ [ "libgamemodeauto.so" ], [ "libgamemodeauto.so" ] ] }, "cpus": [ { "processor": "0", "vendor_id": "GenuineIntel", "cpu family": "6", "model": "37", "model name": "Intel(R) Core(TM) i5 CPU M 480 @ 2.67GHz", "stepping": "5", "microcode": "0x7", "cpu MHz": "1331.143", "cache size": "3072 KB", "physical id": "0", "siblings": "4", "core id": "0", "cpu cores": "2", "apicid": "0", "initial apicid": "0", "fpu": "yes", "fpu_exception": "yes", "cpuid level": "11", "wp": "yes", "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d", "bugs": "cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs", "bogomips": "5319.37", "clflush size": "64", "cache_alignment": "64", "address sizes": "36 bits physical, 48 bits virtual", "power management": "" }, { "processor": "1", "vendor_id": "GenuineIntel", "cpu family": "6", "model": "37", "model name": "Intel(R) Core(TM) i5 CPU M 480 @ 2.67GHz", "stepping": "5", "microcode": "0x7", "cpu MHz": "1357.986", "cache size": "3072 KB", "physical id": "0", "siblings": "4", "core id": "0", "cpu cores": "2", "apicid": "1", "initial apicid": "1", "fpu": "yes", "fpu_exception": "yes", "cpuid level": "11", "wp": "yes", "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d", "bugs": "cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs", "bogomips": "5319.37", "clflush size": "64", "cache_alignment": "64", "address sizes": "36 bits physical, 48 bits virtual", "power management": "" }, { "processor": "2", "vendor_id": "GenuineIntel", "cpu family": "6", "model": "37", "model name": "Intel(R) Core(TM) i5 CPU M 480 @ 2.67GHz", "stepping": "5", "microcode": "0x7", "cpu MHz": "1420.642", "cache size": "3072 KB", "physical id": "0", "siblings": "4", "core id": "2", "cpu cores": "2", "apicid": "4", "initial apicid": "4", "fpu": "yes", "fpu_exception": "yes", "cpuid level": "11", "wp": "yes", "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d", "bugs": "cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs", "bogomips": "5319.37", "clflush size": "64", "cache_alignment": "64", "address sizes": "36 bits physical, 48 bits virtual", "power management": "" }, { "processor": "3", "vendor_id": "GenuineIntel", "cpu family": "6", "model": "37", "model name": "Intel(R) Core(TM) i5 CPU M 480 @ 2.67GHz", "stepping": "5", "microcode": "0x7", "cpu MHz": "1294.931", "cache size": "3072 KB", "physical id": "0", "siblings": "4", "core id": "2", "cpu cores": "2", "apicid": "5", "initial apicid": "5", "fpu": "yes", "fpu_exception": "yes", "cpuid level": "11", "wp": "yes", "flags": "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d", "bugs": "cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs", "bogomips": "5319.37", "clflush size": "64", "cache_alignment": "64", "address sizes": "36 bits physical, 48 bits virtual", "power management": "" } ], "drives": [ { "name": "sda", "fstype": null, "label": null, "uuid": null, "fsavail": null, "fsuse%": null, "mountpoint": null, "children": [ { "name": "sda1", "fstype": "ntfs", "label": "Door systeem gereserveerd", "uuid": "D28AAA208AAA00D9", "fsavail": null, "fsuse%": null, "mountpoint": null }, { "name": "sda2", "fstype": "ntfs", "label": null, "uuid": "06FAAE82FAAE6E1D", "fsavail": "89G", "fsuse%": "81%", "mountpoint": "/media/skybuck/06FAAE82FAAE6E1D" } ] }, { "name": "sdb", "fstype": null, "label": null, "uuid": null, "fsavail": null, "fsuse%": null, "mountpoint": null, "children": [ { "name": "sdb1", "fstype": "vfat", "label": "EFI", "uuid": "67E3-17ED", "fsavail": null, "fsuse%": null, "mountpoint": null }, { "name": "sdb2", "fstype": "ntfs", "label": "External Harddisk", "uuid": "CEF0ABAFF0AB9BE9", "fsavail": "4,3T", "fsuse%": "7%", "mountpoint": "/media/skybuck/External Harddisk" } ] }, { "name": "sdc", "fstype": null, "label": null, "uuid": null, "fsavail": null, "fsuse%": null, "mountpoint": null, "children": [ { "name": "sdc1", "fstype": "vfat", "label": "SPARKY_64BI", "uuid": "14F4-2A56", "fsavail": null, "fsuse%": null, "mountpoint": null }, { "name": "sdc2", "fstype": "ext4", "label": null, "uuid": "edcc9ade-a815-4f64-94d2-78c76807811a", "fsavail": "53,8G", "fsuse%": "25%", "mountpoint": "/" }, { "name": "sdc3", "fstype": "swap", "label": null, "uuid": "35732adc-28a3-4566-8db4-6e9b5283995a", "fsavail": null, "fsuse%": null, "mountpoint": "[SWAP]" } ] }, { "name": "sr0", "fstype": null, "label": null, "uuid": null, "fsavail": null, "fsuse%": null, "mountpoint": null } ], "ram": { "mem": { "total": "5960292", "used": "667784", "free": "460444", "shared": "54064", "buff/cache": "4832064", "available": "4941232" }, "swap": { "total": "33555024", "used": "0", "free": "33555024" } }, "dist": [ "SparkyLinux", "6", "Po-Tolo" ], "glxinfo": { "name_of_display": ":0.0", "opengl_core_profile_version": "3.3 (Core Profile) Mesa 19.2.1", "opengl_core_profile_context_flags": "(none)", "display": ":0", "opengl_shading_language_version": "1.40", "opengl_core_profile_profile_mask": "core profile", "opengl_es_profile_shading_language_version": "OpenGL ES GLSL ES 3.10", "direct_rendering": "Yes", "opengl_renderer": "AMD REDWOOD (DRM 2.50.0 / 5.2.0-3-amd64, LLVM 9.0.0)", "opengl_version": "3.1 Mesa 19.2.1", "opengl_context_flags": "(none)", "opengl_vendor": "X.Org", "opengl_core_profile_shading_language_version": "3.30", "opengl_es_profile_version": "OpenGL ES 3.1 Mesa 19.2.1", "screen": "0" } } } Is there anything I can do to make it work a bit better ? Perhaps update something ? Try different drivers ? Problem seems to be the "fixme" issues. -- 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 12

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 August 2023