wine-bugs August 2025

wine-bugs@winehq.org

1 participants
496 discussions

[Bug 2082] DirectDraw games only showing black screen
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #176 from chaosesqueteam(a)sogetthis.com --- Could the entryists that are just going to close and delete this bug be gotten rid of? That's how free software is now: every "package" or "app" (we used to call them programs and projects) is brigaded by do-nothings padding their resume by "resolving" bugs. They just "wont fix" everything and cause the project to get worse and worse. Resume: I resolved 1024 bugs! (bobbles head) In my linux mint install from 2015 Diablo 1 works fine. In my Debian install from 2012 Diablo 1 works fine. In my Devuan install from 2018 Diablo 1 works fine. In my Debian server from 2003 Diablo 1 works fine. In OSX from right now, but running on intel: WONT FIX CHUUUDDDDDD WONT FIX GT THE FK OUT OF OPENSOURCE THIS IS ___OUR___ SPACE NOW ONLY RUST GAMES SUPPORTED BURN DOWN 16 BIT BECASUE MICROSOFT WOW DOESNT SUPPORT IT (note: diablo1 is 32 bit) CHUDDDD WONT FIX WONT FIX C PROGRAMS CHUUUUUUDDDD CNILE Etc. It's all resume padding, and entryism -- 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 2082] DirectDraw games only showing black screen
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #175 from chaosesqueteam(a)sogetthis.com --- h the following 2 Vulkan extensions enabled: VK_KHR_external_memory_capabilities v1 VK_KHR_get_physical_device_properties2 v2 00d4:err:hid:handle_DeviceMatchingCallback Ignoring HID device 0x7fb5654729f0 (vid 0000, pid 0000): not a joystick or gamepad 00d4:err:hid:handle_DeviceMatchingCallback Ignoring HID device 0x7fb565471e60 (vid 046d, pid c31c): not a joystick or gamepad 00d4:err:hid:handle_DeviceMatchingCallback Ignoring HID device 0x7fb5654721b0 (vid 046d, pid c31c): not a joystick or gamepad 00d4:err:hid:handle_DeviceMatchingCallback Ignoring HID device 0x7fb5654726c0 (vid 046d, pid c52f): not a joystick or gamepad 00d4:err:hid:handle_DeviceMatchingCallback Ignoring HID device 0x7fb565472380 (vid 046d, pid c52f): not a joystick or gamepad 00d4:err:hid:handle_DeviceMatchingCallback Ignoring HID device 0x7fb565472db0 (vid 05ac, pid 8242): not a joystick or gamepad 00b0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebth": c0000135 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"winebth" failed to start: 126 0124:err:environ:init_peb starting L"Z:\\Users\\user\\Diablo\\Diablo.exe" in experimental wow64 mode 0124:fixme:wow:wow64_NtSetLdtEntries 1107 0488323f 0000f333 0000 00000000 00000000: stub 012c:err:environ:init_peb starting L"Z:\\Users\\user\\Diablo\\Diablo.exe" in experimental wow64 mode 012c:fixme:wow:wow64_NtSetLdtEntries 1107 0488323f 0000f333 0000 00000000 00000000: stub [mvk-info] MoltenVK version 1.3.0, supporting Vulkan version 1.3.313. The following 117 Vulkan extensions are supported: VK_KHR_16bit_storage v1 VK_KHR_8bit_storage v1 VK_KHR_bind_memory2 v1 VK_KHR_calibrated_timestamps v1 VK_KHR_copy_commands2 v1 VK_KHR_create_renderpass2 v1 VK_KHR_dedicated_allocation v3 VK_KHR_deferred_host_operations v4 VK_KHR_depth_stencil_resolve v1 VK_KHR_descriptor_update_template v1 VK_KHR_device_group v4 VK_KHR_device_group_creation v1 VK_KHR_driver_properties v1 VK_KHR_dynamic_rendering v1 VK_KHR_external_fence v1 VK_KHR_external_fence_capabilities v1 VK_KHR_external_memory v1 VK_KHR_external_memory_capabilities v1 VK_KHR_external_semaphore v1 VK_KHR_external_semaphore_capabilities v1 VK_KHR_fragment_shader_barycentric v1 VK_KHR_format_feature_flags2 v2 VK_KHR_get_memory_requirements2 v1 VK_KHR_get_physical_device_properties2 v2 VK_KHR_get_surface_capabilities2 v1 VK_KHR_imageless_framebuffer v1 VK_KHR_image_format_list v1 VK_KHR_incremental_present v2 VK_KHR_index_type_uint8 v1 VK_KHR_load_store_op_none v1 VK_KHR_maintenance1 v2 VK_KHR_maintenance2 v1 VK_KHR_maintenance3 v1 VK_KHR_maintenance4 v2 VK_KHR_maintenance6 v1 VK_KHR_maintenance7 v1 VK_KHR_map_memory2 v1 VK_KHR_multiview v1 VK_KHR_portability_subset v1 VK_KHR_push_descriptor v2 VK_KHR_relaxed_block_layout v1 VK_KHR_sampler_mirror_clamp_to_edge v3 VK_KHR_sampler_ycbcr_conversion v14 VK_KHR_separate_depth_stencil_layouts v1 VK_KHR_shader_draw_parameters v1 VK_KHR_shader_expect_assume v1 VK_KHR_shader_float_controls v4 VK_KHR_shader_float16_int8 v1 VK_KHR_shader_integer_dot_product v1 VK_KHR_shader_non_semantic_info v1 VK_KHR_shader_subgroup_extended_types v1 VK_KHR_shader_subgroup_rotate v2 VK_KHR_shader_terminate_invocation v1 VK_KHR_spirv_1_4 v1 VK_KHR_storage_buffer_storage_class v1 VK_KHR_surface v25 VK_KHR_swapchain v70 VK_KHR_swapchain_mutable_format v1 VK_KHR_synchronization2 v1 VK_KHR_timeline_semaphore v2 VK_KHR_uniform_buffer_standard_layout v1 VK_KHR_variable_pointers v1 VK_KHR_vertex_attribute_divisor v1 VK_KHR_vulkan_memory_model v3 VK_KHR_zero_initialize_workgroup_memory v1 VK_EXT_calibrated_timestamps v2 VK_EXT_debug_marker v4 VK_EXT_debug_report v10 VK_EXT_debug_utils v2 VK_EXT_descriptor_indexing v2 VK_EXT_depth_clip_control v1 VK_EXT_extended_dynamic_state v1 VK_EXT_extended_dynamic_state2 v1 VK_EXT_extended_dynamic_state3 v2 VK_EXT_external_memory_host v1 VK_EXT_external_memory_metal v1 VK_EXT_fragment_shader_interlock v1 VK_EXT_hdr_metadata v3 VK_EXT_headless_surface v1 VK_EXT_host_image_copy v1 VK_EXT_host_query_reset v1 VK_EXT_image_2d_view_of_3d v1 VK_EXT_image_robustness v1 VK_EXT_index_type_uint8 v1 VK_EXT_inline_uniform_block v1 VK_EXT_layer_settings v2 VK_EXT_load_store_op_none v1 VK_EXT_memory_budget v1 VK_EXT_metal_objects v2 VK_EXT_metal_surface v1 VK_EXT_pipeline_creation_cache_control v3 VK_EXT_pipeline_creation_feedback v1 VK_EXT_pipeline_robustness v1 VK_EXT_private_data v1 VK_EXT_robustness2 v1 VK_EXT_sample_locations v1 VK_EXT_scalar_block_layout v1 VK_EXT_separate_stencil_usage v1 VK_EXT_shader_stencil_export v1 VK_EXT_shader_subgroup_ballot v1 VK_EXT_shader_subgroup_vote v1 VK_EXT_shader_viewport_index_layer v1 VK_EXT_subgroup_size_control v2 VK_EXT_surface_maintenance1 v1 VK_EXT_swapchain_colorspace v5 VK_EXT_swapchain_maintenance1 v1 VK_EXT_texel_buffer_alignment v1 VK_EXT_tooling_info v1 VK_EXT_vertex_attribute_divisor v3 VK_AMD_gpu_shader_half_float v2 VK_AMD_negative_viewport_height v1 VK_AMD_shader_trinary_minmax v1 VK_INTEL_shader_integer_functions2 v1 VK_GOOGLE_display_timing v1 VK_MVK_macos_surface v3 VK_MVK_moltenvk v37 VK_NV_fragment_shader_barycentric v1 [mvk-info] GPU device: model: Intel HD Graphics 4000 type: Integrated vendorID: 0x8086 deviceID: 0x0166 pipelineCacheUUID: 49B97F26-0A0F-0200-0000-000100000000 GPU memory available: 1536 MB GPU memory used: 0 MB Metal Shading Language 2.2 supports the following GPU Features: GPU Family Mac 2 Read-Write Texture Tier 1 [mvk-info] Created VkInstance for Vulkan version 1.1.0, as requested by app, with the following 4 Vulkan extensions enabled: VK_KHR_external_memory_capabilities v1 VK_KHR_get_physical_device_properties2 v2 VK_KHR_surface v25 VK_EXT_metal_surface v1 [mvk-info] Destroyed VkPhysicalDevice for GPU Intel HD Graphics 4000 with 0 MB of GPU memory still allocated. [mvk-info] Destroying VkInstance for Vulkan version 1.1.0 with 4 Vulkan extensions enabled. [mvk-info] MoltenVK version 1.3.0, supporting Vulkan version 1.3.313. The following 117 Vulkan extensions are supported: VK_KHR_16bit_storage v1 VK_KHR_8bit_storage v1 VK_KHR_bind_memory2 v1 VK_KHR_calibrated_timestamps v1 VK_KHR_copy_commands2 v1 VK_KHR_create_renderpass2 v1 VK_KHR_dedicated_allocation v3 VK_KHR_deferred_host_operations v4 VK_KHR_depth_stencil_resolve v1 VK_KHR_descriptor_update_template v1 VK_KHR_device_group v4 VK_KHR_device_group_creation v1 VK_KHR_driver_properties v1 VK_KHR_dynamic_rendering v1 VK_KHR_external_fence v1 VK_KHR_external_fence_capabilities v1 VK_KHR_external_memory v1 VK_KHR_external_memory_capabilities v1 VK_KHR_external_semaphore v1 VK_KHR_external_semaphore_capabilities v1 VK_KHR_fragment_shader_barycentric v1 VK_KHR_format_feature_flags2 v2 VK_KHR_get_memory_requirements2 v1 VK_KHR_get_physical_device_properties2 v2 VK_KHR_get_surface_capabilities2 v1 VK_KHR_imageless_framebuffer v1 VK_KHR_image_format_list v1 VK_KHR_incremental_present v2 VK_KHR_index_type_uint8 v1 VK_KHR_load_store_op_none v1 VK_KHR_maintenance1 v2 VK_KHR_maintenance2 v1 VK_KHR_maintenance3 v1 VK_KHR_maintenance4 v2 VK_KHR_maintenance6 v1 VK_KHR_maintenance7 v1 VK_KHR_map_memory2 v1 VK_KHR_multiview v1 VK_KHR_portability_subset v1 VK_KHR_push_descriptor v2 VK_KHR_relaxed_block_layout v1 VK_KHR_sampler_mirror_clamp_to_edge v3 VK_KHR_sampler_ycbcr_conversion v14 VK_KHR_separate_depth_stencil_layouts v1 VK_KHR_shader_draw_parameters v1 VK_KHR_shader_expect_assume v1 VK_KHR_shader_float_controls v4 VK_KHR_shader_float16_int8 v1 VK_KHR_shader_integer_dot_product v1 VK_KHR_shader_non_semantic_info v1 VK_KHR_shader_subgroup_extended_types v1 VK_KHR_shader_subgroup_rotate v2 VK_KHR_shader_terminate_invocation v1 VK_KHR_spirv_1_4 v1 VK_KHR_storage_buffer_storage_class v1 VK_KHR_surface v25 VK_KHR_swapchain v70 VK_KHR_swapchain_mutable_format v1 VK_KHR_synchronization2 v1 VK_KHR_timeline_semaphore v2 VK_KHR_uniform_buffer_standard_layout v1 VK_KHR_variable_pointers v1 VK_KHR_vertex_attribute_divisor v1 VK_KHR_vulkan_memory_model v3 VK_KHR_zero_initialize_workgroup_memory v1 VK_EXT_calibrated_timestamps v2 VK_EXT_debug_marker v4 VK_EXT_debug_report v10 VK_EXT_debug_utils v2 VK_EXT_descriptor_indexing v2 VK_EXT_depth_clip_control v1 VK_EXT_extended_dynamic_state v1 VK_EXT_extended_dynamic_state2 v1 VK_EXT_extended_dynamic_state3 v2 VK_EXT_external_memory_host v1 VK_EXT_external_memory_metal v1 VK_EXT_fragment_shader_interlock v1 VK_EXT_hdr_metadata v3 VK_EXT_headless_surface v1 VK_EXT_host_image_copy v1 VK_EXT_host_query_reset v1 VK_EXT_image_2d_view_of_3d v1 VK_EXT_image_robustness v1 VK_EXT_index_type_uint8 v1 VK_EXT_inline_uniform_block v1 VK_EXT_layer_settings v2 VK_EXT_load_store_op_none v1 VK_EXT_memory_budget v1 VK_EXT_metal_objects v2 VK_EXT_metal_surface v1 VK_EXT_pipeline_creation_cache_control v3 VK_EXT_pipeline_creation_feedback v1 VK_EXT_pipeline_robustness v1 VK_EXT_private_data v1 VK_EXT_robustness2 v1 VK_EXT_sample_locations v1 VK_EXT_scalar_block_layout v1 VK_EXT_separate_stencil_usage v1 VK_EXT_shader_stencil_export v1 VK_EXT_shader_subgroup_ballot v1 VK_EXT_shader_subgroup_vote v1 VK_EXT_shader_viewport_index_layer v1 VK_EXT_subgroup_size_control v2 VK_EXT_surface_maintenance1 v1 VK_EXT_swapchain_colorspace v5 VK_EXT_swapchain_maintenance1 v1 VK_EXT_texel_buffer_alignment v1 VK_EXT_tooling_info v1 VK_EXT_vertex_attribute_divisor v3 VK_AMD_gpu_shader_half_float v2 VK_AMD_negative_viewport_height v1 VK_AMD_shader_trinary_minmax v1 VK_INTEL_shader_integer_functions2 v1 VK_GOOGLE_display_timing v1 VK_MVK_macos_surface v3 VK_MVK_moltenvk v37 VK_NV_fragment_shader_barycentric v1 [mvk-info] GPU device: model: Intel HD Graphics 4000 type: Integrated vendorID: 0x8086 deviceID: 0x0166 pipelineCacheUUID: 49B97F26-0A0F-0200-0000-000100000000 GPU memory available: 1536 MB GPU memory used: 0 MB Metal Shading Language 2.2 supports the following GPU Features: GPU Family Mac 2 Read-Write Texture Tier 1 [mvk-info] Created VkInstance for Vulkan version 1.0.0, as requested by app, with the following 2 Vulkan extensions enabled: VK_KHR_external_memory_capabilities v1 VK_KHR_get_physical_device_properties2 v2 012c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 012c:fixme:ddraw:ddraw7_WaitForVerticalBlank iface 00010790, flags 0x1, event 00000000 stub! 012c:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff 012c:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff 012c:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff 012c:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff 012c:fixme:d3d:wined3d_output_get_raster_status output 000115F0, raster_status 0012FD18 semi-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 2082] DirectDraw games only showing black screen
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=2082 chaosesqueteam(a)sogetthis.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chaosesqueteam(a)sogetthis.co | |m --- Comment #174 from chaosesqueteam(a)sogetthis.com --- I also get this on macosX catalina on 10.12 devel. Meaning Wine has regressed. What the hell? WONT FIX right? -- 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 58542] New: Dual GPU 32-Bit PhysX
by WineHQ Bugzilla 12 Aug '25

