wine-bugs January 2021

wine-bugs@winehq.org

1 participants
7005 discussions

[Bug 35884] New: Visual Studio 20XX frequently calls CoGetCallerTID(), resulting in console spam due to stub
by wine-bugs＠winehq.org 22 Jan '21

22 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=35884 Bug ID: 35884 Summary: Visual Studio 20XX frequently calls CoGetCallerTID(), resulting in console spam due to stub Product: Wine Version: 1.7.15 Hardware: x86 OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says... not really harmful though. --- snip --- ... fixme:ole:CoGetCallerTID stub! fixme:ole:CoGetCallerTID stub! fixme:ole:CoGetCallerTID stub! fixme:ole:CoGetCallerTID stub! ... --- snip --- I'd prefer a real implementation over a 'FIXME once', it's not particularly hard to do. MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/ms680683%28v=vs.85%… --- quote --- lpdwTID [out] Receives the apartment ID of the caller's thread. For a single threaded apartment (STA), this is the current thread ID. For a multithreaded apartment (MTA), the value is 0. For a neutral apartment (NA), the value is -1. --- quote --- Source: http://source.winehq.org/git/wine.git/blob/39562961283ccb7c838c5650b11873e6… --- snip --- 92 HRESULT WINAPI CoGetCallerTID(LPDWORD lpdwTID) 93 { 94 FIXME("stub!\n"); 95 return E_NOTIMPL; 96 } --- snip --- $ wine --version wine-1.7.15-112-g2aad5d7 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.

2 8

[Bug 16882] New: WMI core 1.5 installation hangs (needed for .NET 3.0 installer, WCF part), SECURITY_SERVICE_RID missing from service token group
by wine-bugs＠winehq.org 22 Jan '21

22 Jan '21

