wine-bugs February 2023

wine-bugs@winehq.org

1 participants
3554 discussions

[Bug 48339] New: RadiAnt DICOM Viewer cannot export series to WMV movie
by WineHQ Bugzilla 24 Feb '23

24 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=48339 Bug ID: 48339 Summary: RadiAnt DICOM Viewer cannot export series to WMV movie Product: Wine Version: 5.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: bozkar(a)gmail.com Distribution: --- Movie export to wmv does not work under Wine 5.0~rc1-staging in RadiAnt DICOM Viewer 5.5.0 64 bit As far as I tested RadiAnt on wine it never did. Console output: 01cc:fixme:wmvcore:WMProfileManager_LoadProfileByData (0000000000C24D40)->(L"<profile version=\"589824\" storageformat=\"1\" name=\"radiant\" description=\"\"><streamconfig majortype=\"{73646976-0000-0010-8000-00AA00389B71}\" streamnumber=\"2\" streamname=\"Video Stream\"inputname=\"Video409\" bitrate=\"20000000\" bufferwindow=\"3000\" reliabletransport=\"0\" deco"... 0000000007913480) I suppose that wmv export is probably not implemented currently, at least in this profile. To reproduce: Open any example CT series in RadiAnt DICOM viewer, export series, pick "wmv", directory, and click save, nothing happens. -- 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 1

[Bug 54568] New: Trying retrieve list of WMI classes makes powershell core crash instantly
by WineHQ Bugzilla 24 Feb '23

24 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54568 Bug ID: 54568 Summary: Trying retrieve list of WMI classes makes powershell core crash instantly Product: Wine Version: 8.2 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.0.3/PowerShell-7.0.3-win-x64.msi OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Hi, trying code snippet below found on the internet (to retrieve all wmi classes) makes powershell core crash instantly. $managementClass = New-Object System.Management.ManagementClass $enumOptions = New-Object System.Management.EnumerationOptions $enumOptions.EnumerateDeep = $true $managementClass.PSBase.GetSubclasses( $enumOptions ) | Sort-Object Maybe this is not yet supported in wine, but i guess it shouldn't crash powershell anyway. (Code snippet works fine in powershell core on windows) From a debuglog: 015c:trace:wbemprox:class_object_Get 000000001FB1DB70, L"__PATH", 0, 0000000022F 1E318, 0000000022F1E548, 0000000022F1E540 015c:trace:seh:dispatch_exception code=c0000005 flags=0 addr=00000001ED48AB7F ip=1ed48ab7f 015c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised Steps to reproduce: - Save 4 lines of code above in e.g. a.ps1 - wine pwsh -f a.ps1 Output from console: Fatal error. System.AccessViolationException: Attempted to read or write protect ed memory. This is often an indication that other memory is corrupt. at System.Management.IWbemClassObjectFreeThreaded.Get_(System.String, Int32, System.Object ByRef, Int32 ByRef, Int32 ByRef) at System.Management.ManagementObject.Initialize(Boolean) at System.Management.ManagementBaseObject.get_wbemObject() at System.Management.ManagementBaseObject.get_ClassName() at System.Management.ManagementClass.GetSubclasses(System.Management.Enumerat ionOptions) at System.Management.Automation.MethodInformation.Invoke(System.Object, Syste m.Object[]) -- 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 1

[Bug 53774] New: WinZip 7
by WineHQ Bugzilla 23 Feb '23

23 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53774 Bug ID: 53774 Summary: WinZip 7 Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: blueguitar1978(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- WinZip 7: crashes when extracting a zip archive -- 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 54550] New: Move registry functions implementations into offreg.dll
by WineHQ Bugzilla 22 Feb '23

22 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54550 Bug ID: 54550 Summary: Move registry functions implementations into offreg.dll Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- https://learn.microsoft.com/en-us/windows/win32/devnotes/offline-registry-l… This is a library to work with registry files. It is not shipped with Windows, but is a part of WDK, so usually apps needing it bring one with itself. But AFAIK Wine registry format is different from Windows one. Also it'd be nice to be able to manipulate Wine registry from the apps native to the host. So it is proposed to 1. move all the impls of the registry format into a unix library `libwineoffreg.so` 2. generate `offreg.dll.so` and `offreg.dll` using `libwineoffreg.so` 3. use it from `advapi32.dll` -- 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 54558] New: dinput:device8 - test_overlapped_format() sometimes gets a permission denied on Windows
by WineHQ Bugzilla 22 Feb '23

