January 2024 - Wine-Bugs - list.winehq.org

[Bug 56129] New: Total War: Rome II d3dx11_42 darkness bug

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56129 Bug ID: 56129 Summary: Total War: Rome II d3dx11_42 darkness bug Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d-util Assignee: wine-bugs(a)winehq.org Reporter: Blisto(a)protonmail.com Distribution: --- Running Total War: Rome 2 with builtin d3dx11_42 will result in a mostly black scene when using wined3d and overly darkened shadows or AO with dxvk. Lines like this and similar can be seen in the log, but don't know whether they are relevant to the issue: 8d8:fixme:d3dx:D3DX11FilterTexture context 00B9BD28, texture 10426858, src_level 0, filter 0x3 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.

Jan. 1, 2024

[Bug 55951] AXE-Edit version 1.13.04 crashes, while v1.13.03 runs without problems

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55951 --- Comment #3 from Jörg <joerg(a)hagemann.ws> --- Created attachment 75803 --> https://bugs.winehq.org/attachment.cgi?id=75803 Dump running Axe-Edit-III-Win32-v1p13p04.exe on wine 9.0rc3 -- 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.

Jan. 1, 2024

[Bug 55951] AXE-Edit version 1.13.04 crashes, while v1.13.03 runs without problems

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55951 --- Comment #2 from Jörg <joerg(a)hagemann.ws> --- (In reply to temp82 from comment #1) > I was able to install and run 1.13.04 with wine 9.0rc3. could you retest > this with more recent wine? Hi temp82, happy new year and thanks for checking this. Unfortunately I cannot confirm that version 1.13.04 runs on wine 9.0rc3. 1.13.04 crashed immediately after starting the program. I use this command to install: WINEPREFIX="/home/xyz/.wine-axeed04" wine /home/xyz/Axe-Edit-III-Win32-v1p13p04.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.

Jan. 1, 2024

[Bug 45277] Multiple applications need Vulkan child window rendering (DxO PhotoLab, Affinity Photo, Google Earth Pro, Autodesk Fusion 360)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45277 Alexander Vereeken <Alexander88207(a)Protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Alexander88207(a)Protonmail.c | |om --- Comment #110 from Alexander Vereeken <Alexander88207(a)Protonmail.com> --- The browser of Steam (steamwebhelper.exe) seems to make also usage of child window rendering at some point. It works fine but the message still comes up. 0194:fixme:vulkan:X11DRV_vkCreateWin32SurfaceKHR Application requires child window rendering, which is not implemented yet! err: Failed to create surface [1226/231937.627:ERROR:angle_platform_impl.cc(43)] initialize(312): CreateDevice1 failed: (HRESULT: 0x8876086A) -- 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.

Jan. 1, 2024

[Bug 56101] Cheat Engine 7.5 (32bit) crashes shorty after attaching to process

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56101 --- Comment #10 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- Created attachment 75802 --> https://bugs.winehq.org/attachment.cgi?id=75802 notes, backtraces with debug symbols and modifications.txt I did some testing and got a cheatengine-i386.exe built with debug symbols. There I found the crash happens because the return address on top of the stack got overwritten with zero and therefore after the ret instructions the crash happens when address 0 is executed. Further a cheatengine-i386.exe with additional writeln's showed that on windows the SymEnumTypes is called, no SymGetTypeInfo (targetting a wine notepad.exe). A cheatengine-i386.exe with the "stdcall;" added to the SymGetTypeInfo definition did no longer crash in wine. I assume wine's dbghelp.dll is able to read the debug information in wine's dlls. Native dlls and cheatengine-i386.exe might have stripped those away, or use a format not understood by native dbghelp.dll? I tried to bring this to the Cheat Engine's developers here: https://github.com/cheat-engine/cheat-engine/issues/2789 -- 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.

Jan. 1, 2024

[Bug 52500] error with winediag (nodrv_CreateWindow)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52500 --- Comment #31 from O. Nykyforchyn <oleh.nyk(a)gmail.com> --- Created attachment 75801 --> https://bugs.winehq.org/attachment.cgi?id=75801 part of debug messages As I said above, these lines have been egrep'ped, the entire log is 166 Mb long. -- 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.