http://bugs.winehq.org/show_bug.cgi?id=16882 Summary: WMI core 1.5 installation hangs (needed for .NET 3.0 installer, WCF part), SECURITY_SERVICE_RID missing from service token group Product: Wine Version: 1.1.12 Platform: Other URL: http://www.microsoft.com/downloads/details.aspx?familyid =AFE41F46-E213-4CBF-9C5B-FBF236E0E875 OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, after getting past bug 16879 one encounters this one. ---- Prerequisite: 1. clean WINEPREFIX 2. sh winetricks -q dotnet20 3. download .NET 3.0 Framework installer from: http://download.microsoft.com /download/4/d/a/4da3a5fa-ee6a-42b8-8bfa-ea5c4a458a7d/dotnetfx3setup.exe (sha1sum: a566bcd2ffffc3842a95adc57f7df3f8cd11577f) 4. export _SFX_CAB_SHUTDOWN_REQUEST=1 (workaround, see bug 9158) 5. wine ./dotnetfx3setup.exe It might take a while until all required packages are downloaded using BITS. Note: If you need to redo steps, backup the directory "dotnetfx304506.30" from "c:\\windows\\temp" to a different location, remove ~/.wine, copy "dotnetfx304506.30" again to "c:\\windows\\temp" to prevent BITS from downloading over and over again. ---- "c:\\windows\\temp\\dd_dotnetfx3error.txt": --- snip --- [01/11/09,12:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603 [01/11/09,12:50:31] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed. [01/11/09,12:50:31] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed. --- snip --- "c:\\windows\\temp\\dd_wcf_retMSI597F.txt": --- snip --- 1: C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe /r /x /y /v 2: 1: ERROR: Process returned non-0 value! CMDLINE: C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe /r /x /y /v 2: 1: Failed 2: --- snip --- and "c:\\windows\\temp\\dd_wcf_retCA69A1.txt": --- snip --- === Verbose logging started: 1/11/2009 12:50:17 Calling process: C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe === ServiceModelReg [12:50:18:302]: Warning: Could not detect IIS installation or IIS is disabled, skipping the Web Host Script Mappings component since it depends upon IIS to function properly. If you believe this message is an error, check your IIS installation to make sure it is installed properly. ServiceModelReg [12:50:18:329]: Information: The ServiceModelReg tool will take the following actions: Reinstalling configuration section system.serviceModel to C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. Reinstalling configuration section system.runtime.serialization to C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. Reinstalling configuration section system.serviceModel.activation to C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. Adding configuration entry for BuildProvider: System.ServiceModel.Activation.ServiceBuildProvider, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Reinstalling compilation assembly node to System.Web section group: System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL Reinstalling compilation assembly node to System.Web section group: System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitectur... ServiceModelReg [12:50:18:358]: Uninstalling: Machine.config Section Groups and Handlers ServiceModelReg [12:50:18:366]: Warning: Configuration section system.serviceModel does not exist in C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. ServiceModelReg [12:50:18:369]: Warning: Configuration section system.runtime.serialization does not exist in C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. ServiceModelReg [12:50:18:373]: Warning: Configuration section system.serviceModel.activation does not exist in C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. ServiceModelReg [12:50:18:374]: Installing: Machine.config Section Groups and Handlers ServiceModelReg [12:50:18:893]: Uninstalling: System.Web Build Provider ServiceModelReg [12:50:19:095]: Warning: A configuration entry for BuildProvider System.ServiceModel.Activation.ServiceBuildProvider, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 does not exist. ServiceModelReg [12:50:19:096]: Installing: System.Web Build Provider ServiceModelReg [12:50:19:138]: Uninstalling: System.Web Compilation Assemblies ServiceModelReg [12:50:19:153]: Warning: All compilation assembly nodes do not exist in System.Web section group. ServiceModelReg [12:50:19:154]: Installing: System.Web Compilation Assemblies ServiceModelReg [12:50:19:246]: Uninstalling: HTTP Handlers ServiceModelReg [12:50:19:260]: Warning: HttpHandlers node *.svc does not exist in System.Web section group. ServiceModelReg [12:50:19:261]: Installing: HTTP Handlers ServiceModelReg [12:50:19:322]: Uninstalling: HTTP Modules ServiceModelReg [12:50:19:333]: Warning: HttpModules node ServiceModel does not exist in System.Web section group. ServiceModelReg [12:50:19:334]: Installing: HTTP Modules ServiceModelReg [12:50:19:365]: Repairing: WMI Classes ServiceModelReg [12:50:19:396]: Warning: Failure executing "C:\windows\system32\wbem\mofcomp.exe" with parameters ""C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModel.mof"": System.IO.FileNotFoundException: Could not load file or assembly 'C:\windows\system32\wbem\mofcomp.exe' or one of its dependencies. Exception from HRESULT: 0x80070002 File name: 'C:\windows\system32\wbem\mofcomp.exe' at System.ServiceModel.Install.InstallHelper.ExecuteWaitHelper(String program, String parameters) at System.ServiceModel.Install.InstallHelper.ExecuteWait(String program, String parameters, Int32[] allowedExitCodes) at System.ServiceModel.Install.WmiInstallComponent.OnInstall(OutputLevel outputLevel) ServiceModelReg [12:50:19:516]: System.InvalidCastException: Retrieving the COM class factory for component with CLSID {4590F811-1D3A-11D0-891F-00AA004B2E24} failed due to the following error: 80004002. at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementScope.Connect() at System.ServiceModel.Install.WmiInstallComponent.get_IsInstalled() at System.ServiceModel.Install.WmiInstallComponent.ApplyNamespaceDacl(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.OnInstall(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.Reinstall(OutputLevel outputLevel) at Microsoft.Tools.ServiceModel.ServiceModelReg.PerformAction(ActionItem actionItem, Nullable`1 confirmUninstall) at Microsoft.Tools.ServiceModel.ServiceModelReg.Run(String[] args) at Microsoft.Tools.ServiceModel.ServiceModelReg.TryRun(String[] args) === Verbose logging stopped: 1/11/2009 12:50:19 === --- snip --- Oh joy ... WMI. Providing fake mofcomp.exe (returning success) is not enough, WCF installer will try *use* WMI hence there needs to be some working infrastructure: --- snip --- ServiceModelReg [19:37:29:832]: Starting tool 'C:\windows\system32\wbem\mofcomp.exe' with parameters '"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModel.mof"'. ServiceModelReg [19:37:29:895]: ServiceModelReg [19:37:29:896]: ServiceModelReg [19:37:29:897]: Tool 'C:\windows\system32\wbem\mofcomp.exe' with parameters '"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModel.mof"' exited with code '0'. ServiceModelReg [19:37:29:955]: System.InvalidCastException: Retrieving the COM class factory for component with CLSID {4590F811-1D3A-11D0-891F-00AA004B2E24} failed due to the following error: 80004002. at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementScope.Connect() at System.ServiceModel.Install.WmiInstallComponent.get_IsInstalled() at System.ServiceModel.Install.WmiInstallComponent.ApplyNamespaceDacl(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.OnInstall(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.Reinstall(OutputLevel outputLevel) at Microsoft.Tools.ServiceModel.ServiceModelReg.PerformAction(ActionItem actionItem, Nullable`1 confirmUninstall) at Microsoft.Tools.ServiceModel.ServiceModelReg.Run(String[] args) at Microsoft.Tools.ServiceModel.ServiceModelReg.TryRun(String[] args) === Verbose logging stopped: 1/8/2009 19:37:29 === --- snip --- This is a big blocker and getting WMI to work with Wine is imperative for .NET 3.0 and higher. Of course this also useful for older .NET Frameworks Roll-back, prepare clean WINEPREFIX again;-) We need to install native WMI core 1.5 from: http://www.microsoft.com/downloads/details.aspx?familyid=AFE41F46-E213-4CBF… Download wmicore http://download.microsoft.com/download/platformsdk/wmicore/1.5/W9XNT4/EN-US… (sha1sum: f7a36668eb6c82a28393637ffdf0ec6e8adfa6a1) Make sure you set winver to NT 4.0 (don't forget to reset to default) and execute the installer (I already have my own winetricks step for this): --- snip --- wine wmicore.exe --- snip --- The installer will then hang at some point "Configuring repository". With winedbg one can see following processes: --- snip --- Wine-dbg>info process pid threads parent executable (all id:s are in hex) 0000000c 5 0000000a 'services.exe' 0000000f 1 0000000a 'explorer.exe' 0000001b 4 0000000c 'winedevice.exe' 00000025 1 00000000 'wmicore.exe' 00000027 2 00000025 'GLBbab.tmp' 00000022 4 0000000c 'WinMgmt.exe' --- snip --- The problem is "WinMgmt.exe" which ought to be a service but due to Wine insufficiency the service thinks it's a normal process not showing usual service process behaviour as registering control handler and the like. If you do 'wineserver -k' and try to start anything with Wine nothing will happen until wineboot times out... As quickfix, start regedit (wait until wineboot timeout) and set service start type key for "WinMgmt" to manual start, e.g. "2" -> "3". Also a kernel driver (service) that is installed with WMI "smbios" fails to load but this currently harmless. If we look now in "c:\\windows\\system32\\WBEM" we see the whole stuff installed. The logs in "logs" subdirs are not revealing much so we have to increase the log level: --- snip --- [HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM] "Logging"="1" "Logging Directory"="C:\\windows\\system32\\WBEM\\Logs" --- snip --- LogLevel is 0 to turn off logging, a 1 to turn on logging, and a 2 for verbose logging. After that, we manually try to start the service: --- snip --- $ wine net start winmgmt err:winedevice:ServiceMain driver L"smbios" failed to load The Windows Management Instrumentation service is starting. fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),2,2,(nil),32,(nil)) - stub! fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),1,3,(nil),0,(nil)) - stub! fixme:advapi:RegisterEventSourceW (L"",L"WinMgmt"): stub wine: Call from 0x7b844f54 to unimplemented function ole32.dll.CoSwitchCallContext, aborting err:rpc:I_RpcReceive we got fault packet with status 0x80000100 fixme:ole:CoCreateInstance no instance created for interface {00000000-0000-0000-c000-000000000046} of class {8bc3f05e-d86b-11d0-a075-00c04fb68820}, hres is 0xc0000005 --- snip --- This is bug 7187 After fixing this problem, we repeat the whole stuff again to get this in logs: --- snip --- (Sun Jan 11 13:41:41 2009) : Starting WinMgmt, ProcID = 26, CmdLine = , User = focht(Sun Jan 11 13:41:41 2009) : WinMgmt bIsService = 0, return code from function determining if service = 0(Sun Jan 11 13:41:41 2009) : WinMgmt gbRunAsApp = 1(Sun Jan 11 13:41:41 2009) : Starting Initialize, ID = 26(Sun Jan 11 13:41:41 2009) : Registered class factory with flags: 0x15 (Sun Jan 11 13:41:41 2009) : RegOpenKey returned 0x2 while trying to open the transports node. Using default transports!(Sun Jan 11 13:41:41 2009) : Initialize complete(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=24, wParam=0, lParam=33f814(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=81, wParam=0, lParam=33fce8(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=83, wParam=0, lParam=33f974(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=1, wParam=0, lParam=33fce8(Sun Jan 11 13:41:41 2009) : Inside the waiting function --- snip --- "WinMgmt bIsService = 0" is the culprit. The process retrieves token information and checks if process token groups contain "SECURITY_INTERACTIVE_RID" (-> normal process) or "SECURITY_SERVICE_RID" (service process). I think it's actually services.exe that adds the SECURITY_SERVICE_RID sid to the newly created service process (token groups). This requires some infrastructure, including wineserver. I already quick-hacked a path to verify this and it works as expected, letting the service successfully start ;-) 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 50541] New: Cross Code - screen freezes for a few secs.
by WineHQ Bugzilla 22 Jan '21