12 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58542 Bug ID: 58542 Summary: Dual GPU 32-Bit PhysX Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: audioprof2002(a)hotmail.com Distribution: --- Batman Arkham Asylum v1.1 32-Bit PhysX has 3 modes: OFF, Normal, High. Normal & Off work ok. PhysX works, but Not High "Dual GPU", Windows driver allows to force PhysX to a single GPU, Dual GPU or CPU. Linux driver 470 does Not. Problem #1. instead of using Dual GPU on Linux or a single GPU, PhysX falls back to CPU PhysX in Linux. Problem #2. CPUs are very slow for 32-Bit, Batman Arkham Asylum PhysX High, requires 1-core 100% CPU load, gives 15fps on modern CPU´s. Problem #3. Nvidia deleted 32-Bit PhysX support in hardware since 2016-Q4, IF you install a 2017 GPU like P1000, in Windows, Activate/Force PhysX GPU, Does Not work. Only work with 2016-Q2 & older GPUs. im confused where could be the problem... Linux Nvidia 470 driver? Wine? winetricks? ¿how does Wine handle 32-Bit PhysX requests? block diagram? signal path? more details here: https://github.com/juanpc2018/Batman-Arkham-Asylum-Game-of-the-Year-Edition… -- 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 56648] New: Autodesk DWG TrueView fails at installation
by WineHQ Bugzilla 11 Aug '25