Jan. 1, 2024

[Bug 52500] error with winediag (nodrv_CreateWindow)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52500 O. Nykyforchyn <oleh.nyk(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oleh.nyk(a)gmail.com --- Comment #30 from O. Nykyforchyn <oleh.nyk(a)gmail.com> --- The issue is still present in wine-9.0-rc3 making it quite unusable for me, can't even run winecfg to create a new prefix. Tested on two laptops, one with a single integrated GPU, the other with two GPUs (intel + radeon), both with Slackware-15.0+. What is interesting, when I try to debug on a "quite created" prefix what is going on with winex11 and user32 removed from RelayFromExclude and WINEDEBUG=+relay,+module,+x11drv,+reg,+explorer winecfg 2>&1 | tee ~/wine.log egrep 'winex11|X11 Driver' wine.log > wine-winex11.log the x11drv debug channel is silent, although other ones work as extected. Initialization of winex11.drv is started and failed, no debug messages from within at all, although there is a "deeper" message that open_hkcu_key() opens 'Software\\Wine\\X11 Driver' key (see attachment), which can be done only from setup_options() in x11drv_main.c. Not working TRACEs and even ERRs for x11drv make impossible to track what goes wrong in x11drv_init(). -- 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.

Jan. 1, 2024

[Bug 56128] Genshin Impact: after changing to another window and back, input does not work anymore

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56128 9427421240(a)posteo.net changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download -- 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.

Jan. 1, 2024

[Bug 56128] New: Genshin Impact: after changing to another window and back, input does not work anymore

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56128 Bug ID: 56128 Summary: Genshin Impact: after changing to another window and back, input does not work anymore Product: Wine Version: 8.0.2 Hardware: x86-64 URL: https://genshin.hoyoverse.com/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 9427421240(a)posteo.net Distribution: --- Created attachment 75800 --> https://bugs.winehq.org/attachment.cgi?id=75800 Log After changing to another window and then back to the game (with Alt + TAB, for example), no input will be accepted anymore. Neither keyboard, mouse, nor gamepad will work until the game is restarted. After switching to another window, this will be added to the log multiple times, until returning to the game: "0238:fixme:win:NtUserGetKeyboardLayout couldn't return keyboard layout for thread 0074" There are multiple menu-options in the game that start a webbrowser, after which this issue will happen, so it is probably quite likely to happen during normal play once in a while. If i press the screenshot-key on my keyboard to access the screenshot-UI of GNOME, use it with the mouse-pointer, and then go back to the game, input will still work; this is the only exception i noticed. It is more like an overlay than a window, so i guess the focus still remains on the game while using it. Desktop-environment: GNOME (Wayland) Operating-system: Debian GNU/Linux Testing (Trixie) Wine-versions tested: 8.0.2, devel 8.18, 9.0-rc-3 Game-version: 4.3 -- 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.

Jan. 1, 2024

[Bug 52300] Oculus Setup installer claims that not enough space is available (needs IOCTL_STORAGE_GET_HOTPLUG_INFO)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52300 garagebay9(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |garagebay9(a)gmail.com --- Comment #6 from garagebay9(a)gmail.com --- Can confirm with a 9.0-rc3 test build that this fix not only gets us to the download, but the download can complete successfully and it begins the install process. Note: stopping and attempting to resume the download from a partial downloaded cache causes the program to exit as soon as it finishes loading the cache to the point where it left off. So you have to let it download fully in one pass. There are other issues inherent to the Oculus installer that cause the download to slow SIGNIFICANTLY towards the very end (less than 1kb/s in some cases). Starting a download of something else on the machine seems to improve speeds. This is a documented issue even on Windows. Once the download finishes it begins to attempt to install, and successfully copies some files (Vulkan related libraries and executables), but not the main software to the specified install directory. There is an install error of some kind at that point, that does not give a lot of details about what went wrong (there appears to be some window rendering issues unrelated to this bug causing some text to be missing). But that is much further than we have gotten previously trying to install the Oculus software under WINE. This is really encouraging progress. -- 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.

Jan. 1, 2024