wine-bugs

wine-bugs@winehq.org

1 participants
159195 discussions

[Bug 54576] New: riched32:editor - test_EM_POSFROMCHAR() fails in the Hindi locale on Windows
by WineHQ Bugzilla 25 Feb '23

25 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54576 Bug ID: 54576 Summary: riched32:editor - test_EM_POSFROMCHAR() fails in the Hindi locale on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com riched32:editor - test_EM_POSFROMCHAR() fails in the Hindi locale on Windows: editor.c:876: Test failed: EM_POSFROMCHAR reports x=8, expected 1 editor.c:902: Test failed: EM_POSFROMCHAR reports x=8, expected 1 See https://test.winehq.org/data/patterns.html#riched32:editor The failure is systematic and started as soon as we got a real Windows Hindi locale to test. -- 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 54577] New: riched32:editor - test_EM_GETLINE() fails in the Hindi locale on Windows
by WineHQ Bugzilla 25 Feb '23

25 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54577 Bug ID: 54577 Summary: riched32:editor - test_EM_GETLINE() fails in the Hindi locale on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com riched32:editor - test_EM_GETLINE() fails in the Hindi locale on Windows: editor.c:451: Test failed: 0: expected_bytes_written=9 editor.c:451: Test failed: 1: expected_bytes_written=4 editor.c:451: Test failed: 2: expected_bytes_written=4 editor.c:451: Test failed: 3: expected_bytes_written=2 See https://test.winehq.org/data/patterns.html#riched32:editor The failure is systematic and started as soon as we got a real Windows Hindi locale to test. -- 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 29028] New: Starcraft crashes on exit
by wine-bugs＠winehq.org 25 Feb '23

25 Feb '23

http://bugs.winehq.org/show_bug.cgi?id=29028 Bug #: 29028 Summary: Starcraft crashes on exit Product: Wine Version: 1.3.31 Platform: x86 OS/Version: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: amasterov(a)gmail.com Classification: Unclassified After upgrading wine to 1.3.31 Starcraft crashes on exit. wine 1.3.30 has not this problem. After choosing exit in game menu I get black screen in 640x480 resolution (I switch to nvidia-settings with Alt-Tab and set up correct resolution after this). In console there are this lines: fixme:advapi:SetSecurityInfo stub fixme:win:EnumDisplayDevicesW ((null),0,0x33f3d8,0x00000000), stub! err:seh:setup_exception_record stack overflow 844 bytes in thread 0024 eip 0041efcc esp 00240fe4 stack 0x240000-0x241000-0x340000 err:ntdll:RtlpWaitForCriticalSection section 0x62385d40 "time.c: TIME_tz_section" wait timed out in thread 0027, blocked by 0024, retrying (60 sec) err:seh:raise_exception Unhandled exception code c0000194 flags 0 addr 0x6231354f I've tried regression testing with git bisect and get this result: 496b438ede825fc00daac7a5869e045ae583cec9 is the first bad commit commit 496b438ede825fc00daac7a5869e045ae583cec9 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Tue Sep 27 09:31:59 2011 -0500 wined3d: Remove d3d8/9 palette support. :040000 040000 8b95a8e0e4e7524170ba43bc2ffe369359b9811d 7c427ec5a0816aa5da25718cee9c70e0d3605214 M dlls :040000 040000 a6ee1c817b1f21634ddad86780fad5cfe9c4fb29 fe57de377c4cf96d0f48c4560d0db321b7b28e91 M include There was slightly different errors on the screen during testing, but I did "git bisect bad" on every crash on exit. With what WINEDEBUG flags should I run wine to provide any additional information about this issue? -- 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 12

[Bug 54569] New: Guitar Rig 6 crashes when playing any sound
by WineHQ Bugzilla 25 Feb '23

25 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54569 Bug ID: 54569 Summary: Guitar Rig 6 crashes when playing any sound Product: Wine Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: velicaglayan(a)hacettepe.edu.tr Distribution: --- Created attachment 74111 --> https://bugs.winehq.org/attachment.cgi?id=74111 I used wine explorer to select the exe and it crashed when I play a video from mpv. While Guitar Rig is open, playing audio from my browser or any other app immediately crashes the program. Both Guitar Rig and the other software go silent first, after the crash, other software etc. mpv restores its audio playback. I use Arch Linux with PipeWire. And my audio interface is UA Volt 2. You can download the demo version of the program here: 2https://www.native-instruments.com/en/products/komplete/guitar/guitar-rig-… -- 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 54572] New: Miflash_unlocker fatal error when opening
by WineHQ Bugzilla 25 Feb '23

