July 2020 - Wine-bugs - list.winehq.org

[Bug 44016] New: Improve path handling in Open and Save dialogs
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=44016 Bug ID: 44016 Summary: Improve path handling in Open and Save dialogs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- Current open and save dialogs have large usability issues. 1 When I paste a path of a folder into it to make it open that folder in itself it doesn't work and writes an error. 2 I also expect this dialog to accept the absolute path in linux rootfs. 3 I also expect it to show a drop-down menu as in Windows. -- 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 11

[Bug 42645] New: File dialog usability
by wine-bugs＠winehq.org 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=42645 Bug ID: 42645 Summary: File dialog usability Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: freddi34(a)yahoo.de Distribution: --- When working with project files across different programs (e.g. Linux/OS X program and Windows program through Wine), users usually have to access the same locations and files. Quick file access and navigation is essential for productivity. If Wine's goal is not to be a bottom-of-the-drawer academic project, but actually useful, it must sufficiently integrate with the non-Windows desktop that its users are using. Example workflow: A 1. Native file manager (e.g. Nautilus) is opened at /home/username/folder1 2. User wants to open file1.ext from this folder in a Wine program through the file open dialog. B 1. User creates a file2.ext in a Wine program, opens the file save dialog and wants to save it in the same location (folder1). 2. File save dialog is opened at a path deep in the virtual C: drive (C:/Programs/Manufacturer/ProgramName/client/assets/.../...). The file save dialog's location may be controlled by the Windows application or where it was opened the last time. Wine's file open/save dialog has significantly worse usability than any GTK/KDE/OS X file dialog or even Windows' own. - It is more likely not opened where the user needs it (since working cross-system) - Navigation is only possible by one step up (green up arrow button) or by going multiple steps up towards the file system root (scrollable dropdown) and then navigating step by step down in the native system's file tree. - Double-click is cumbersome and leads repeatedly to accidental renamings or wrong selections. Wine's open/save dialogs should allow faster changing between commonly used locations. This should be supported through: - editable address (would allow to paste a complete path and press enter) - droppable for native paths (drag&drop a folder from a native file manager, this is commonly supported in e.g. GTK) - persistent list of recently openend locations in this WINEPREFIX While these are platform-agnostic, more comfort can be achieved by further integrating with the desktop (Gnome/KDE/OS X): - integrate with the desktop's bookmarks through Free Desktop Standard - integrate with the desktop's recent locations - (native file dialogs) -- 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 4

[Bug 35062] New: FarCry3 : graphical glitches
by wine-bugs＠winehq.org 10 Dec '23

10 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=35062 Bug #: 35062 Summary: FarCry3 : graphical glitches Product: Wine Version: 1.7.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: berillions(a)gmail.com Classification: Unclassified Created attachment 46762 --> http://bugs.winehq.org/attachment.cgi?id=46762 Graphical glitches on see Hi, There is a graphical bug when i play at FarCry3. this bug appears only when you look the sea. As you can see in the screenshot, it seems that the map is drawn in the sea. I think it's not a problem about the sun/moon light reflections on the sea, they're correctly drawn (not viewable in the screenshot) Thanks, Max -- 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 22

[Bug 23676] New: Arcanum essentially unusable due to graphics errors
by wine-bugs＠winehq.org 10 Dec '23

10 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=23676 Summary: Arcanum essentially unusable due to graphics errors Product: Wine Version: 1.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alex.richardson(a)gmx.de When playing Arcanum, the issue shown by the screenshot happens as soon as you attempt to scroll the view. It seems that it only happens when scrolling to the top, left right and down seem to be fine. I know this did not happen with older versions of Wine ~1 year ago. For testing purposes there is a demo of the game available here: http://www.terra-arcanum.com/downloads/ If you need any other information please tell me, I'm quite new to reporting bugs in Wine. -- 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 49107] New: Rise of the Tomb Raider shows a black screen in DX12 mode
by WineHQ Bugzilla 09 Dec '23

09 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=49107 Bug ID: 49107 Summary: Rise of the Tomb Raider shows a black screen in DX12 mode Product: vkd3d Version: 1.1 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: --- No crash just spamming this line: err:vkd3d_wait_for_gpu_fences: Failed to wait for Vulkan fences, vr -4. wine-5.7-209-g4e2ad334b5 -- 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 46510] New: Vkd3d is confused on optimus systems.
by wine-bugs＠winehq.org 09 Dec '23

09 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=46510 Bug ID: 46510 Summary: Vkd3d is confused on optimus systems. Product: vkd3d Version: 1.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: janarvottin(a)gmail.com Distribution: --- When on integrated card, wine crashes. When discrete card is enabled following error message is reported: fixme:vkd3d_select_physical_device: Multiple physical devices available, selecting the first one. DXVK works around this problem by selecting discrete card over integrated one. If dicrete isn't shown, integrated will be used instead. https://github.com/doitsujin/dxvk/commit/40b52758e3240700b061dd9650986a1312… Debian buster packages: libvkd3d1 (1.1-2) wine-4.0-rc6 (Debian 4.0~rc6-1) -- 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 4