11 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=56648 Bug ID: 56648 Summary: Autodesk DWG TrueView fails at installation Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: szatkus(a)gmail.com Distribution: --- Installation fails with the fixme: "Could not find dependent assembly odis.bs.win (1.0.0)" Turns out the installer creates a new folder (%TEMP%/7z0F0512E4) with another installer that apparently is invoked next. The program removes it automatically after crashing, but it could be retrieved by placing `while(1);` next to the fixme or by using a Windows machine. There's the Setup.exe file that has the following manifest in its resources: <?xml version='1.0' encoding='UTF-8' standalone='yes'?> <assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level='asInvoker' uiAccess='false' /> </requestedPrivileges> </security> </trustInfo> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='odis.bs.win' version='1.0.0.0' processorArchitecture='*' language='*' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='odis.bs.wx' version='1.0.0.0' processorArchitecture='*' language='*' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*' /> </dependentAssembly> </dependency> </assembly> From what I gathered this manifest is used to resolve some required dlls files, but it ultimately fails. The odis.bs.win is resolved by the following algorithm (a comment from the wine code): /* Lookup in <dir>\name.dll * <dir>\name.manifest * <dir>\name\name.dll * <dir>\name\name.manifest * * First 'appdir' is used as <dir>, if that failed * it tries application manifest file path. */ The file it's looking for is in ODIS/odis.bs.win/odis.bs.win.manifest, not in odis.bs.win/odis.bs.win.manifest (name="odis.bs.win"). Where from does Windows get the ODIS part? Well, there's also a file called "Setup.exe.config" with the following content: <configuration> <windows> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <probing privatePath="ODIS"/> </assemblyBinding> </windows> </configuration> It looks that the program should resolve through <dir>/<privatePath>. I added a few prints here and there, and it seems that Setup.exe.config is not loaded by wine at any point. Moving odis.bs.win and odis.bs.wx to the upper folder fixes the problem, although the installation still fails after a while. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 58505] New: Odd windows management behaviour in later dev versions
by WineHQ Bugzilla 11 Aug '25

