wine-bugs November 2024

wine-bugs@winehq.org

1 participants
557 discussions

[Bug 56367] New: Tomb Raider 3 GOG crashes at start
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=56367 Bug ID: 56367 Summary: Tomb Raider 3 GOG crashes at start Product: Wine Version: 9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: dkk089(a)gmail.com Distribution: --- Created attachment 76108 --> https://bugs.winehq.org/attachment.cgi?id=76108 Tomb3.exe backtrace with Wine 9.3 Tomb Raider 3 GOG crashes in Wine 9.3 with the attached backtrace. Last known working version in AppDB is Wine 4.2. Working upwards from that identified Wine 5.7 as the last working release, and bisecting between 5.7 and 5.8 identified commit 100ca518055c0e9edb68aa370f15a2768cf2c74f as the cause. Reverting this commit from current master (1b32ac45f821ee1fe06a3dc4f903a81a190216c7) makes the game work normally. Tested with Windows version set to 98, WINEARCH is win32. This is also reproducible with the demo version available at https://archive.org/details/TombRaiderIiiAdventuresOfLaraCroftDemo . -- 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 56357] New: Zero sized writes using WriteProcessMemory succeed on Windows, but fail on Wine. testcase source
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=56357 Bug ID: 56357 Summary: Zero sized writes using WriteProcessMemory succeed on Windows, but fail on Wine. testcase source Product: Wine Version: 9.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: admin(a)sewer56.dev Distribution: --- Created attachment 76082 --> https://bugs.winehq.org/attachment.cgi?id=76082 Precompiled sample C program. [ testcase source ] Zero sized writes using WriteProcessMemory succeed on Windows, but fail on Wine. Build the following program: ```c #include <windows.h> #include <stdio.h> int main() { // Allocate a buffer in memory char* buffer = (char*) VirtualAlloc(NULL, 1024, MEM_COMMIT | MEM_RESERVE, PAGE_READWRITE); if (buffer == NULL) { printf("Memory allocation failed\n"); return 1; } // Sample data to write (not actually used due to 0-byte length) const char* data = "Sample data"; SIZE_T writtenBytes = 0; // Get a handle to the current process HANDLE processHandle = GetCurrentProcess(); // Attempt to write memory with 0 byte length BOOL result = WriteProcessMemory(processHandle, buffer, data, 0, &writtenBytes); if (result == FALSE) { printf("WriteProcessMemory failed: %lu\n", GetLastError()); } else { printf("WriteProcessMemory succeeded, but 0 bytes were written.\n"); } VirtualFree(buffer, 0, MEM_RELEASE); return 0; } ``` Commandline: ``` x86_64-w64-mingw32-gcc write_process_memory.c -o write_process_memory.exe -lkernel32 ``` When running on Linux, this prints `WriteProcessMemory failed: 87`. When running on Windows, this succeeds `WriteProcessMemory succeeded, but 0 bytes were written`. Tested on x86_64 Archlinux using latest git version of Wine (wine-9.2-286-g232b18d820e). ----------- Extra Notes: I encountered this bug while unit testing a Rust DLL Injection library against Wine: https://github.com/OpenByteDev/dll-syringe/pull/19 -- 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 6

