wine-bugs September 2024

wine-bugs@winehq.org

1 participants
680 discussions

[Bug 52622] New: Crash of `lib` test from `windows-rs` due missing implementation of `d3dcompiler_47.dll.D3DCreateLinker`
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=52622 Bug ID: 52622 Summary: Crash of `lib` test from `windows-rs` due missing implementation of `d3dcompiler_47.dll.D3DCreateLinker` Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- This test pass on Windows 10 Failures ``` running 1 test test test ... FAILED failures: ---- test stdout ---- wine: Call from 000000007B0123DE to unimplemented function d3dcompiler_47.dll.D3DCreateLinker, aborting wine: Unimplemented function d3dcompiler_47.dll.D3DCreateLinker called at address 000000007B0123DE (thread 0130), starting debugger... ``` Rust for Windows can be installed via https://forge.rust-lang.org/infra/other-installation-methods.html or directly https://static.rust-lang.org/dist/rust-1.59.0-x86_64-pc-windows-gnu.msi https://raw.githubusercontent.com/microsoft/windows-rs/master/crates/tests/… Steps to reproduce git clone https://github.com/microsoft/windows-rs.git cd windows-rs git checkout 9965e3c44829d0c86b2d9d2b3c5338376f158bde cd crates/tests/lib/ wine cargo test -- 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 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 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 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

[Bug 44467] New: South Park The Fractured But Whole: Crashes on startup
by wine-bugs＠winehq.org 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=44467 Bug ID: 44467 Summary: South Park The Fractured But Whole: Crashes on startup Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: k.haoz(a)zoho.com Distribution: --- Created attachment 60410 --> https://bugs.winehq.org/attachment.cgi?id=60410 Backtrace when trying to start the game through Steam. The game crashes when trying to start it through the Steam client. -- 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 14

[Bug 50064] New: A transparent Agent.exe window is shown when Battle.Net launches
by WineHQ Bugzilla 15 Nov '24

15 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=50064 Bug ID: 50064 Summary: A transparent Agent.exe window is shown when Battle.Net launches Product: Wine-staging Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Regression SHA1: 3cea972271b4529e332c75b06f902c80e7de1798 Distribution: ArchLinux Since 3cea972271b4529e332c75b06f902c80e7de1798 (Rebase against f4a66ad257df4605e73dfea792eec55a70a04e84) and with all later staging commits, including 5.20 release, when you launch Battle.Net (a client for Blizzard games), a transparent Agent.exe is shown. Normally, there shouldn't be any window shown for Agent.exe at all. With staging commit b49e8743866224df57eb1032b6c63c999b28c808 and older, the issue cannot be reproduced. Mainline wine (5.20) doesn't have this issue, and 8d04884c1f6aa6b21435130e42978fdeac06df55 (Updated winex11.drv-Query_server_position patchset …), which was supposed to fix this, had no effect. More than that, using a build with that patchset disabled did not get rid of the issue. -- 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 56139] New: vbscript: Dictionary does not allow storing Undefined
by WineHQ Bugzilla 14 Nov '24

14 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=56139 Bug ID: 56139 Summary: vbscript: Dictionary does not allow storing Undefined Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: francisdb(a)gmail.com Distribution: --- Example code below, min the commented KEY1 const Dim pinEvents Set pinEvents = CreateObject("Scripting.Dictionary") 'Const KEY1 = "one" pinEvents.Add KEY1, "hello" WScript.Echo pinEvents(KEY1) WScript.Echo pinEvents(Undefined) Prints on windows [Running] cscript //Nologo "test.vbs" hello hello [Done] exited with code=0 in 0.057 seconds On Linux we get no output wine cscript ./test.vbs This is because the code ends up in a FIXME section at https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/scrrun/dictionary.c#… -- 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 10

← Newer
1
...
28
29
30
31
32
33
34
...
68
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 September 2024