22 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50541 Bug ID: 50541 Summary: Cross Code - screen freezes for a few secs. Product: Wine Version: 6.0 Hardware: x86-64 URL: https://store.steampowered.com/app/368340/CrossCode/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: BOBBLOG(a)protonmail.com Distribution: --- Created attachment 69210 --> https://bugs.winehq.org/attachment.cgi?id=69210 Cross Code Screen Freeze Terminal wine-6.0 With the game Cross Code, the screen freezes for a few secs in wine-6.0 with a clean wine prefix. This issue does not happen right away, you have to play the game for a while to see the issue come up. I saw on the terminal this message just before the screen freeze up for a few seconds. 01b8:fixme:d3d:create_texture_view OpenGL implementation does not support texture views. Not sure if that's the issue but figure i'd mention it. Anyways i'll upload the full terminal messages log. -- 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 46079] New: Support 32-bit ARM hard-float cross-toolchains with GNU binutils assembler that doesn 't implicitly assume '.fpu {vfp,neon}' (Yocto/Poky SDK)
by wine-bugs＠winehq.org 21 Jan '21

21 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=46079 Bug ID: 46079 Summary: Support 32-bit ARM hard-float cross-toolchains with GNU binutils assembler that doesn't implicitly assume '.fpu {vfp,neon}' (Yocto/Poky SDK) Product: Wine Version: 3.19 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, after working around bug 46053 ("Support cross-toolchains that need target sysroot explicitly passed via ' --sysroot' command-line option (Yocto/Poky SDK)") by having 'winegcc' passing the target sysroot to the cross-compiler/linker via '--sysroot', aarch64 Wine now cross compiles successfully with a full target sysroot. -> aarch64-poky-linux ------------------------------------------------------------------------- Build Configuration: BB_VERSION = "1.38.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "fedora-28" TARGET_SYS = "aarch64-poky-linux" MACHINE = "qemuarm64" DISTRO = "poky" DISTRO_VERSION = "2.5.1" TUNE_FEATURES = "aarch64" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "sumo:d240b885f26e9b05c8db0364ab2ace9796709aad" meta-oe = "sumo:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966" meta-clang = "sumo:1784b06e6b1a83748438b4bec7e079d735d5b608" ... ------------------------------------------------------------------------- Building for 32-bit ARMv7 hard-float fails (using the same mechanics). -> arm-poky-linux-gnueabi (cortexa9hf-vfpv3-poky-linux-gnueabi) ------------------------------------------------------------------------- Build Configuration: BB_VERSION = "1.38.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "fedora-28" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "qemuarma9" DISTRO = "poky" DISTRO_VERSION = "2.5.1" TUNE_FEATURES = "arm armv7a vfp vfpv3d16 vfpv3 callconvention-hard cortexa9" TARGET_FPU = "hard" meta meta-poky meta-yocto-bsp = "sumo:d240b885f26e9b05c8db0364ab2ace9796709aad" meta-oe = "sumo:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966" meta-clang = "sumo:1784b06e6b1a83748438b4bec7e079d735d5b608" ... ------------------------------------------------------------------------- --- snip --- ... /home/focht/projects/wine/mainline-build-x86_64/tools/winegcc/winegcc -o d2d1.dll.so \ -B/home/focht/projects/wine/mainline-build-x86_64/tools/winebuild --sysroot=../.. -b \ arm-poky-linux-gnueabi -marm -mfloat-abi=hard -fasynchronous-unwind-tables -shared /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec \ bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o \ hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o version.res \ -ldwrite -ld3d10_1 ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a -lgdi32 -luser32 \ -ladvapi32 ../../libs/port/libwine_port.a -Wb,-ddwrite -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed d2d1.IYX82U.s: Assembler messages: d2d1.IYX82U.s:291: Error: selected processor does not support `vpush {s0-s15}' in ARM mode d2d1.IYX82U.s:310: Error: selected processor does not support `vpush {s0-s15}' in ARM mode winebuild: arm-poky-linux-gnueabi-gcc failed with status 1 winegcc: /home/focht/projects/wine/mainline-build-x86_64/tools/winebuild/winebuild failed make[1]: *** [Makefile:1440: d2d1.dll.so] Error 2 make[1]: Leaving directory '/home/focht/projects/wine/mainline-build-arm/dlls/d2d1' make: *** [Makefile:8385: dlls/d2d1] Error 2 --- snip --- Re-executing failing last command with '-v -save-temps': --- snip --- /home/focht/projects/wine/mainline-build-x86_64/tools/winegcc/winegcc -v -save-temps -o d2d1.dll.so -B/home/focht/projects/wine/mainline-build-x86_64/tools/winebuild --sysroot=../.. -b arm-poky-linux-gnueabi -marm -mfloat-abi=hard -fasynchronous-unwind-tables -shared /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o version.res -ldwrite -ld3d10_1 ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a -lgdi32 -luser32 -ladvapi32 ../../libs/port/libwine_port.a -Wb,-ddwrite -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed /home/focht/projects/wine/mainline-build-x86_64/tools/winebuild/winebuild -v --save-temps --target arm-poky-linux-gnueabi -fasynchronous-unwind-tables --cc-cmd=arm-poky-linux-gnueabi-gcc --ld-cmd=arm-poky-linux-gnueabi-ld -D_REENTRANT -fPIC --dll -o d2d1.dll-IpMxH8.spec.o -E /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec -L../../dlls -L../../libs/wine -marm -mfloat-abi=hard -ddwrite -rversion.res -- bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o ../../dlls/dwrite/libdwrite.def ../../dlls/d3d10_1/libd3d10_1.def ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a ../../dlls/gdi32/libgdi32.def ../../dlls/user32/libuser32.def ../../dlls/advapi32/libadvapi32.def ../../libs/port/libwine_port.a ../../dlls/winecrt0/libwinecrt0.a ../../dlls/kernel32/libkernel32.def ../../dlls/ntdll/libntdll.def arm-poky-linux-gnueabi-gcc -xassembler -c -o d2d1.nY1v31.o d2d1.CJoop5.s arm-poky-linux-gnueabi-ld -r -o d2d1.KKS2kZ.o d2d1.nY1v31.o bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a ../../libs/port/libwine_port.a ../../dlls/winecrt0/libwinecrt0.a arm-poky-linux-gnueabi-gcc -xassembler -c -o d2d1.dll-IpMxH8.spec.o d2d1.vn7wK8.s d2d1.vn7wK8.s: Assembler messages: d2d1.vn7wK8.s:291: Error: selected processor does not support `vpush {s0-s15}' in ARM mode d2d1.vn7wK8.s:310: Error: selected processor does not support `vpush {s0-s15}' in ARM mode winebuild: arm-poky-linux-gnueabi-gcc failed with status 1 winegcc: /home/focht/projects/wine/mainline-build-x86_64/tools/winebuild/winebuild failed --- snip --- $ cat d2d1.vn7wK8.s /* File generated automatically from /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec; do not edit! */ /* This file can be copied, modified and distributed without restriction. */ .section ".text","ax" b 1f __wine_spec_pe_header: .skip 69632 1: .data .align 2 .globl __wine_spec_nt_header .hidden __wine_spec_nt_header __wine_spec_nt_header: .L__wine_spec_rva_base: ... .L__wine_spec_exports_funcs: .long D2D1CreateFactory .long D2D1MakeRotateMatrix .long D2D1MakeSkewMatrix .long D2D1IsMatrixInvertible .long D2D1InvertMatrix .long __wine_stub_D2D1ConvertColorSpace .long __wine_stub_D2D1CreateDevice .long __wine_stub_D2D1CreateDeviceContext .long __wine_stub_D2D1SinCos .long __wine_stub_D2D1Tan .long __wine_stub_D2D1Vec3Length ... __wine_spec_relay_entry_points: nop .align 2 .L__wine_spec_relay_entry_point_1: .cfi_startproc push {r0-r3} mov r2, SP push {LR} sub SP, #4 mov r1,#393216 ldr r0, 2f add r0, PC ldr IP, [r0, #4] 1: blx IP ldr IP, [SP, #4] add SP, #24 bx IP 2: .long .L__wine_spec_relay_descr-1b .cfi_endproc .align 2 .L__wine_spec_relay_entry_point_2: .cfi_startproc push {r0-r3} mov r2, SP vpush {s0-s15} push {LR} sub SP, #4 mov r1,#1 add r1,#65536 ldr r0, 2f add r0, PC ldr IP, [r0, #4] 1: blx IP ldr IP, [SP, #4] add SP, #88 bx IP 2: .long .L__wine_spec_relay_descr-1b .cfi_endproc .align 2 --- snip --- https://source.winehq.org/git/wine.git/blob/HEAD:/tools/winebuild/spec32.c#… --- snip --- ... case CPU_ARM: { unsigned int mask, val, count = 0; int j, has_float = 0; if (strcmp( float_abi_option, "soft" )) for (j = 0; j < odp->u.func.nb_args && !has_float; j++) has_float = is_float_arg( odp, j ); val = (odp->u.func.args_str_offset << 16) | (i - spec->base); output( "\tpush {r0-r3}\n" ); output( "\tmov r2, SP\n"); if (has_float) output( "\tvpush {s0-s15}\n" ); output( "\tpush {LR}\n" ); output( "\tsub SP, #4\n"); for (mask = 0xff; mask; mask <<= 8) if (val & mask) output( "\t%s r1,#%u\n", count++ ? "add" : "mov", val & mask ); if (!count) output( "\tmov r1,#0\n" ); output( "\tldr r0, 2f\n"); output( "\tadd r0, PC\n"); output( "\tldr IP, [r0, #4]\n"); output( "1:\tblx IP\n"); output( "\tldr IP, [SP, #4]\n" ); output( "\tadd SP, #%u\n", 24 + (has_float ? 64 : 0) ); output( "\tbx IP\n"); output( "2:\t.long .L__wine_spec_relay_descr-1b\n" ); break; ... --- snip --- The code was introduced by commit https://source.winehq.org/git/wine.git/commitdiff/5e3534ee411a8c5baea502270… ("ntdll: Fix handling of floating point arguments in relay debugging on ARM.") The problem is that Wine makes the assumption that the assembler from hardfloat binutils implicitly assumes '.fpu {vfp,neon}' without any command line options. This isn't necessarily true for most hard-float cross-toolchains but for native toolchains, running on actual targets. Usually this is solved by the cross-toolchain environment by passing the proper '-mfloat-abi=' and/or '-mfpu=' options when cross-compiling. Simple test with .c file: --- snip --- $ cat vfptest.c void foo(void){ __asm__ volatile("fadds s0, s0, s0"); } --- snip --- --- snip --- $ arm-poky-linux-gnueabi-gcc -c vfptest.c /tmp/cc3DpeRI.s: Assembler messages: /tmp/cc3DpeRI.s:27: Error: selected processor does not support `fadds s0,s0,s0' in ARM mode $ arm-poky-linux-gnueabi-gcc -mfloat-abi=hard -c vfptest.c --- snip --- Test to show the available fpu target options: --- snip --- $ arm-poky-linux-gnueabi-gcc -mfpu=? arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option ‘-mfpu=?’ arm-poky-linux-gnueabi-gcc: note: valid arguments to ‘-mfpu=’ are: auto crypto-neon-fp-armv8 fp-armv8 fpv4-sp-d16 fpv5-d16 fpv5-sp-d16 neon neon-fp-armv8 neon-fp16 neon-vfpv3 neon-vfpv4 vfp vfp3 vfpv2 vfpv3 vfpv3-d16 vfpv3-d16-fp16 vfpv3-fp16 vfpv3xd vfpv3xd-fp16 vfpv4 vfpv4-d16 arm-poky-linux-gnueabi-gcc: fatal error: no input files compilation terminated. --- snip --- Simple test with assembly file, illustrating the problem with Wine: --- snip --- $ cat vfptest.S .text test: fadds s0, s0, s0 --- snip --- NOTE: 'vfp' is an alias for 'vfpv2', 'neon' is an alias for 'neon-vfpv3' --- snip --- $ arm-poky-linux-gnueabi-gcc -c vfptest.s vfptest.s: Assembler messages: vfptest.s:3: Error: selected processor does not support `fadds s0,s0,s0' in ARM mode $ arm-poky-linux-gnueabi-gcc -c -mfloat-abi=hard vfptest.s vfptest.s: Assembler messages: vfptest.s:3: Error: selected processor does not support `fadds s0,s0,s0' in ARM mode $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfp vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfpv2 vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfpv3 vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfpv4 vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=neon vfptest.s ... --- snip --- Unlike using C with inline assembly, real assembly sources need either '.fpu' directive, or '-mfpu=' option provided in the command line. Using CFLAGS, EXTRACFLAGS to set '-mfpu=' doesn't work because of the 'winegcc' wrapper limitation (like bug 46053 it builds a custom command line, not passing these option down). Forcing to a use hardfloat binutils with assembler that implicitly assumes '.fpu vfp' without any command line options is IMHO not feasible. I don't want to change/hack upstream toolchain projects. Changing 'winebuild' to add explicit '.fpu vfp' or '.fpu neon' directives to the assembly sources in case of 32-bit ARM hard-float seems reasonable to me. https://source.winehq.org/git/wine.git/blob/HEAD:/tools/winebuild/spec32.c Simple test: --- snip --- $ cat vfptest.s .fpu vfp .text test: fadds s0, s0, s0 --- snip --- --- snip --- $ arm-poky-linux-gnueabi-gcc -c vfptest.s --- snip --- With that problem fixed, Wine now cross compiles successfully with a full 32-bit ARM hardfloat target sysroot (same x11/freetype/libxml2 etc. deps as for my x86_64 host). Next step would be running apps/tests on my x86_64 host with 'qemuarm64' and 'qemuarma9' using the generic ARM system emulation with the 'virt machine' machine which also supports 'virtio-gpu' for full graphics stack. $ wine --version wine-3.19-117-g4852130c82 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.