[Bug 55619] New: VOCALOID AI Shared Editor v.6.1.0 crashes with System.Management.ManagementObject object construction
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=55619 Bug ID: 55619 Summary: VOCALOID AI Shared Editor v.6.1.0 crashes with System.Management.ManagementObject object construction Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: theboomtnt46(a)gmail.com Distribution: --- Created attachment 75156 --> https://bugs.winehq.org/attachment.cgi?id=75156 Crash log VOCALOID AI Shared Editor v.6.1.0 crashes while initializing. Logs attached. wine-8.16 (Staging) kubuntu linux 23.04 -- 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 51957] New: Program started via HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths should also be started if extension ".exe" is missing
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=51957 Bug ID: 51957 Summary: Program started via HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths should also be started if extension ".exe" is missing Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: NEW Keywords: source Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 70937 --> https://bugs.winehq.org/attachment.cgi?id=70937 possible patch Hi, I found this as installer of adobe digital editions is failing in chocolatey. First autohotkey is installed, i guess to press some button from license agreement. After that script tries to install adobe digital editions but fails at a line: $ahkProc = Start-Process -FilePath 'AutoHotKey' ` -ArgumentList $ahkRun ` -PassThru Autohotkey is never started as this fails. I tested on windows and then both: Start-Process -FilePath 'AutoHotKey' and Start-Process -FilePath 'AutoHotKey.exe' succeed. In wine only the last one succeeds. Attached a patch that fixes this; Maybe needs more error checking? Hints for improvement welcome; Additional note: due to install-script for autohotkey following key is present: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\AutoHotkey.exe] @="C:\\Program Files\\AutoHotkey\\AutoHotkey.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.

1 9

[Bug 57408] New: Windows Movie Maker doesn't render license dialog properly
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57408 Bug ID: 57408 Summary: Windows Movie Maker doesn't render license dialog properly Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 77393 --> https://bugs.winehq.org/attachment.cgi?id=77393 Screenshot Followup to bug 57403 and bug 57407. First workaround those issues. (Install in win7 mode and run with the patch linked in bug 57407) Steps to reproduce - Download and extract the ISO (you only need the "en" and "neutral" folders) - Enter the "en" folder and run the setup, install only Windows Movie Maker and Photo Gallery - Run MovieMaker.exe (.wine/drive_c/Program Files (x86)/Windows Live/Photo Gallery You should now be showing the "Microsoft Service Agreement". It's hard to click accept, since the button is invisible. If you click around the bottom right you dismiss/confirm the dialog though. Keep in mind that once you dismissed the license dialog it won't be shown again. -- 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 57359] New: Multiple games failed to launch in DX12 mode (SILENT HILL 2 (2024), Sumerian Six)
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57359 Bug ID: 57359 Summary: Multiple games failed to launch in DX12 mode (SILENT HILL 2 (2024), Sumerian Six) Product: vkd3d Version: 1.13 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: gmascellani(a)codeweavers.com Regression SHA1: 080f25c5839f8fe3ee8b082143cfff66b2497eb5 Distribution: --- Spamming with 'err:shader_dst_param_io_normalise ../vkd3d/libs/vkd3d-shader/ir.c:1663: Unreachable code reached.' -- 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 57422] New: Winecfg DPI issue with games
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57422 Bug ID: 57422 Summary: Winecfg DPI issue with games Product: Wine Version: 9.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: LiveFreeDead(a)hotmail.com Distribution: --- I have an NVIDIA card and a 4k screen To make my wine apps readable I use winecfg Graphics tab and set the DPI to 192, which works great for windowed desktop apps, but as soon as I run a game, it only shows the top left of my game and crops the mouse area even smaller than that. I changed the DPI back to 96 (default) and they work as expected/intended. This even occurs if I use a virtual desktop. The other issue with 4k screens on NVIDIA is it can't mode set at all, I need to preset the mode using xrandr and pass the new res to the virtual desktop. If I leave it to change the mode itself, 8 get a black screen and it powers the screen off. I can get the terminal back by pressing ctrl + alt + F2. Or get the login screen with ctrl alt backspace. But nothing else I do can change the mode back or turn the screen back on. So to be clear, I need to sety wine DPI to 96dpi and preset my screen res to run games (full screen). I do not get the same issue on my NVIDIA graphics laptop and I don't on AMD graphics. Just my 3060to and a 4k screen. I no longer have a 1080p screen to test if that works. But changing my desktop to 1080p doesn't fix things except for games that are 1080p. 800x600 and 1024x768 will cause the black screen issue. I noticed that wine v9.0 (mint v22 default) doesn't have the doi glitch 9ny 4k screen. It does still have the black screen bug if I don't pre modest. -- 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 52159] New: 64-bit cygwin gdb.exe and python3.8.exe fail to run
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=52159 Bug ID: 52159 Summary: 64-bit cygwin gdb.exe and python3.8.exe fail to run Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 71205 --> https://bugs.winehq.org/attachment.cgi?id=71205 details.txt This issue can be seen if the workarounds for bug #47808 got applied first. Both gdb.exe and python3.8.exe fail in the python initialisation. As far as I see it python allocates 8 bytes for a sem_t structure. This uninitialized struct is given to sem_init which checks if this is a previously initialized semaphore by checking with verifyable_object_isvalid. This check happens inside a __try/__endtry [2] [3]. That way we end up in RtlUnwindEx, which inspects NtCurrentTeb()->Tib.ExceptionList. Unfortunately this list finally contains a pointer to the initial stack, which cygwin deallocated before [1]. See details.txt. -- 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 13

