wine-bugs

wine-bugs@winehq.org

1 participants
158725 discussions

[Bug 52103] New: Crazy Stone has been working on Wine for years but now crashes following update
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52103 Bug ID: 52103 Summary: Crazy Stone has been working on Wine for years but now crashes following update Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gerry(a)gavigan.me.uk Distribution: --- Created attachment 71125 --> https://bugs.winehq.org/attachment.cgi?id=71125 backtrace generated by Wine After splash screen Crazy Stone crashes. I have been using Crazy Stone under Wine for about five years without problem. Today, on Tumbleweed, after an update. -- 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 44

[Bug 52093] New: malloc() after installing Insta360 pro stitcher (incl. wine config)
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52093 Bug ID: 52093 Summary: malloc() after installing Insta360 pro stitcher (incl. wine config) Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wwjdtd(a)gmail.com Distribution: --- To reproduce: 1. Download Insta360 STITCHER from here: https://www.insta360.com/download/insta360-pro2 Note: You will want to use the href link since it will otherwise ask for a serial number. 2. Run Installer 3. Close all wine programs 4. Try to run anything in wine or the wine config tool (or any other built-in). You will receive the following: ``` malloc(): invalid size (unsorted) Aborted (core dumped) ``` Copying the program files out and into a fresh wineprefix allows the program to run properly and does not corrupt the new prefix. All testing was done in bottles (to prevent stuff breaking from misconfiguration on my part) with `winehq-devel`. Versions effected is everything from somewhere above 6.0 to 6.22, this also means it's some form of regression since it didn't do this previously. Forum post: https://forum.winehq.org/viewtopic.php?f=8&t=35914&p=135171#p135140 -- 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 52072] New: winmm:mci fails in wow64 Wine
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52072 Bug ID: 52072 Summary: winmm:mci fails in wow64 Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- winmm:mci started failing in wow64 Wine on 2021-11-11. It now has 51 failures: mci.c:248: Test failed: status 4(mode): MCIERR_UNSUPPORTED_FUNCTION mci.c:328: Test failed: status mode: MCIERR_UNSUPPORTED_FUNCTION mci.c:656: Test marked todo: mci info new file returned 0=NOERROR mci.c:660: Test marked todo: status x length initial: MCIERR_UNSUPPORTED_FUNCTION mci.c:665: Test failed: mci status samplespersec returned MCIERR_UNSUPPORTED_FUNCTION mci.c:732: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:781: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:812: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:827: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:848: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:849: Test failed: mci status mode: after play from 0 to 0 mci.c:860: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:903: Test failed: mci status position notify returned MCIERR_UNSUPPORTED_FUNCTION mci.c:906: Test failed: Expect message 0001 from status position mci.c:909: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:910: Test failed: mci status mode: mci.c:915: Test marked todo: Expect message 0001 from play to 250 wait notify mci.c:955: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:956: Test failed: mci status mode: mci.c:974: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:975: position after Sleep: ms [...] https://test.winehq.org/data/patterns.html#winmm:mci Note that besides the test failures the "mci status mode: " and "position after Sleep: ms" messages are suspicious. All four Linux test machines are impacted by this: the failure test pattern makes it obvious for cw-gtx560, cw-rx460 and the TestBot's debiant2 VM. fg-deb64 is impacted as well but it is masked by the preexisting timeout. Strangely a bisect shows that these failures started with this commit: commit 7c5761ed40f0b8cead7fa837b745b687d5df67d8 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Nov 11 16:21:00 2021 +0100 wrc: Ignore the target option. Nothing in resource files depends on the pointer size. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52068] New: hid:device times out randomly in test_get_input_report()
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52068 Bug ID: 52068 Summary: hid:device times out randomly in test_get_input_report() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- hid:device times out randomly (>10% of the time) in test_get_input_report(): device.c:406: HidD_GetInputRpeort tests on device :L"Wine HID mouse" hid:device:05cc done (258) in 120s https://test.winehq.org/data/patterns.html#hid:device So far this only happened in the pure 32-bit builds but it does impact various machines (cw-gtx560, cw-rx460, some debiant2 configurations and fg-deb64). A bisect shows that the timeouts started with this commit: commit fca0f18d0857d6aee67c6ef652c31c6810292270 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Fri Nov 19 09:39:39 2021 +0100 winebus.sys: Avoid unnecessary scaling of effect parameter values. Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52023] New: VirtualFree returning error when it should not
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52023 Bug ID: 52023 Summary: VirtualFree returning error when it should not Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: elpochodelagente(a)gmail.com Distribution: --- Created attachment 71022 --> https://bugs.winehq.org/attachment.cgi?id=71022 test case source and exe I find it odd that Wine's version of VirtualFree [1] with MEM_DECOMMIT does nothing, and always returns error (STATUS_NO_MEMORY, see decommit_pages and anon_map_fixed in dlls/ntdll/unix/virtual.c). The attached test passes, (crashing) in windows but doesn't in wine: $ x86_64-w64-mingw32-gcc -o decommit.exe decommit.c Windows: $ ./decommit.exe ====== test 1 - reserve, commit, release > success! ====== test 2 - reserve, commit, decommit, attempt use > Segmentation fault Wine: $ wine decommit.exe ====== test 1 - reserve, commit, release > success! ====== test 2 - reserve, commit, decommit, attempt use > Could not decommit memory. Error code: 8 ====== [1] https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-v… -- 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 51895] New: ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51895 Bug ID: 51895 Summary: ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ucrtbase Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines: misc.c:799: Test failed: fma(inf, 0.000000, 0.000000) got errno -1 misc.c:799: Test failed: fma(0.000000, inf, 0.000000) got errno -1 misc.c:799: Test failed: fma(inf, 1.000000, -inf) got errno -1 misc.c:799: Test failed: fma(-inf, 1.000000, inf) got errno -1 misc.c:799: Test failed: fma(1.000000, inf, -inf) got errno -1 misc.c:799: Test failed: fma(1.000000, -inf, inf) got errno -1 https://test.winehq.org/data/patterns.html#ucrtbase:misc Additional tests seem to indicate this is related to the CPU features: * The test succeeds on all TestBot VMs, and they also all return _get_FMA3_enabled() = 0. * The test fails on fgtb-w10pro64 (i7-4790K) where _get_FMA3_enabled() returns 1. * Paul Gofman reported getting this failure on a modern AMD processor where _get_FMA3_enabled() presumably returns 1 too. Yet: * The documentation says _get_FMA3_enabled() is about transcendental functions. fma() is not one of them. * _get_FMA3_enabled() is only available in 64-bit code but the failures happen on both 32- and 64-bit code. So it does look like this is related to the fma() implementation (x87/SSE2/other?) picked by the ucrtbase library as opposed to library version issues. But the details are murky and there may be some other common factor. The MSDN documentation does say that fma(inf,0,0) should return NaN, which it does. The documentation is less clear on errno which is what we test. https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/fma-fmaf-f… So maybe applications cannot rely on errno being set (particularly on modern processors) and this particular test should be removed. -- 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 51624] New: TETRIS (16bit) shows wrong background for scoreboard
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51624 Bug ID: 51624 Summary: TETRIS (16bit) shows wrong background for scoreboard Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: NEW Severity: trivial Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 70480 --> https://bugs.winehq.org/attachment.cgi?id=70480 Screenshot showing the issue Follow up to bug 51570. The graphics of the game almost work now, but the scoreboard to the left has the wrong 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 9