11 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58505 Bug ID: 58505 Summary: Odd windows management behaviour in later dev versions Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kg.hammarlund(a)gmail.com Distribution: --- I run a geneaology database program written for windows under wine. It runs fine on v10.0 (stable) and on dev versions up to 10.4. From v10.5 and upwards, including v1012, I'm encountering an odd issue. When opening a search window, this window opens in the background instead of on top of the main window. I then have to move or resize the main window in order to highilght the search window and fill in the search data. But this only happens the first time I open the search window. Next time it opens in the foreground. If I untick the box "Allow the window manager to control the windows" in winecfg > graphics, the search window opens expected. But this solution has its drawbacks. -- 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 57414] New: BioShock needs support for 'Generic samplers need to be lowered'
by WineHQ Bugzilla 11 Aug '25

11 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=57414 Bug ID: 57414 Summary: BioShock needs support for 'Generic samplers need to be lowered' Product: vkd3d Version: 1.13 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Using builtin d3dx9_33 and '-dx9' flag. 098c:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -5. 098c:err:d3dcompiler:D3DCompile2 Shader log: 098c:err:d3dcompiler:D3DCompile2 <anonymous>:1:371: E5017: Aborting due to not yet implemented feature: Generic samplers need to be lowered. 098c:err:d3dcompiler:D3DCompile2 1.13-654-g756b98f0 -- 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 56347] New: The Sinking City exits after Click any key to continue
by WineHQ Bugzilla 11 Aug '25