22 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54558 Bug ID: 54558 Summary: dinput:device8 - test_overlapped_format() sometimes gets a permission denied on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:device8 - test_overlapped_format() sometimes gets a permission denied on Windows. When that happens all the tests that follow fail too which makes for a lot of failures. device8.c:347: Test failed: 0x700: Acquire returned 0x80070005 device8.c:356: Test failed: 0x700: WaitForSingleObject returned 0x102 device8.c:360: Test failed: 0x700: WaitForSingleObject returned 0x102 device8.c:364: Test failed: 0x700: GetDeviceData returned 0x8007000c device8.c:371: Test failed: 0x700: WaitForSingleObject returned 0x102 device8.c:375: Test failed: 0x700: GetDeviceData returned 0x8007000c device8.c:376: Test failed: 0x700: got count 10 ... device8.c:408: Test failed: 0x700: Acquire returned 0x80070005 ... device8.c:1972: Test failed: 0x500: Acquire returned 0x80070005 device8.c:1974: Test failed: 0x500: Acquire returned 0x80070005 device8.c:1983: Test failed: 0x500: WaitForSingleObject returned 0x102 ... device8.c:2002: Test failed: 0x500: Acquire returned 0x80070005 device8.c:2011: Test failed: 0x500: WaitForSingleObject returned 0x102 ... See https://test.winehq.org/data/patterns.html#dinput:device8 Where 0x80070005 == E_ACCESSDENIED Maybe the permission denied error happens when a previous test triggered a UAC prompt which then grabbed the keyboard and mouse to get a secure answer? In any case this has happened for a long time but since 2022-11-21 it seems to only happen on w1064v1507, w7u-adm and w7u-el. -- 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 54557] New: winmm:midi gets unexpected messages on w10pro64 (21H1)
by WineHQ Bugzilla 22 Feb '23

22 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54557 Bug ID: 54557 Summary: winmm:midi gets unexpected messages on w10pro64 (21H1) 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 winmm:midi gets unexpected messages on w10pro64 (21H1): * 2023-02-13 on w10pro64-fr (64-bit) midi.c:988: Message 3c7, wParam=2f1e410, lParam=0 from midiStreamOpen midi.c:1039: Message 320, wParam=e3006fc7, lParam=1 from midiStreamOut midi.c:1039: Test failed: bad message 320/1 from midiStreamOut, expect 3c9/65f820 midi.c:1048: Message 320, wParam=e3006fc7, lParam=1 from midiStreamClose midi.c:1048: Test failed: bad message 320/1 from midiStreamClose, expect 3c8/0 * 2023-02-20 on w10pro64-he (64-bit) midi.c:662: Message 320, wParam=e3006fc7, lParam=1 from midiStream still paused midi.c:662: Test failed: bad message 320/1 from midiStream still paused, expect 0/feedf00d midi.c:685: Message 320, wParam=e3006fc7, lParam=1 from midiStream callback midi.c:685: Test failed: bad message 320/1 from midiStream callback, expect 3ca/65f820 midi.c:686: Message 3ca, wParam=2eeb120, lParam=65f820 from midiStreamOut midi.c:686: Test failed: bad message 3ca/65f820 from midiStreamOut, expect 3c9/65f820 ... midi.c:746: Message 3c9, wParam=2eeb120, lParam=65f820 from 0 bytes recorded midi.c:746: Test failed: bad message 3c9/65f820 from 0 bytes recorded, expect 0/feedf00d * 2023-02-21 on w10pro64-hi (64-bit) midi.c:366: Message 320, wParam=e3006fc7, lParam=1 from midiOutLong unprepared midi.c:366: Test failed: bad message 320/1 from midiOutLong unprepared, expect 0/feedf00d midi.c:378: MIDIHDR flags=2 when unsent midi.c:415: Message 320, wParam=e3006fc7, lParam=1 from midiOutClose midi.c:415: Test failed: bad message 320/1 from midiOutClose, expect 3c8/0 midi.c:423: Message 3c8, wParam=2ea4810, lParam=0 from midiOutOpen WINDOW midi.c:423: Test failed: bad message 3c8/0 from midiOutOpen WINDOW, expect 0/feedf00d See https://test.winehq.org/data/patterns.html#winmm:midi These are the only known instances so far so it looks like this is caused by a change that happened in February. Where 0x320 == WM_DWMCOLORIZATIONCOLORCHANGED ??? 0x3c8 == MM_MOM_CLOSE 0x3c9 == MM_MOM_DONE 0x3ca == MM_MOM_POSITIONCB It's possible that 0x320 is the cause for all failures. If it really is WM_DWMCOLORIZATIONCOLORCHANGED then it is probably caused by some other test and thus really not related to midi. So it may make sense to add it to the spurious_message() filter. -- 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 54556] New: winmm:midi fails on w11pro64_amd and w11pro64_nv
by WineHQ Bugzilla 22 Feb '23