25 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54572 Bug ID: 54572 Summary: Miflash_unlocker fatal error when opening Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: realdark(a)protonmail.com Distribution: --- Created attachment 74115 --> https://bugs.winehq.org/attachment.cgi?id=74115 backtraces from error Miflash_unlocker fatal error when opening New Prefix 32-Bit and 64-Bit used. App starts but get seqfaults. -- 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 0

[Bug 19017] New: DirectX Hardware presenting Problem
by wine-bugs＠winehq.org 24 Feb '23

24 Feb '23

http://bugs.winehq.org/show_bug.cgi?id=19017 Summary: DirectX Hardware presenting Problem Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: fr.fr(a)vr-web.de Created an attachment (id=21920) --> (http://bugs.winehq.org/attachment.cgi?id=21920) Log output of the Game Balls (in Appdb is a link for a Download) Device is not Found It seams DirectX in Wine has a Problem with presenting Hardware devices -- 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 32

[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

[Bug 54547] New: Hyperplanning software (index education) crashes all the time for now
by WineHQ Bugzilla 21 Feb '23

21 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54547 Bug ID: 54547 Summary: Hyperplanning software (index education) crashes all the time for now Product: Wine Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: olivier.corrio(a)gmail.com Distribution: --- Created attachment 74087 --> https://bugs.winehq.org/attachment.cgi?id=74087 It is the backtrace The software works several minutes but often it crashes in less than 1mn. I can use it but suddenly it crashes -- 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 0

[Bug 54169] New: ntoskrnl.exe:ntoskrnl - test_pnp_devices() sometimes fails on Windows and Linux
by WineHQ Bugzilla 21 Feb '23

21 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54169 Bug ID: 54169 Summary: ntoskrnl.exe:ntoskrnl - test_pnp_devices() sometimes fails on Windows and Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntoskrnl.exe:ntoskrnl - test_pnp_devices() fails on Windows 10 with test signing turned on: ntoskrnl.c:1801: Test failed: failed to create device, error 0xe0000207 ntoskrnl.c:1805: Test failed: failed to create set hardware ID, error 0x57 ntoskrnl.c:1808: Test failed: failed to register device, error 0x57 ntoskrnl.c:1813: Test failed: got error 0x57 ntoskrnl.c:1817: Test failed: failed to install device, error 0xe000020b ntoskrnl.c:1822: Test failed: got error 0x57 ntoskrnl.c:1823: Test failed: got flags 0x10 ntoskrnl.c:1824: Test failed: got type 0 ntoskrnl.c:1546: Test failed: failed to get interface, error 0x103 ntoskrnl.c:1547: Test failed: wrong class {deadbeef-29ef-4538-a5fd-b69573a362c0} ntoskrnl.c:1549: Test failed: got flags 0x1 ntoskrnl.c:1563: Test failed: got 0 bus arrival messages ntoskrnl.c:1569: Test failed: failed to get interface, error 0x103 ntoskrnl.c:1570: Test failed: wrong class {deadbeef-29ef-4538-a5fd-b69573a362c0} ntoskrnl.c:1579: Test failed: got 0 bus arrival messages ntoskrnl.c:1580: Test failed: got 0 bus removal messages ntoskrnl.c:1585: Test failed: failed to get interface, error 0x103 ntoskrnl.c:1586: Test failed: wrong class {deadbeef-29ef-4538-a5fd-b69573a362c0} ntoskrnl.c:1588: Test failed: got flags 0x1 ntoskrnl.c:1605: Test failed: got 0 child arrival messages ntoskrnl.c:1612: Test failed: failed to get device, error 0x103 ntoskrnl.c:1613: Test failed: wrong class {4d36e97d-e325-11ce-bfc1-08002be10318} ntoskrnl.c:1616: Test failed: failed to get device ID, error 0x57 ntoskrnl.c:1617: Test failed: got ID "\x08" ntoskrnl.c:1621: Test failed: got error 0x57 ntoskrnl.c:1637: Test failed: got error 0x57 ntoskrnl.c:1639: Test failed: got flags 0x69f1b90b ntoskrnl.c:1640: Test failed: got type 0 ntoskrnl.c:1645: Test failed: got error 0x57 ntoskrnl.c:1650: Test failed: got error 0x57 ntoskrnl.c:1654: Test failed: got error 0x57 ntoskrnl.c:1655: Test failed: got type 0 ntoskrnl.c:1656: Test failed: got size 0 ntoskrnl.c:1662: Test failed: got error 0x57 ntoskrnl.c:1663: Test failed: got type 0 ntoskrnl.c:1664: Test failed: got size 0 ntoskrnl.c:1669: Test failed: got error 0x57 ntoskrnl.c:1670: Test failed: got type 0 ntoskrnl.c:1671: Test failed: got size 0 ntoskrnl.c:1676: Test failed: got error 0x57 ntoskrnl.c:1688: Test failed: failed to open child: 0xc0000034 ntoskrnl.c:1692: Test failed: got error 6 ntoskrnl.c:1693: Test failed: got id -559038737 ntoskrnl.c:1694: Test failed: got size 0 ntoskrnl.c:1699: Test failed: failed to open child: 0xc0000034 ntoskrnl.c:1703: Test failed: got error 6 ntoskrnl.c:1711: Test failed: got 0 child arrival messages ntoskrnl.c:1712: Test failed: got 0 child removal messages ntoskrnl.c:1715: Test failed: got error 6 ntoskrnl.c:1718: Test failed: got 0xc0000034 ntoskrnl.c:1722: Test failed: got error 6 ntoskrnl.c:1728: Test failed: got 0 child arrival messages ntoskrnl.c:1729: Test failed: got 0 child removal messages ntoskrnl.c:1833: Test failed: failed to remove device, error 0x57 ntoskrnl.c:1836: Test failed: expected failure ntoskrnl.c:1837: Test failed: got error 0 ntoskrnl.c:1857: Test failed: failed to open service, error 1060 ntoskrnl.c:291: Test failed: expected SERVICE_STOPPED, got 0 See https://test.winehq.org/data/patterns.html#ntoskrnl.exe:ntoskrnl This happens a couple of times per month, mostly in the 64-bit w1064-tsign tests. However this also happened on: * 2022-07-04 w7u-pt-PT despite it not having test signing turned on. * 2022-10-24 master: this is the first known instance of these failures in Wine. * 2022-12-01 lastestmaster: these failures seem to have been systematic on this Wine test configuration. Unlike on Windows, none of the official Wine test configurations seem to be having 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 4

[Bug 54543] New: Avantree Leaf USB audio device does not play sound in applications run via wine
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54543 Bug ID: 54543 Summary: Avantree Leaf USB audio device does not play sound in applications run via wine Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linux(a)bernd-steinhauser.de Distribution: --- I'm using an USB audio device called "Avantree Leaf" to pass audio via Bluetooth to a receiver. After this change in the kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… applications run by wine via the pulseaudio output cannot initiate a stream on the audio device and there is no sound. To test, I've used the audio player foobar2000, but it's the same for other Windows applications. Native Linux applications work without problems so far. The latest Wine version that I tested is 8.1, but I haven't found any between Wine versions in this regard. It also does not work, if I select the usb device specifically in winecfg or in foobar2000 itself. I do however get sound if I select another device, e.g. my onboard sound card or the HDMI output, thus I know it is a problem with the usb device only. I usually use pipewire/wireplumber as an audio server with pipewire-pulse as a Pulseaudio replacement, but the problem also exists if I'm using standard Pulseaudio instead. There are two possible workarounds that I can use to get sound from the device when running Wine application: 1. Disable the usb audio latency management by loading the module with the parameter lowlatency=0 2. Set clock.min-quantum 512 in pipewire/wireplumber, which I think also increases the latency a bit The maintainer of the kernel usb audio driver thinks that this an application problem and that the kernel driver is working correctly. Therefore, I'm now opening this bug report. The corresponding bug report on the kernel side is, there I also have some additional information available, not sure if I should replicate all of that here: https://bugzilla.kernel.org/show_bug.cgi?id=216909 Also, see this discussion on a pipewire issue, which was the first report I did about this: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2739#note_1713023 -- 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 53144] New: kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53144 Bug ID: 53144 Summary: kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7: debugger.c:2122: Test failed: NtSetInformationDebugObject failed c0000008 debugger.c:2144: Test failed: NtSetInformationDebugObject failed c0000008 https://test.winehq.org/data/patterns.html#kernel32:debugger 0xc0000008 == STATUS_INVALID_HANDLE Sometimes only the second failure 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 4

[Bug 54541] New: d3dx10_34:d3dx10 - test_get_image_info() gets unexpected hr on Windows 21H1+
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54541 Bug ID: 54541 Summary: d3dx10_34:d3dx10 - test_get_image_info() gets unexpected hr on Windows 21H1+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3dx10_34:d3dx10 - test_get_image_info() gets unexpected hr on Windows 21H1+: d3dx10.c:2677: Test failed: Test 0: Got unexpected hr2 0xdeadbeef. d3dx10.c:2686: Test failed: Test 0: Got unexpected hr2 0xdeadbeef. See https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10 For d3dx10_34 it's always the same two checks that fail (the other d3dx10_* tests get similar failures in other places) and it always happens in the 32-bit tests. These failures are pretty rare too, only 5 instances in the past 6 months: 2022-09-07 on w1064 32-bit 2022-09-20 on w1064-tsign 32-bit 2022-11-29 on w10pro64 32-bit 2023-01-27 on fgtb-w10pro64 32-bit 2023-02-17 on w1064 32-bit -- 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 54513] New: wine: Call from 0000000170032138 to unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err, aborting
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54513 Bug ID: 54513 Summary: wine: Call from 0000000170032138 to unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err, aborting Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sagar.ghuge(a)intel.com Distribution: --- When I run games through steam, I am running into an issue where I see the following error and the game suddenly crashes. wine: Call from 0000000170032138 to unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err, aborting -- 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 54467] New: Printing not possible after update to Wine 8.0
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54467 Bug ID: 54467 Summary: Printing not possible after update to Wine 8.0 Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: n296869(a)rtrtr.com Distribution: --- Printing from windows-apps doesn't work anymore, after updating to wine-8.0. I tried printing with PDFXChange-Viewer and PDFXChange-Editor. In both programs, all cups printers are available. However, when trying to print, cups doesn't receive any printjobs. In the wine-directory the print-jobs seem to get spooled. There are files created in: $HOME/.wine/drive_c/windows/system32/spool/printers/ I can open them with ghostscript-viewer. I can find several old, unfinished print-jobs in this folder. I can't find any print-related error-messages. I looked in: /var/log/cups/access_log /var/log/syslog /var/log/apport.log ...and the commandline, of course. I also tried the command "aa-complain cupsd" on the commandline to enable everything cups-related inside apparmor. It didn't help. BTW, I'm on ubuntu 18.04, 64-Bit, with cups 2.2.7. Registering/log-in on wine-forums isn't possible for some reason and there are no similar reports for print-problems with wine trying several search-enginges. This is a very annoying bug. I really want to track it down. -- 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 54540] New: Wine Devel: needs to be updated error [MAC OS]
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54540 Bug ID: 54540 Summary: Wine Devel: needs to be updated error [MAC OS] Product: Wine Version: 5.7 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tanataba58(a)gmail.com Created attachment 74081 --> https://bugs.winehq.org/attachment.cgi?id=74081 Error pop-up msg Using Monterey on macOS, ver 12.5 Decided to download Wine Development 5.7 (https://dl.winehq.org/wine-builds/macosx/download.html), but after it's finished downloading I keep getting an error that asks for Wine Devel to be updated by the developer. The "Learn more" leads to (https://support.apple.com/en-us/HT208436), so I assume it has to do with the file being 32bit? I'm not tech savy so my apologies. I made sure to download the "64bit support" that showed up on the installer itself. I'm unsure why it doesn't work though. Image is attached. Any help is appreciated. -- 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 54512] New: Hardwar (Steam) crashes while loading the main menu
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54512 Bug ID: 54512 Summary: Hardwar (Steam) crashes while loading the main menu Product: Wine Version: 8.0-rc1 Hardware: x86-64 URL: https://store.steampowered.com/app/1500540/Hardwar/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: a7fda2f8cb7e09b16fd7dc0ce2e40b5939757e78 Distribution: ArchLinux Created attachment 74054 --> https://bugs.winehq.org/attachment.cgi?id=74054 terminal output The game's launcher and the intro video work but the game crashes while loading to the main menu. Works in Wine-7.22 and the regression test points to commit a7fda2f8cb7e09b16fd7dc0ce2e40b5939757e78 ntdll: Make realloc implementation more generic. Either resizing a block in place, or reallocating through RtlHeap calls. With the previous commit the game works properly. Tested with wine-8.1-231-gdf5f6f66de8. -- 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