wine-bugs February 2023

wine-bugs@winehq.org

1 participants
3683 discussions

[Bug 53225] New: gameux:gamestatistics has a rare pair of failures on Windows 8
by WineHQ Bugzilla 08 Feb '23

08 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53225 Bug ID: 53225 Summary: gameux:gamestatistics has a rare pair of failures on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gameux Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gameux:gamestatistics has a rare pair of failures on Windows 8: gamestatistics.c:59: Test failed: got 0x80004005 gamestatistics.c:201: statistics file path: L"C:\\Users\\winetest\\AppData\\Local\\Microsoft\\Windows\\GameExplorer\\GameStatistics\\{17A6558E-60BE-4078-B66F-9C3ADA2A32E6}\\{17A6558E-60BE-4078-B66F-9C3ADA2A32E6}.gamestats" gamestatistics.c:75: Test failed: got 0x80070057 https://test.winehq.org/data/patterns.html#gameux:gamestatistics Only one known instance on 2022-06-20 on w8adm so far. -- 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 53239] New: dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows
by WineHQ Bugzilla 08 Feb '23

08 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53239 Bug ID: 53239 Summary: dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dplay Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dpnet:client - test_enum_hosts() and test_enum_hosts_peer() fail randomly on Windows: client.c:323: Test failed: got 0x80004005 or client.c:753: Test failed: got 0x80004005 https://test.winehq.org/data/patterns.html#dpnet:client In both cases the API that fails is IDirectPlay8Client_CancelAsyncOperation() so this looks like a race condition. The failure rate (~4.4%) is low enough to cause false positives. Strangely enough all but one of the failures happened on w7u, w7pro64 and w10pro64 (21H1). That means none of the failures happened on Windows 10 1507 to 2009! -- 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 54459] New: Transparent windows aren't rendered properly + System Freezes
by WineHQ Bugzilla 07 Feb '23

07 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54459 Bug ID: 54459 Summary: Transparent windows aren't rendered properly + System Freezes 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: lunarleafclover(a)outlook.com Distribution: --- When playing the "Unresponsive" Friday Night Funkin' mod, it messes with it's Windows a lot. It moves the windows a lot and has a transparent window to render the antagonist "Fatal Error." Similar to the untitled "No More Innocence" mod with its windows moving at the end of it's one-off song. Playing the Unresponsive mod whilst recording in OBS causes the System to hang quite a while when it's 4 additional windows get created alongside the actual game process, all of which render details as the antagonist with minor background characters. Not tested on Wayland but I'd imagine it'd be somewhat smoother. The video is too big to be linked as an attachment, so I put it in streamable instead. https://streamable.com/espjym -- 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 54455] New: CodeMeterRuntime: Install fails with '00c4:err:service:process_send_command service protocol error - failed to write pipe!'
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54455 Bug ID: 54455 Summary: CodeMeterRuntime: Install fails with '00c4:err:service:process_send_command service protocol error - failed to write pipe!' 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: irmin.okic(a)gmail.com Distribution: --- Created attachment 74012 --> https://bugs.winehq.org/attachment.cgi?id=74012 Terminal output of the installer. Steps to reproduce: * Install dotnet48 into the prefix with winetricks. * Download CodeMeterRuntime 64bit 7.60 (but earlier versions had the same error) for Windows from: https://www.wibu.com/us/support/user/downloads-user-software.html * Execute the installer. * To reduce complexity in the installer on the Custom Setup step select "don't install" for all components except "CodeMeter Runtime Kit". I.e. "don't install" for Network Server, WibuShellExtension, User Help, Automatic server search, Remote access to WebAdmin. * Finish the installation. The installer will state that it ended prematurely. The relevant errors are probably: 00c4:err:service:process_send_command service protocol error - failed to write pipe! 016c:err:msi:ITERATE_StartService failed to start service L"CmWebAdmin.exe" (1053) 016c:err:msi:execute_script Execution of script 0 halted; action L"StartServices" returned 1627 016c:err:msi:ITERATE_Actions Execution halted, action L"InstallExecute" returned 1627 In Wine 7 I ignored the installer error with the following arguments to the installer: /ComponentArgs "*":"/qn ADDLOCAL=Complete,DotNET_Modules,AutomaticServerSearch REMOVE=WibuShellExtension,EnableNetworkServer,AccessToWebAdmin /l*v C:\users\z0rb\Temp\keyinst.log /norestart DISABLEROLLBACK=1 PROP_CMCC=\"none\"" The important argument was DISABLEROLLBACK=1. This meant that I can keep the install even with the failure. Then run CodeMeterCC.exe which started the CodeMeter windows service. With that service I could use further software that uses CodeMeter as their licensing service. In wine 8 even that service (together with CmWebAdmin.exe) started having the "failed to write pipe error!". I am out of workarounds at the moment and asking here for help. If you can instruct me with further debug flags and similar to narrow down the error I am ready to put in the work. -- 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 38673] New: valgrind shows uninitialized memory in dlls/kernel32/sync.c:ConnectNamedPipe()
by wine-bugs＠winehq.org 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=38673 Bug ID: 38673 Summary: valgrind shows uninitialized memory in dlls/kernel32/sync.c:ConnectNamedPipe() Product: Wine Version: 1.7.42 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Fedora ../../../tools/runtest -q -P wine -T ../../.. -M hlink.dll -p hlink_test.exe.so hlink && touch hlink.ok ==14126== Thread 3: ==14126== Syscall param writev(vector[...]) points to uninitialised byte(s) ==14126== at 0x4F7A0F4B: ??? (in /usr/lib/libc-2.21.so) ==14126== by 0x7BC7A9C5: send_request (server.c:228) ==14126== by 0x7BC7AB52: wine_server_call (server.c:309) ==14126== by 0x7BC7B8CD: server_select (server.c:607) ==14126== by 0x7BC85426: NtWaitForMultipleObjects (sync.c:976) ==14126== by 0x7BC85471: NtWaitForSingleObject (sync.c:985) ==14126== by 0x7BC45DFF: server_ioctl_file (file.c:1539) ==14126== by 0x7BC46565: NtFsControlFile (file.c:1786) ==14126== by 0x7B87406B: ConnectNamedPipe (sync.c:1615) ==14126== by 0x49255A5: listen_thread (rpc_transport.c:132) ==14126== by 0x7BC81BB7: ??? (signal_i386.c:2682) ==14126== by 0x7BC81BFE: call_thread_func (signal_i386.c:2741) ==14126== by 0x7BC81B95: ??? (signal_i386.c:2682) ==14126== by 0x7BC88D78: start_thread (thread.c:443) ==14126== by 0x4F88F37F: start_thread (in /usr/lib/libpthread-2.21.so) ==14126== by 0x4F7ABD4D: clone (in /usr/lib/libc-2.21.so) ==14126== Address 0x4cee5c4 is on thread 1's stack ==14126== Uninitialised value was created by a stack allocation ==14126== at 0x7B873FA5: ConnectNamedPipe (sync.c:1601) ==14126== also shows in ieframe/webbrowser, kernel32/pipe, -- 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 3