[Bug 49398] New: vkd3d fails to compile against Vulkan 1.2.140 headers
by WineHQ Bugzilla 09 Dec '23

09 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=49398 Bug ID: 49398 Summary: vkd3d fails to compile against Vulkan 1.2.140 headers Product: vkd3d Version: 1.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: mike(a)fireburn.co.uk Distribution: --- Here's the compile error: In file included from /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c:20: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_private.h:964:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? 964 | struct vkd3d_pipeline_bindings pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | VK_PIPELINE_BIND_POINT_MAX_ENUM libtool: compile: x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I/var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999 -I./include -I/var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/include -I/var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/include/dummy -I/var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/include/private -Wall -pipe -std=c99 -Wdeclaration-after-statement -Wimplicit-fallthrough -Wmissing-prototypes -Wunused-but-set-parameter -Wvla -Wpointer-arith -Wl,--no-undefined -O3 -march=native -pipe -flto -c /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_main.c -fPIC -DPIC -o libs/vkd3d/.libs/vkd3d_main.o /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c: In function ‘d3d12_command_list_invalidate_root_parameters’: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c:1876:29: warning: parameter ‘bind_point’ set but not used [-Wunused-but-set-parameter] 1876 | VkPipelineBindPoint bind_point) | ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~ /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c: In function ‘d3d12_command_list_prepare_descriptors’: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c:2551:29: warning: parameter ‘bind_point’ set but not used [-Wunused-but-set-parameter] 2551 | VkPipelineBindPoint bind_point) | ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~ /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c: In function ‘d3d12_command_list_update_descriptor_table’: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c:2648:29: warning: parameter ‘bind_point’ set but not used [-Wunused-but-set-parameter] 2648 | VkPipelineBindPoint bind_point, unsigned int index, struct d3d12_desc *base_descriptor) | ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~ /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c: In function ‘d3d12_command_list_update_push_descriptors’: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c:2751:29: warning: parameter ‘bind_point’ set but not used [-Wunused-but-set-parameter] 2751 | VkPipelineBindPoint bind_point) | ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~ /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c: In function ‘d3d12_command_list_set_descriptor_table’: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c:4083:29: warning: parameter ‘bind_point’ set but not used [-Wunused-but-set-parameter] 4083 | VkPipelineBindPoint bind_point, unsigned int index, D3D12_GPU_DESCRIPTOR_HANDLE base_descriptor) | ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~ /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c: In function ‘d3d12_command_list_set_root_constants’: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/command.c:4121:29: warning: parameter ‘bind_point’ set but not used [-Wunused-but-set-parameter] 4121 | VkPipelineBindPoint bind_point, unsigned int index, unsigned int offset, | ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~ In file included from /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/device.c:19: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_private.h:964:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? 964 | struct vkd3d_pipeline_bindings pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | VK_PIPELINE_BIND_POINT_MAX_ENUM In file included from /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/resource.c:20: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_private.h:964:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? 964 | struct vkd3d_pipeline_bindings pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | VK_PIPELINE_BIND_POINT_MAX_ENUM In file included from /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/state.c:20: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_private.h:964:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? 964 | struct vkd3d_pipeline_bindings pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | VK_PIPELINE_BIND_POINT_MAX_ENUM make[1]: *** [Makefile:1167: libs/vkd3d/command.lo] Error 1 make[1]: *** Waiting for unfinished jobs.... In file included from /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/utils.c:19: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_private.h:964:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? 964 | struct vkd3d_pipeline_bindings pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | VK_PIPELINE_BIND_POINT_MAX_ENUM make[1]: *** [Makefile:1167: libs/vkd3d/device.lo] Error 1 In file included from /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_main.c:20: /var/tmp/portage/app-emulation/vkd3d-9999/work/vkd3d-9999/libs/vkd3d/vkd3d_private.h:964:54: error: ‘VK_PIPELINE_BIND_POINT_RANGE_SIZE’ undeclared here (not in a function); did you mean ‘VK_PIPELINE_BIND_POINT_MAX_ENUM’? 964 | struct vkd3d_pipeline_bindings pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | VK_PIPELINE_BIND_POINT_MAX_ENUM make[1]: *** [Makefile:1167: libs/vkd3d/resource.lo] Error 1 make[1]: *** [Makefile:1167: libs/vkd3d/state.lo] Error 1 make[1]: *** [Makefile:1167: libs/vkd3d/utils.lo] Error 1 make[1]: *** [Makefile:1167: libs/vkd3d/vkd3d_main.lo] Error 1 The patch required to get this compiling is: diff --git a/libs/vkd3d/vkd3d_private.h b/libs/vkd3d/vkd3d_private.h index 1cc7864..fa736e4 100644 --- a/libs/vkd3d/vkd3d_private.h +++ b/libs/vkd3d/vkd3d_private.h @@ -53,6 +53,7 @@ #define VKD3D_MAX_SHADER_EXTENSIONS 1u #define VKD3D_MAX_SHADER_STAGES 5u #define VKD3D_MAX_VK_SYNC_OBJECTS 4u +#define VKD3D_PIPELINE_BIND_POINT_COUNT 2u struct d3d12_command_list; struct d3d12_device; @@ -961,7 +962,7 @@ struct d3d12_command_list VkPipeline current_pipeline; VkRenderPass pso_render_pass; VkRenderPass current_render_pass; - struct vkd3d_pipeline_bindings pipeline_bindings[VK_PIPELINE_BIND_POINT_RANGE_SIZE]; + struct vkd3d_pipeline_bindings pipeline_bindings[VKD3D_PIPELINE_BIND_POINT_COUNT]; struct d3d12_pipeline_state *state; Which is slightly different to: https://github.com/d3d12/vkd3d/commit/8e7bf8a5c3e004763a62822ff2d79cf76907b… -- 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 47713] New: Control crashes at launch with vkd3d
by wine-bugs＠winehq.org 09 Dec '23