2 6

[Bug 265] Copy pasting into a wine app works only once
by WineHQ Bugzilla 20 Jan '21

20 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=265 abuy(a)protonmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abuy(a)protonmail.com -- 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 50532] New: get_timezone_info doing binary search in the wrong way
by WineHQ Bugzilla 20 Jan '21

20 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50532 Bug ID: 50532 Summary: get_timezone_info doing binary search in the wrong way Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: gmascellani(a)codeweavers.com Distribution: --- get_timezone_info in dlls/ntdll/unix/system.c appears to compute the daylight saving time changes for a given year in a smelly if not buggy way. I don't have any specific examples of mistaken computations, but the code seems to basically work by chance. More specifically, the indention of the code seems to be the following: * two time_t values are computed, corresponding to the beginning and the end of the requested year (year_start and year_end); * a binary search procedure is used to narrow down that interval around a DST change event. However, this cannot work in general, because binary searches only work for monotonic data, and DST is not monotonic (each year it switches forth and back, assuming there is DST at all). The algorithm works "by chance", because it first tests the beginning of the interval and then half of the interval, and usually beginning of January and beginning of June are on different DST values; then the algorithm recurses on the first half of the year, and there DST is monotonic (again, usually; I don't know if this is always true). Moreover, year_end is also set to an invalid value (0th day of 12th month, which is a month past December). Doing the "arithmetic" this corresponds to 31st of December, but is that a supported way to specify it? Why not directly setting 31st of December? Anyway, the core of this bug is the issue with binary search. -- 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 50531] New: Windows 3D Movie Maker fails to import or save sound recordings
by WineHQ Bugzilla 20 Jan '21

