July 2022 - Wine-Bugs - list.winehq.org

[Bug 16911] New: WriteProcessMemory() not working for memory protected by X11DRV_DIB_DoProtectDIBSection()
by wine-bugs＠winehq.org Feb. 23, 2024

Feb. 23, 2024

http://bugs.winehq.org/show_bug.cgi?id=16911 Summary: WriteProcessMemory() not working for memory protected by X11DRV_DIB_DoProtectDIBSection() Product: Wine Version: 1.1.12 Platform: PC OS/Version: Linux Status: UNCONFIRMED Keywords: patch, source Severity: minor Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com Created an attachment (id=18660) --> (http://bugs.winehq.org/attachment.cgi?id=18660) test program Hi, I have a test case here that works on WinXP but not Wine. I deliberately wrote a standalone test case because I'm not sure which unit test to put it in. It's in fact based off of dlls/kernel32/tests/virtual.c where the other WriteProcessMemory() test is. In this test case, we call CreateDIBSection() which returns a HBITMAP (hbitmap) and some memory (mem). Next, we call SetDIBits() with hbitmap. We get into X11DRV_SetDIBits(), where it calls X11DRV_DIB_Lock( physBitmap, DIB_Status_GdiMod );. This marks the memory (mem) as PAGE_NOACCESS, and leaves it in that state as SetDIBts() returns. Normally if the process tries to access it, we get a page fault that's handled by X11DRV_DIB_FaultHandler(), and everything works. However, when the test code calls WriteProcessMemory(), we talk to wineserver in NtWriteVirtualMemory(). In wine_server_call(), we do send_request(), where writev() tries to read 'mem' and fails with EFAULT. This doesn't trigger X11DRV_DIB_FaultHandler(), and WriteProcessMemory() fails. -- 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 5

[Bug 50098] New: FFXIV_Textools crashes on start
by WineHQ Bugzilla Feb. 18, 2024

Feb. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=50098 Bug ID: 50098 Summary: FFXIV_Textools crashes on start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nsextyfour(a)protonmail.com Distribution: --- Created attachment 68574 --> https://bugs.winehq.org/attachment.cgi?id=68574 I try to start FFXIV_TexTools, and then try to copy the text from the error dialog. FFXIV Textools, a modding tool for Final Fantasy XIV, will not launch in Wine. https://textools.dualwield.net/ It brings up an error window, and when I try to copy the text from it, the window disappears due to a crash. If I click 'yes', I get another error window. Clicking yes on this brings another, and then another. After the fourth, the program closes. -- 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 8

[Bug 47116] New: Indiana Jones and the Emperor's Tomb: white line
by wine-bugs＠winehq.org Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=47116 Bug ID: 47116 Summary: Indiana Jones and the Emperor's Tomb: white line Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Created attachment 64326 --> https://bugs.winehq.org/attachment.cgi?id=64326 screen captures with white lines Hello, to play Indiana Jones and the Emperor's Tomb with Wine, I know I have to: - override dll msvcrt bug 27594 - disable vertex shader 12400 But now I have a new graphic issue with Wine 4.7 (even with staging version): look at the screen captures I joined to this bug report, there are white lines. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 12

[Bug 49199] New: Wine on macOS no longer loads dylibs from /lib(64)
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=49199 Bug ID: 49199 Summary: Wine on macOS no longer loads dylibs from /lib(64) Product: Wine Version: 5.6 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gcenx83(a)gmail.com Starting from Wine-5.6 the libwine wrappers have been removed in favor of using dlopen() however this now causes component in question to no longer load embedded dylibs into /lib(64) Here’s an example; ```907aaf9e72714293909351648827e7c5aebc12a3 is the first bad commit commit 907aaf9e72714293909351648827e7c5aebc12a3 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Apr 6 11:46:10 2020 +0200 gdi32: Use standard dlopen() instead of the libwine wrappers. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/gdi32/dibdrv/opengl.c | 12 +++++------- dlls/gdi32/freetype.c | 20 ++++++++++---------- 2 files changed, 15 insertions(+), 17 deletions(-)``` Any commit doing “ Use standard dlopen() instead of the libwine wrappers.” will now experience this. Previous behavior was the ability to simply embed dylibs into /lib(64) and wine(64) would load them as needed, now rpath is required. Winehq packages will also experience this issue worse once the current embedded libraries swap to using dlopen() -- 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 20

[Bug 39859] New: WineHQ packages for wine-gecko and wine-mono
by wine-bugs＠winehq.org Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=39859 Bug ID: 39859 Summary: WineHQ packages for wine-gecko and wine-mono Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Most users of the distros we now package for are accustomed to installing wine-gecko and wine-mono from packages. We should provide them. -- 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 16

[Bug 47558] New: Ubuntu package for 4.12.1 cannot open project in Adobe Premiere Pro 2.0
by wine-bugs＠winehq.org Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=47558 Bug ID: 47558 Summary: Ubuntu package for 4.12.1 cannot open project in Adobe Premiere Pro 2.0 Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: julius.schwartzenberg(a)gmail.com CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 64946 --> https://bugs.winehq.org/attachment.cgi?id=64946 output of Wine When I run Adobe Premiere Pro 2.0 with Wine 4.12.1 in Ubuntu, I get the following dialog when trying to open a project: Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project. Rebuilding Wine myself from Git, currently the latest commit matches 4.12.1, does not show this problem. -- 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 50692] New: Office 2019 Professional Plus doesn't install
by WineHQ Bugzilla Feb. 11, 2024

Feb. 11, 2024