11 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=56347 Bug ID: 56347 Summary: The Sinking City exits after Click any key to continue Product: vkd3d Version: 1.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- After starting new game and loading the game shows 'Click any key to continue' which results in 0880:err:msvcrt:_wassert (L"1 <= count && count <= VKD3D_VEC4_SIZE",L"../vkd3d/libs/vkd3d-shader/vkd3d_shader_private.h",1613) vkd3d-1.10-492-gd9c68ee4 -- 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 58578] New: Hygeia Pharmacy: complains that Microsoft ReportViewer is not installed (unimplemented MsiProvideAssemblyW() ?)
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58578 Bug ID: 58578 Summary: Hygeia Pharmacy: complains that Microsoft ReportViewer is not installed (unimplemented MsiProvideAssemblyW() ?) Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: peathot(a)hotmail.com Distribution: --- Created attachment 79093 --> http://bugs.winehq.org/attachment.cgi?id=79093 Terminal output of Hygeia Pharmacy running under Wine Hygeia Pharmacy is a .NET 4 application for pharmacy retail. When the application starts up, it will check for various shared components, ending up complaining that Microsoft Report Viewer has to be installed despite already installed. Attached is the screenshot of the error. It says, "It's necessary to install an additional programed named Microsoft Report Viewer" ("มีความจำเป็นต้องติดตั้งโปรแกรมเสริมที่ชื่อว่า Microsoft Report Viewer"). Terminal output reveals 2 interesting FIXME's: ``` 0174:fixme:msi:MsiProvideAssemblyW L"Microsoft.ReportViewer.Common, Version=10.0 .0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MS IL", L"C:\\Program Files\\HygeiaPharmacy\\HygeiaPharmacy.exe.config", 0, 0, 10D7 A618, 10D7A614 0174:fixme:msi:MsiProvideAssemblyW L"Microsoft.ReportViewer.Common, Version=10.0 .0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MS IL", (null), 0, 0, 10D7A618, 10D7A614 ``` This leads me to believe that the application chokes up because it does not receive the correct path to this .NET assembly, part of MS ReportViewer 2010. --- Looking into multiple documents and into Wine itself, I _think_ it would be relatively simple to implement MsiProvideAssembly[A|W]() using facilities already implemented in Wine. Bug 58577 plays an important role on this. I actually would love to get my hands dirty, if not for 2 problems: 1. I don't actually have much time myself. 2. Many years ago, I disassembled a different component of Windows (related to MDM/management policy) in order to debug my graduating project. I forgot everything by now, and it's IMHO not related, but combined with 1. I think it's probably better to stay safe. (Can I explain some high-level idea? Will I run afoul of 2.?) A number of MSDN documents that might be useful: https://learn.microsoft.com/en-us/windows/win32/api/msi/nf-msi-msiprovideas… https://learn.microsoft.com/en-us/windows/win32/msi/assembly-registry-keys-… Also helpful is a small test program I write myself to exercise MsiProvideAssemblyW() in the same way as the application (and in a slightly different way). On Windows 11, this outputs as follow: ``` MsiProvideAssemblyW("Microsoft.ReportViewer.Common, ..." (qualified)) returns 0 Returned path (119): C:\WINDOWS\assembly\GAC_MSIL\Microsoft.ReportViewer.Common\10.0.0.0__b03f5f7f11d50a3a\Microsoft.ReportViewer.Common.dll MsiProvideAssemblyW("Microsoft.ReportViewer.Common" (unqualified)) returns 0 Returned path (119): C:\WINDOWS\assembly\GAC_MSIL\Microsoft.ReportViewer.Common\10.0.0.0__b03f5f7f11d50a3a\Microsoft.ReportViewer.Common.dll ``` On Wine, it outputs (excluding Wine's output itself): ``` MsiProvideAssemblyW("Microsoft.ReportViewer.Common, ..." (qualified)) returns 120 MsiProvideAssemblyW("Microsoft.ReportViewer.Common" (unqualified)) returns 120 ``` --- Following is the way I run Hygeia Pharmacy. Hygeia Pharmacy is a relatively complex application and requires the full .NET installation (Mono is not enough). The following commands recreate the environment from scratch: ``` export WINEARCH=win32 export WINEPREFIX=/a/new/prefix winetricks dotnet48 jet40 mdac28 wine ReportViewer.exe # sha256sum: e8ff182e202b321ac2b9245ee20c4eb659008ffb2a34cdbd3486f9da3d4c3e06 wine hygeia_trial_install.2.6.28.1.exe # sha256sum: 380085defb0af240f144d603da70d09a76c940a27a65953a9fbe3668c321b4e2 wine "C:\\\\users\\\\Public\\\\Desktop\\\\Hygeia Pharmacy.lnk" &>hygeia_pharmacy_wine_output.txt ``` --- The (trial) version can be obtained from https://www.hygeia-pharmacy.com/trial/. However, it requires a (free) registration, and the website is entirely in Thai with no English version. In order to (try to) help you with the registration, the registration page at https://www.hygeia-pharmacy.com/register/ requires the followed: 1. A chosen username ("Hygeia ID") 2. A chosen password. 3. Your full name 4. Your email. 5. A math captcha (input the equation's answer). I can't remember if there's an email verification after that step or not, because it's been a long time since I registered myself. Once logged in, https://www.hygeia-pharmacy.com/trial/ will show a big blue button for downloading the trial version. The same page will also be a smaller link for "MS Report Viewer" which is hosted by Hygeia Pharmacy themselves (if you prefer an MS link, see the end of bug 58577). -- 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 58588] New: Tokens Acquired from WTSQueryUserToken do not set the session id for the token correctly
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58588 Bug ID: 58588 Summary: Tokens Acquired from WTSQueryUserToken do not set the session id for the token correctly Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wtsapi32 Assignee: wine-bugs(a)winehq.org Reporter: katharina(a)hacked.xyz Distribution: --- A service running under NTAUTHORITY\SYSTEM may use the Windows Terminal Server API to resolve user sessions. This is also works on non-terminalservers, that is, normal computers where only one simoultaneous session is allowed. My best guess is that Windows internally treats all sessions as terminal service sessions, so this API becomes canon. If a service wants to then spawn a process attached to this user's session, so that the spawned process is able to open a window showing in the user's session, it may use CreateProcessAsUserW to do this, and supply a token to a users's Windows session. The general principle is for example documented in this stackoverflow question: https://stackoverflow.com/questions/3128017/launching-a-process-in-user-s-s… A real-world user of this mechanism is the Dassault 3DEXPERIENCE Launcher, which is unfortunately not available without purchase. The actual source of the token is not terribly important; the code I debugged uses WTSEnumerateSessions in conjunction with WTSQueryUserToken. The latter should return a token that has it's session ID set to the current users session ID; most likely 1. A reproducer for this bug is available here: https://gitlab.winehq.org/hackathi/wtsqueryusertoken-bug -- 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

← Newer
1
...
41
42
43
44
45
46
47
...
50
Older →

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 August 2025