20 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50531 Bug ID: 50531 Summary: Windows 3D Movie Maker fails to import or save sound recordings Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zenithgraymgmt(a)gmail.com Distribution: --- Recording your own sounds via microphone or importing WAV files in Windows 3D Movie Maker shows an ingame dialog box stating "Sorry. We can't use that sound file. Try using another sound file or one of the sounds from 3D Movie Maker." 1) Start a new movie. 2) Click the "Sounds" button at the top, then the Speech button (which is represented by a pair of red lips). 3) Click either the microphone or briefcase icon at the bottom left to record or import an audio file, respectively. 4) Either record microphone input or open a WAV file from your computer. After recording microphone input, type in a filename for the recorded sound file and click "OK". The ingame dialog box I mentioned above shows. The application should either import the recording (which plays back correctly after stopping the recording) or the WAV file into the game. Build 2021-01-17 on Arch Linux This bug has been mentioned before in multiple test results on the AppDB page for Windows 3D Movie Maker, but hasn't been reported on Bugzilla prior to now. I think this may have something to do with msacm.dll, as the only useful debug/console output given when this happens is "00ec:fixme:msacm:modSetVolume stub". -- 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 48334] New: Cannot instal Forza Horizon 3
by WineHQ Bugzilla 19 Jan '21

19 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=48334 Bug ID: 48334 Summary: Cannot instal Forza Horizon 3 Product: Wine Version: 5.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Atempts to instal game results in a window pop-up that says: Runtime error at (-1:0): Cannot import dll:<utf8>kernelbase.dll This error occurs with winetricks corefonts installed and also when not installed. -- 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 48239] New: MTGA Launcher fails to download the game (regression)
by WineHQ Bugzilla 19 Jan '21