[Bug 57354] New: HeidiSQL 7.0 shows black window
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57354 Bug ID: 57354 Summary: HeidiSQL 7.0 shows black window Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 77325 --> https://bugs.winehq.org/attachment.cgi?id=77325 Screenshot Bisected to commit ae3384fe2f9e1e5283fa2b8881251b4716c8487d Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Aug 5 13:05:46 2024 +0200 win32u: Always use the dummy surface if a surface isn't needed. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=57033 To reproduce: - Work around bug 57033 (revert 5924ab4c5155d97f4b23a33e97258c1ec382ea02) - Download https://web.archive.org/web/20130612145220/http://heidisql.googlecode.com/f… - Extract and run the exe - Click the new button - you now get a black window that updates when you hover/click elements -- 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 52715] New: wine segfaults on asahi linux (apple M1 hardware, linux kernel/userland)
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=52715 Bug ID: 52715 Summary: wine segfaults on asahi linux (apple M1 hardware, linux kernel/userland) Product: Wine Version: 7.4 Hardware: aarch64 OS: Linux Status: NEW Keywords: source Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian The GCC Compile Farm has a m1 machine running asahi linux, so I tried building wine. While it compiles (note: most optional deps and freetype were missing), the resulting binary segfaults, even for --version/--help: austin@gcc103:~/wine$ file loader/wine loader/wine: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=c47e4c565e49cc68efce4887d600f06d749670e0, for GNU/Linux 3.7.0, with debug_info, not stripped austin@gcc103:~/wine$ ./loader/wine --version Segmentation fault austin@gcc103:~/wine$ ./loader/wine --help Segmentation fault austin@gcc103:~/wine$ uname -a Linux gcc103.fsffrance.org 5.17.0-rc7-asahi-next-20220310-g4a4f4ec03834 #1 SMP PREEMPT Sat Mar 12 18:16:45 UTC 2022 aarch64 GNU/Linux austin@gcc103:~/wine$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/11/lto-wrapper Target: aarch64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 11.2.0-18' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=aarch64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libquadmath --disable-libquadmath-support --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --enable-fix-cortex-a53-843419 --disable-werror --enable-checking=release --build=aarch64-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=4 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.2.0 (Debian 11.2.0-18) austin@gcc103:~/wine$ ~/llvm-mingw-20211002-ucrt-ubuntu-18.04-aarch64/bin/aarch64-w64-mingw32-gcc --version clang version 13.0.0 (https://github.com/llvm/llvm-project.git d7b669b3a30345cfcdb2fde2af6f48aa4b94845d) Target: aarch64-w64-windows-gnu Thread model: posix InstalledDir: /home/austin/llvm-mingw-20211002-ucrt-ubuntu-18.04-aarch64/bin Note that the machine uses a 16k stack size instead of 4k, which may be at fault: https://github.com/AsahiLinux/docs/wiki/Software-known-to-have-issues-with-… -- 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 23

← Newer
1
...
43
44
45
46
47
48
49
...
56
Older →

Jump to page:

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 November 2024