[Bug 32991] New: ARM port of "WabbitEMU" crashes due to unimplemented function KERNEL32.dll.RtlUnwindEx (no ntdll forward on arch=arm)
by wine-bugs＠winehq.org 03 Dec '21

03 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=32991 Bug #: 32991 Summary: ARM port of "WabbitEMU" crashes due to unimplemented function KERNEL32.dll.RtlUnwindEx (no ntdll forward on arch=arm) Product: Wine Version: 1.5.24 Platform: arm OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello folks, the ARM port of "WabbitEMU", a Texas Instruments graphing calculator emulator and dev tools crashes after clicking "Browse for a ROM image" radio button in image selection dialog. Download: http://forum.xda-developers.com/showpost.php?p=37928562 (main thread: http://forum.xda-developers.com/showthread.php?t=2092348) --- snip --- $ WINEDEBUG=+tid,+seh,+relay wine ./Wabbitemu.exe ... 0024:Call user32.GetWindowTextA(00010096,40a0ebf0,00000104) ret=00439fa5 0024:Call window proc 0x40bc5f30 (hwnd=0x10096,msg=WM_GETTEXT,wp=00000104,lp=40a0ebf0) 0024:Ret window proc 0x40bc5f30 (hwnd=0x10096,msg=WM_GETTEXT,wp=00000104,lp=40a0ebf0) retval=00000000 0024:Ret user32.GetWindowTextA() retval=00000000 ret=00439fa5 0024:Call KERNEL32.GetLastError() ret=004141cf 0024:Ret KERNEL32.GetLastError() retval=00000000 ret=004141cf 0024:trace:seh:raise_exception info[0]=0047be54 0024:trace:seh:raise_exception info[1]=0047cc8e wine: Call from 0x7bc9a630 to unimplemented function KERNEL32.dll.RtlUnwindEx, aborting 0024:trace:seh:call_stack_handlers calling handler at 0x7bcb8d88 code=80000100 flags=1 0024:Call KERNEL32.UnhandledExceptionFilter(40a0e81c) ret=7bcb8df0 --- snip --- The app is importing all win32 API by name so it's the real thing :-) +module,+imports --- snip --- ... 0009:trace:module:load_dll looking for L"KERNEL32.dll" in L"Z:\\home\\linaro\\wine-apps\\wabbitemu;.;C:\\windows\\system32;C:\\windows\\system;C:\\windows;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem" 0009:trace:module:load_dll Found L"C:\\windows\\system32\\KERNEL32.dll" for L"KERNEL32.dll" at 0x7b820000, count=19 0009:warn:module:import_dll No implementation for KERNEL32.dll.RtlUnwindEx imported from L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting to 0x41820000 0009:trace:imports:import_dll --- RtlUnwindEx KERNEL32.dll.1209 = 0x41820000 0009:trace:imports:import_dll --- GetCommandLineA KERNEL32.dll.481 = 0x7b846be0 0009:trace:imports:import_dll --- RtlPcToFileHeader KERNEL32.dll.1205 = 0x7bc69188 0009:warn:module:import_dll No implementation for KERNEL32.dll.RtlLookupFunctionEntry imported from L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting to 0x41820024 0009:trace:imports:import_dll --- RtlLookupFunctionEntry KERNEL32.dll.1203 = 0x41820024 0009:trace:imports:import_dll --- GetModuleFileNameW KERNEL32.dll.634 = 0x7b86b864 ... --- snip --- It also needs KERNEL32.dll.RtlLookupFunctionEntry later. Wine forwards both to ntdll but only on arch=x86_64. It seems Windows RT exposes both API. Interestingly only the MSDN page for KERNEL32.dll.RtlLookupFunctionEntry gives a hint about this: http://msdn.microsoft.com/en-us/library/windows/desktop/ms680597%28v=vs.85%… ("ARM Definition"). Regards -- 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 23