22 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54556 Bug ID: 54556 Summary: winmm:midi fails on w11pro64_amd and w11pro64_nv 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 winmm:midi fails on w11pro64_amd and w11pro64_nv: midi.c:1147: Found 1 MIDI OUT devices midi.c:252: Found 1 MCI sequencer devices midi.c:1155: ** Testing device 0 midi.c:285: * Microsoft GS Wavetable Synth: manufacturer=1, product=27, tech=7, support=1: 32 voices, 32 notes midi.c:304: Test failed: midiOutOpen(dev=0) rc=MMSYSERR_ERROR midi.c:620: Test failed: midiStreamOpen(dev=-2) rc=MMSYSERR_ERROR midi.c:1164: ** Testing MIDI mapper midi.c:285: * Microsoft MIDI Mapper: manufacturer=1, product=1, tech=5, support=9: 0 voices, 0 notes midi.c:304: Test failed: midiOutOpen(dev=-1) rc=MMSYSERR_ERROR midi.c:620: Test failed: midiStreamOpen(dev=-2) rc=MMSYSERR_ERROR See https://test.winehq.org/data/patterns.html#winmm:midi Where -1 == MIDIMAPPER -2 is probably udev after being modified by midiStreamOpen() This is probably because these two test configurations use the graphics card's HDMI out audio device but the 'screen' has no speaker. See bug 54523 for more details. Bug 54538 is probably the same issue too. It's still strange that midiOutGetNumDevs() returns 1 device when trying to use it does not actually work. Maybe that's a bug in the GPU drivers? -- 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 54555] New: winmm:mci sometimes crashes on exit on Windows
by WineHQ Bugzilla 22 Feb '23

22 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54555 Bug ID: 54555 Summary: winmm:mci sometimes crashes on exit on Windows 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 winmm:mci sometimes crashes on exit on Windows: 0fec:mci: 675 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. mci.c:1796: this is the last test seen before the exception 0fec:mci: unhandled exception c0000005 at 75B37660 winmm:mci:0fec done (-1073741819) in 15s 453B See https://test.winehq.org/data/patterns.html#winmm:mci The "tests executed" line indicates that the crash happened either in the test framework's main function or on process exit. The usual suspects are memory / stack corruption, threads running code from unloaded dlls, etc. There is a comment indicating that "Win9X hangs when exiting with something still open". Maybe the "close all" command it not always completely effective. The oldest known instance was on 2022-08-31 and this happened 8 times until 2022-12-07, and then twice in February 2023. It's not clear if the December and January hiatus was just pure luck or if this is caused by external interference that went away during that period. This also seems to be specific to Windows 10 2004+. -- 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 32235] New: Soldiers heroes of World War II crashes on startup
by wine-bugs＠winehq.org 22 Feb '23

22 Feb '23

http://bugs.winehq.org/show_bug.cgi?id=32235 Bug #: 32235 Summary: Soldiers heroes of World War II crashes on startup Product: Wine Version: 1.5.16 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: paulthetall(a)gmail.com Classification: Unclassified Created attachment 42522 --> http://bugs.winehq.org/attachment.cgi?id=42522 Crash log Soldiers Heroes of World War 2 crash on startup see crash log. It says a out of memory notification, so maybe a memory leak or something? I use the GOG.com version in this test. Hope you guys can ind out what is going on. If you need andy extra debug extensions let me know so I can provide it. Many thanks in advance! -- 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 40

[Bug 54548] New: eMule 0.51d: everything seems to work fine, but after a while (minutes, hours) the program crashes with Wine 8.0 (stable).
by WineHQ Bugzilla 21 Feb '23

21 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54548 Bug ID: 54548 Summary: eMule 0.51d: everything seems to work fine, but after a while (minutes, hours) the program crashes with Wine 8.0 (stable). Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lupuseh(a)hotmail.es Distribution: --- Created attachment 74088 --> https://bugs.winehq.org/attachment.cgi?id=74088 A recent backtrace I have been using eMule 0.51d correctly for years with Wine versions lower than 8.0, but with the upgrade to Wine 8.0 in Ubuntu 22.04.1 it stopped working correctly. With Wine 8.0, eMule seems to work correctly until it crashes, leaving the screen with black areas (without refreshing) and the only solution I find is to kill the process with "kill -9 [PID_of_eMule]". I have been testing also the latest version of eMule (0.60d) in a new WINEPREFIX, but with the same results. My system info: Ubuntu 22.04.2 LTS Linux 5.19.0-32-generic Wine 8.0 (stable) eMule 0.51d (https://github.com/irwir/eMule/releases/tag/eMule_v0.51d-community) inxi -Gxz Graphics: Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: ASUSTeK P8 series driver: i915 v: kernel bus-ID: 00:02.0 Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 22.2.5 direct render: Yes -- 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

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