https://bugs.winehq.org/show_bug.cgi?id=50692 Bug ID: 50692 Summary: Office 2019 Professional Plus doesn't install Product: Wine Version: 6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: atillolann-1815(a)yopmail.com Distribution: --- Created attachment 69422 --> https://bugs.winehq.org/attachment.cgi?id=69422 Terminal Log Tried intalling Office 2019 ProPlus Retail, after the loading screen the installer crashes. Using Wine 6.2-developer Arch: x86_64 Distro: Linux Mint 19.0 Cinnamon 64 bit -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 14010] New: RivaTuner 2.09 not work ,no overclocking or sensor ability
by wine-bugs＠winehq.org Feb. 10, 2024

Feb. 10, 2024

http://bugs.winehq.org/show_bug.cgi?id=14010 Summary: RivaTuner 2.09 not work ,no overclocking or sensor ability Product: Wine Version: 1.0.0 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dj--alex(a)ya.ru RivaTuner 2.09 not work ,no overclocking or sensor ability My videocard is very loud without this program!! I and not only i, want to overclocking without BIOS VRAM rewrite. Program can be downloaded free from http://www.radeon.ru/ (Main menu left - newest version) -- 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 4

[Bug 51360] New: vkGetDeviceProcAddr invalid behavior for functions from extensions unsupported by host Vulkan instance
by WineHQ Bugzilla Feb. 9, 2024

Feb. 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=51360 Bug ID: 51360 Summary: vkGetDeviceProcAddr invalid behavior for functions from extensions unsupported by host Vulkan instance Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: loothelion(a)nvidia.com Distribution: --- I believe the below may also be true for vkGetInstanceProcAddr, but I haven't confirmed this locally. The Vulkan 1.2.182 specification states the following about the behavior of vkGetDeviceProcAddr: > The table below defines the various use cases for vkGetDeviceProcAddr and > expected return value for each case. > > The returned function pointer is of type PFN_vkVoidFunction, and must be cast to > the type of the command being queried before use. The function pointer must only > be called with a dispatchable object (the first parameter) that is device or a > child of device. > > Table 2. vkGetDeviceProcAddr behavior > > device | pName | return value > --------------------------------------------------------------------------------------- > NULL | *[1] | undefined > --------------------------------------------------------------------------------------- > invalid device | *[1] | undefined > --------------------------------------------------------------------------------------- > device | NULL | undefined > --------------------------------------------------------------------------------------- > device | core device-level Vulkan command [2] | fp[3] > --------------------------------------------------------------------------------------- > device | enabled extension device-level commands [2] | fp[3] > --------------------------------------------------------------------------------------- > any other case, not covered above | NULL > > [1] - "*" means any representable value for the parameter (including valid > values, invalid values, and NULL). > > [2] - In this function, device-level excludes all physical-device-level > commands. > > [3] - The returned function pointer must only be called with a dispatchable > object (the first parameter) that is device or a child of device e.g. > VkDevice, VkQueue, or VkCommandBuffer. Winevulkan's behavior differs from this slightly. Note the fifth row of the table uses the language "enabled extension device-level commands", this means that if a command is queried via vkGetDeviceProcAddr and isn't part of core, the extension which introduces it must be enabled for the given VkDevice object in order for vkGetDeviceProcAddr to return a valid function pointer, and otherwise it should return NULL. In order to properly conform to the Vulkan specification Winevulkan should only expose device-level commands whose extensions have been enabled. Note that applications should not be querying for Vulkan commands via vkGetDeviceProcAddr if they know the extension is not supported by the underlying implementation. However in the case of an application which does rely on this bad behavior, Winevulkan will return a function pointer to one of its thunks and then proceed to deference a null function pointer when it tries to call into the underlying host Vulkan implementation. -- 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 47521] New: digikam 6.10 crashes on start
by wine-bugs＠winehq.org Feb. 9, 2024

Feb. 9, 2024

https://bugs.winehq.org/show_bug.cgi?id=47521 Bug ID: 47521 Summary: digikam 6.10 crashes on start Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo Created attachment 64913 --> https://bugs.winehq.org/attachment.cgi?id=64913 crash output Backtrace: =>0 0x66401f0a EntryPoint+0xb6a() in qt5widgets (0x006ff4f8) 1 0x1084cf64 WXMPUtils_DuplicateSubtree_1+0x44c5d3() in libdigikamcore (0x737adae8) 2 0x10388bb9 EntryPoint+0x387818() in libdigikamcore (0x006ff5f8) 3 0x104c0cba WXMPUtils_DuplicateSubtree_1+0xc0329() in libdigikamcore (0x006ff688) 4 0x2278b630 EntryPoint+0xba28f() in libdigikamgui (0x006ffab8) 5 0x2276e7b3 EntryPoint+0x9d412() in libdigikamgui (0x006ffb98) 6 0x00404be5 _ZN7Digikam6DColor11premultiplyEv+0x15e4() in digikam (0x006ffe88) 7 0x00401382 EntryPoint+0xffffffff() in digikam (0x006fff28) 8 0x7b47e022 call_process_entry+0x11() in kernel32 (0x006fff48) 9 0x7b480acc start_process+0xeb(entry=<couldn't compute location>, peb=<couldn't compute location>) [Z:\home\austin\wine-git\dlls\kernel32\process.c:1297] in kernel32 (0x006fffd8) 10 0x7b47e02e start_process_wrapper+0x9() in kernel32 (0x006fffec) 0x66401f0a EntryPoint+0xb6a in qt5widgets: movl 0x4(%eax),%ecx austin(a)laptop:~/Downloads$ du -sh digiKam-6.1.0-Win32.exe 321M digiKam-6.1.0-Win32.exe austin(a)laptop:~/Downloads$ sha256sum digiKam-6.1.0-Win32.exe fb870263a8bb2bd178590dfacfe68110b68d8c5b0ca53606084162a1a5e42b44 digiKam-6.1.0-Win32.exe -- 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 7