[Bug 52077] New: Windows PC Health Check crashes on unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFeatureStateChangeNotification
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52077 Bug ID: 52077 Summary: Windows PC Health Check crashes on unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFea tureStateChangeNotification Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Steps to reproduce: 1. Run `winecfg` and set the Windows version to Windows 10. 2. Run `wine msiexec /i WindowsPCHealthCheckSetup.msi` and click through the installer. 3. When the installer finishes and the app tries to start, you will see: wine: Call from 000000007B01230E to unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFeatureStateChangeNotification, aborting $ sha256sum WindowsPCHealthCheckSetup.msi 45c82e40ed0e27db7c55e0554512631b8f175b06d9b2d2cf58db52b18f0913fa -- 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 52075] New: dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52075 Bug ID: 52075 Summary: dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore because they now need GetOverlappedResultEx() which is not available. https://test.winehq.org/data/patterns.html#dinput8:device https://test.winehq.org/data/patterns.html#dinput8:dinput https://test.winehq.org/data/patterns.html#dinput8:hid Before that the tests could run on Windows 7 and even succeeded. The call to GetOverlappedResultEx() was introduced in the commit below: commit 3f110402f6a503d7c312694092e25fc48737c980 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Wed Nov 17 11:51:48 2021 +0100 dinput8/tests: Add some HID device gain report tests. Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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