09 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=47713 Bug ID: 47713 Summary: Control crashes at launch with vkd3d Product: vkd3d Version: 1.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 65184 --> https://bugs.winehq.org/attachment.cgi?id=65184 WINEDEBUG=+vkd3d VKD3D_DEBUG="trace" output log Hello, The game has two separate executable, once for d3d11 and the second for d3d12. The game works correctly with Dx11/DXVK but crashes at launch when i want launch it with vkd3d. You can find the "WINEDEBUG=+vkd3d VKD3D_DEBUG="trace"" output log attached. The backtrace is this : Backtrace: =>0 0x00007fe4ac02bbe7 vkd3d_serialize_root_signature+0xffffffffffffffff() in libvkd3d.so.1 (0x00007fe4a4c409d0) 1 0x00007fe4ac02bdcb vkd3d_serialize_root_signature+0xffffffffffffffff() in libvkd3d.so.1 (0x00007fe4a4c409d0) 2 0x0000000003f2cd55 EntryPoint+0xffffffffffffffff() in d3d_rmdwin10_f (0x00000000198ea7e0) 3 0x0000000003f3ae50 EntryPoint+0xffffffffffffffff() in d3d_rmdwin10_f (0x000000000bbae070) 4 0x0000000003f3e485 EntryPoint+0xffffffffffffffff() in d3d_rmdwin10_f (0x000000000bbae070) 5 0x0000000002d3bf8c EntryPoint+0xffffffffffffffff() in renderer_rmdwin10_f (0x000000003590fbf0) 6 0x0000000002d3afcd EntryPoint+0xffffffffffffffff() in renderer_rmdwin10_f (0x000000003d2f5800) 0x00007fe4ac02bbe7 vkd3d_serialize_root_signature+0xffffffffffffffff in libvkd3d.so.1: movq 0x0000000000000028(%r8),%r9 -- 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 11

[Bug 46291] New: Blizzard update WoW to use DX12 and Multithread.
by wine-bugs＠winehq.org 09 Dec '23

09 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=46291 Bug ID: 46291 Summary: Blizzard update WoW to use DX12 and Multithread. Product: vkd3d Version: 1.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: eaglecomputers.ok(a)gmail.com Distribution: --- Shown below are the fixme that come from vkd3d, after the most recent Blizzard patch to World of Warcraft. Using Nvidia, driver 415.23, latest vkd3d from git, and wine-4.0-rc1-36-gec2c2f9fa0 (Staging). fixme:vkd3d_create_device: Unsupported feature level 0xc000. fixme:d3d12_device_CheckFeatureSupport: Root signature version 1_1 not supported yet. fixme:vkd3d_serialize_root_signature: Ignoring error blob 0x25f418. fixme:d3d12_root_signature_init: Ignoring root signature flags 0x1. fixme:vkd3d_serialize_root_signature: Ignoring error blob 0x25f418. fixme:d3d12_root_signature_init: Ignoring root signature flags 0x1. fixme:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1. fixme:d3d12_device_CheckFeatureSupport: Unhandled feature 0x4. fixme:d3d12_command_queue_GetPrivateData: iface 0x7e5a6230, guid {000000f0-0000-000d-c0f5-fed7c47f0000}, data_size 0x25f898, data 0x25f860 stub! Tell me how I can help, since I can test and report back usually same day. -- 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 26

[Bug 47269] New: World of Warcraft / D3D12 / Unplayable with RADV
by wine-bugs＠winehq.org 09 Dec '23

09 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=47269 Bug ID: 47269 Summary: World of Warcraft / D3D12 / Unplayable with RADV Product: vkd3d Version: 1.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 64563 --> https://bugs.winehq.org/attachment.cgi?id=64563 WoW d3d12 log Hello, i use wine-staging 4.8 + Mesa Git + LLVM 9 + vkd3d git and the game is unplayable with RADV. As you can see on the screenshot, i have a lot of graphical glitches. I have this line in the log : fixme:vkd3d_bind_heap_memory: Invalid heap offset 0x3b0000. -- 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 13