19 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=48239 Bug ID: 48239 Summary: MTGA Launcher fails to download the game (regression) Product: Wine Version: 4.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- How to reproduce: - create a 32-bit prefix - download winetricks with new powershell verb (https://github.com/Winetricks/winetricks/pull/1440) - install these verbs into the prefix: powershell arial d3dcompiler_47 dotnet472 - set Windows version to 10 - install Magic: The Gathering Arena - Launch MTGALauncher.exe The launcher will try to download the game but then return "Oops! Something went wrong while updating". Seeing how this wasn't an issue before, I've run a bisect and found that 2c68c530afbe704698f5a38674e7c72806c7c07a (kernel32: Move file time functions to kernelbase.) was the cause of the regression. Reverting that commit against Wine 4.17 fixes the issue. Should note that this doesn't happen with version set to "Windows 7". Let me know if any logs will be needed from me with any specific debug channels. -- 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

[Bug 46174] New: Fix for Bug 46066 in Wine 3.20 Breaks Voice Chat Feature in Halo Online
by wine-bugs＠winehq.org 19 Jan '21

19 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=46174 Bug ID: 46174 Summary: Fix for Bug 46066 in Wine 3.20 Breaks Voice Chat Feature in Halo Online Product: Wine-staging Version: 3.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rstrube(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62832 --> https://bugs.winehq.org/attachment.cgi?id=62832 Output when running Halo Online and crash occurs. After upgrading to Wine Staging 3.20 I noticed that Halo Online would hang as soon as a I joined any multiplayer match. After some investigation, I noticed that disabling the voice chat feature would cause the game to function correctly. With Wine Staging 3.19 the voice chat feature worked correctly. I noticed in the release notes for 3.20 a stub DLL (qwave.dll) was added. This was to fix Bug 46066. I believe this is causing the crash / hang with Halo Online. It might also affect other games with in game voice chat functionality. I've attached the output from wine when running the game and when the crash occurs. The key line is: wine: Call from 0x7b43e10c to unimplemented function qwave.dll.QOSCreateHandle, aborting Which then calls Audio Read timeouts, which cause the entire game to crash. Thanks! Rob -- 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 28

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 January 2021