[Bug 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #56 from groybe(a)gmail.com --- (In reply to Rémi Bernon from comment #51) > Sure, it's okay. I don't have the device so it's going to be hard to fix it > unless someone with it and a bit of technical knowledge can debug it > directly. > > Anyway thanks for the log, but would you mind adding the +hid channel too? > Not that it will make it magically fixable but I can have a look and see if > there's anything obvious. > > For instance something like running > `WINEDEBUG=+pid,+tid,+timestamp,+joycpl,+dinput,+hid wine control joy.cpl` > and then try running a couple of force feedback effects. The G25 does work on some very old versions of wine. I also have another wheel but it's from a custom opensource project called OpenFFBoard. Both have the same results though the OpenFFBoard supports more effects. Joy.cpl didn't spin the wheel. A FFB test program called fedit.exe did work with a constant effect. RichardBurnsRally didn't work but it should also be sending a constant effect. I have attached logs for all 3. Thanks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #55 from groybe(a)gmail.com --- Created attachment 74010 --> https://bugs.winehq.org/attachment.cgi?id=74010 WINEDEBUG=+pid,+tid,+timestamp,+joycpl,+dinput,+hid RichardBurnsRally -- 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 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #54 from groybe(a)gmail.com --- Created attachment 74009 --> https://bugs.winehq.org/attachment.cgi?id=74009 WINEDEBUG=+pid,+tid,+timestamp,+joycpl,+dinput,+hid fedit.exe Working constant force -- 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 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #53 from groybe(a)gmail.com --- Created attachment 74008 --> https://bugs.winehq.org/attachment.cgi?id=74008 WINEDEBUG=+pid,+tid,+timestamp,+joycpl,+dinput,+hid joy.cpl -- 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 54454] New: Upgrading a Wine prefix configuration after upgrading to Wine 8.1 causes the sound to not work for "wav" files.
by WineHQ Bugzilla 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54454 Bug ID: 54454 Summary: Upgrading a Wine prefix configuration after upgrading to Wine 8.1 causes the sound to not work for "wav" files. 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: craigaschulstad(a)gmail.com Distribution: --- After upgrading from Wine 8.0 to 8.1 and launching a menu item, the configuration for the Wine prefix is then upgraded. The program itself runs fine, but there no longer is any sound. It should be noted that the particular program with this problem is a game program that utilizes the Windows Media Player functionality to play sounds. In comparing the system registry files for the previous version, I found that the media player reference was changed from "wmadmod.dll" to "winegstreamer.dll". Following is the text block from the previous system registry. [Software\\Classes\\CLSID\\{2EEB4ADF-4578-4D10-BCA7-BB955F56320A}] 1674785220 #time=1d931f40aaaf6e4 @="WMAudio Decoder DMO" "Merit"=dword:00800800 "WMSDKMerit"=dword:00000100 [Software\\Classes\\CLSID\\{2EEB4ADF-4578-4D10-BCA7-BB955F56320A}\\InprocServer32] 1674785220 #time=1d931f40aaae924 @="C:\\windows\\system32\\wmadmod.dll" "ThreadingModel"="Both" And following was the updated text block after the configuration was upgraded. [Software\\Classes\\CLSID\\{2EEB4ADF-4578-4D10-BCA7-BB955F56320A}] 1675650169 #time=1d939d1e8450654 @="CWMADecMediaObject" "Merit"=dword:00800800 "WMSDKMerit"=dword:00000100 [Software\\Classes\\CLSID\\{2EEB4ADF-4578-4D10-BCA7-BB955F56320A}\\InprocServer32] 1675650169 #time=1d939d1e845082a @="C:\\windows\\system32\\winegstreamer.dll" "ThreadingModel"="Both" The interim fix is to manually revise the registry entries back to referencing the "dll" file for the Windows Media Player. Once that was done, the program again produces sound. I cannot state for sure what type of code correction needs to be done, but possibly a check of the registry value for the literal "wmadmod.dll" might need to done before replacing that value with "winegstreamer.dll" Regards. -- 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

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