https://bugs.winehq.org/show_bug.cgi?id=56334
Bug ID: 56334
Summary: Page fault when querying dinput8_a_EnumDevices
Product: Wine
Version: 9.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: leonicolas(a)gmail.com
Distribution: ---
Created attachment 76066
--> https://bugs.winehq.org/attachment.cgi?id=76066
Unhandled exception: page fault on read access to 0x00000006 in wow64 32-bit
code (0x7bd37250).
This error happens when I try to run a game I'm developing on the MMBasic For
Windows environment over Wine. I have tried different Wine versions, including
the last dev version (9.2). The error only happens if I have the gamepad
connected to the computer.
This is the MMBasic For Windows interpreter I'm using:
https://www.thebackshed.com/forum/uploads/matherp/2023-12-24_033644_MMBasic…
This is the game repo: https://github.com/leonicolas/knightmare-cmm2/
To run the interpreter environment: wine MMBasic_input.exe &> /dev/null
To run the game:
chdir"the/game/path" Usually the root folder is your Documents folder
run"km.bas"
Wine crashes with the attached backtrace after running the run"km.bas" command.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=56271
Bug ID: 56271
Summary: Free Download Manager no longer works after it updated
(stuck at 100% CPU, no visible window)
Product: Wine
Version: 9.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 75992
--> https://bugs.winehq.org/attachment.cgi?id=75992
Free Download Manager terminal output on Wine 9.1
Hello,
Free Download Manager was working until it updated and restarted itself.
I updated Wine from 9.0-rc3 to 9.1. The application was working as usual after
the Wine update. I used the menu to check for an application update and allowed
it to update. Then the application downloaded some stuff and tried to restart
and got hung.
After forcing everything to close, when I launch the application, there is a
fdm.exe process using one core at 100% and nothing more.
Regards.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55876
Bug ID: 55876
Summary: Acrom Controller Updater broken due to oleaut32
install
Product: Wine
Version: 8.19
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: ---
During installation you get a bunch of errors, terminal shows
> 0160:err:module:import_dll Loading library OLEAUT32.dll (which is needed by L"C:\\windows\\system32\\msvbvm60.dll") failed (error c000007b).
When restalling the installer, it affects that as well
> 01a4:err:module:import_dll Loading library oleaut32.dll (which is needed by L"Z:\\tmp\\ramdisk\\Updater2561installer7_0_3.exe") failed (error c000007b).
> 01a4:err:module:loader_init Importing dlls for L"Z:\\tmp\\ramdisk\\Updater2561installer7_0_3.exe" failed, status c0000135
The installer installs a native oleaut32, but even setting oleaut32 to builtin
doesn't help.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55421
Bug ID: 55421
Summary: Fallout Tactics graphics glitches only with
winehq-devel
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: darkranger_red(a)hotmail.com
Distribution: ---
The game 'Fallout Tactics: Brotherhood of Steel' is fully playable with Wine.
But recently I am not sure from which Wine version, the game shows some
noticeable graphics glitches, which the previous Wine version doesn't have. So
I uninstalled Wine from Fedora's repo, and use the WineHQ's repo instead. It
turns out that the game's graphics runs normally with winehq-stable(8.0.2), but
has some glitches with winehq-devel(8.13).
The attached screenshots show the launcher menu differences between Wine 8.0.2
and 8.13. Besides that, the in-game graphics also has more glitches with
winehq-devel, but usually happen in very short time and difficult to capture
the screenshots.
OS: Fedora Linux 38 (Workstation Edition) x86_64
Kernel: 6.4.7-200.fc38.x86_64
Uptime: 2 hours, 9 mins
Packages: 2703 (rpm)
Shell: bash 5.2.15
Resolution: 1920x1080
DE: GNOME 44.3
WM: Mutter
WM Theme: Adwaita
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: gnome-terminal
CPU: AMD FX-8350 (8) @ 4.000GHz
GPU: NVIDIA GeForce GTX 660
Memory: 5130MiB / 15932MiB
--
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.
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.msihttps://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.
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.
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.
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.
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.
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.