https://bugs.winehq.org/show_bug.cgi?id=57831
Bug ID: 57831
Summary: Keyboard input delayed at high event throughputs
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: inakilbss(a)gmail.com
Distribution: ---
Mashing keys quickly enough causes some games to read inputs with an increasing
delay, only being able to catch up once the mashing stops.
Example program: Touhou 11 trial
172965c20e04accf7932d45918f01a60abf5ee67 th11tr002a_setup.exe
http://mirror.studio-ramble.com/upload/535/200806/th11tr002a_setup.exe
(run with LANG="ja_JP.UTF-8" to avoid mojibake)
Once installed, custom.exe can be used to select the input polling method
(first option, bottom right button to save). Enabling it will force
GetKeyboardState to be used, while disabling it will allow DirectInput use,
which suffers less from the issue.
Test procedure:
- Open th11.exe
- Send around 100 input events per second, including Z presses but no X, either
with a macro or by pressing one's hands into the keyboard repeatedly, until
gameplay begins, and the player respawns after being hit by a bullet.
Correct behavior:
The player keeps shooting for a fraction of a second after Z is last released.
Actual behavior:
The player keeps shooting for a few seconds after Z is last released,
indicating a backed up input queue.
Windows behavior:
While I do not have a Windows setup at the ready, I have heard a report of
120hz macros working fine under Windows in games reading inputs with GKS.
--
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=57829
Bug ID: 57829
Summary: Links 2003 suffers Video related hangs and crashes
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dwg(a)australiamail.com
Distribution: ---
Created attachment 78037
--> https://bugs.winehq.org/attachment.cgi?id=78037
Captued hang
Hi,
Problem Description:
Links 2003 is working nicely under Wine however I have to take action to limit
the amount of shared memory that Wine is using for the Graphics with the
Embedded GPU.
Environment -
Hardware:
Acer Aspire Notebook E5-575G Gen 7 i5-7200U processor, 16GB Memory, 512GB SSD,
1TB HDD.
Intel HD 620 embedded graphics
Software:
Linux Mint 21.3
Wine 10.1
Links 2003, 1.07 Update
Commentary:
I have found that I have to severely restrict the amount of shared memory
allocated for Video to 128MB in Wine, using the parameter VideoMemorySize.
Set any higher than this and I see issues:
- If the parameter is set to 256MB the Links program hangs and has to be
terminated
- If the parameter is set to 512MB I get the attached crash from Links.
As an aside with Wine 10.1 on an older i3 Gen 3 desktop system with Intel 2500
embedded graphics running Mint 21.3, the higher VideoMemorySize parameters
works and also appears to help to improve graphic performance, previous
versions of Wine up to 10.0 on this system exhibited the same problem as on the
notebook.
--
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=57815
Bug ID: 57815
Summary: Splinter Cell (2002): crashes when changing game
resolution when used with DXVK
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.penalized(a)proton.me
Distribution: ArchLinux
Created attachment 78025
--> https://bugs.winehq.org/attachment.cgi?id=78025
output log
When I change the game resolution via the settings menu, the game crashes.
You can also crash when you start the game (right after the introductory
video). Just change the game resolution via the SplinterCellUser.ini
configuration file:
Resolution=1920x1080
This behavior only happens when used with DXVK. It doesn't happen with WineD3D
OpenGL (it's impossible to test with WineD3D Vulkan, as it completely breaks
the look of the game). And of course, it doesn't happen with winex11.drv
either.
- The game was installed via CD-ROM and is up to date with the latest update
(v1.3).
- I use labwc/wlroots as WM.
- Although I'm on Arch Linux, I compile wine manually with these options:
./configure --prefix=/usr --enable-archs=i386,x86_64 --enable-win64. So I'm
using the new WoW64 mode, but this behavior also happens in normal wine.
--
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=57138
Bug ID: 57138
Summary: Unhandled exception after printing a page in Approach
Product: Wine-staging
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 77043
--> https://bugs.winehq.org/attachment.cgi?id=77043
Unhandled exception
Fedora 40
wine-staging-9.15-2.1.x86_64
Lotus Approach N99.8.0208.0800 (Smart Suite)
I have a script set up in Approach to switch from my main page to an envelope
form, print the envelope, then return to the main page.
If I manually switch to the main page, and envelope prints fine. I have no
problem manually switching back to the man page after the print.
If I use the script, the envelope prints, then Approach crashes with a Wine
"Unhandled exception error". This was never an issue under Wine 6. Please see
the attachment.
--
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=57776
Bug ID: 57776
Summary: Wine Approach startup crash
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
Distribution: ---
SmartSuite-N99.8.0208.0800
Fedora 41
wine-stable-10.0.0-1.1.x86_64
winehq-stable-10.0.0-1.1.x86_64
Wine Approach startup crash:
wine approach.exe
Error on LSIOpen, or
"Couldn't load the Lotus Dialogs DynaLink"
wine: Unhandled page fault on read access to 00000024 at
address 1660170C (thread 0144), starting debugger...
Show Detains on crash reporter:
Unhandled exception: page fault on read access to 0x00000024 in
wow64 32-bit code (0x1660170c).
This is due to Wine not using lotus' paths correctly (from the registry).
Work Around:
$ cd ~/.wine/drive_c/lotus
$ mkdir jumble
$ cp -R approach/* jumble/.
$ cp -R compnent/* jumble/.
Simple start:
$ wine ~/.wine/drive_c/lotus/jumble/approach.exe
Fancy start:
$ bash -c "cd $HOME/.wine/drive_c/lotus/jumble; wine explorer
/desktop=Approach_`date +%%H:%%M:%%S`_1680x1050,1680x1050 ./approach.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=57783
Bug ID: 57783
Summary: Approach will not run in a virgin 10.0 wineprefix
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
Distribution: ---
Created attachment 77980
--> https://bugs.winehq.org/attachment.cgi?id=77980
debugg message on crash
What a disaster! Please correct. I need my accounting system back.
SmartSuite-N99.8.0208.0800
Fedora 41
wine-stable-10.0.0-1.1.x86_64
winehq-stable-10.0.0-1.1.x86_64
Lotus Approach will not run in a fresh WINEPREFIX under WineHQ Stable 10.0,
unless you have leftover stuff from a prior wine install. But that would not
be a fresh WINEPREFIX.
Both Approach and WordPro were selected on a customer install and a fulkl
install too after wiping the .wine directory and starting fresh
The following error occurs at the end of installation from the smart suite ISO.
regedit: Unable to open the registry key
'HKEY_CURRENT_USER\Software\Lotus\SmartSuite'.
and
regedit: Unable to open the registry key
'HKEY_CURRENT_USER\Software\Lotus\ScreenCam'.
Only Approach and WordPro were selected on a customer install.
When starting Approach:
$ cd /home/todd/.wine/drive_c/lotus/approach
$ wine ./approach.exe
The following pop occurs
"Lotus Approach: Couldn't load Lotus Dialog DynaLink"
Pressing okay, opens a Program Error box and presents this error in the command
line:
wine: Unhandled exception 0xe06d7363 in thread 24 at address 7B5F7448
(thread 0024), starting debugger...
I will attach the full debug message message.
I have one for one checked a qemu-kvm Windows 10 install of Approach against my
wine registry and they are identical
Many thanks
-T
--
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=57816
Bug ID: 57816
Summary: Splinter Cell: Pandora Tomorrow (2004): crashes when
changing game resolution when used with DXVK
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.penalized(a)proton.me
Distribution: ArchLinux
Created attachment 78026
--> https://bugs.winehq.org/attachment.cgi?id=78026
output log
When I change the game resolution via the options menu, the game crashes.
You can also crash when you start the game (right after the introductory
video). Just change the game resolution via the SplinterCell2.ini configuration
file:
WindowedViewportX=1600
WindowedViewportY=1200
and the SplinterCell2.ini configuration file:
Resolution=1600x1200
This behavior only happens when used with DXVK. It doesn't happen with WineD3D
OpenGL (it's impossible to test with WineD3D Vulkan, as it completely breaks
the look of the game). And of course, it doesn't happen with winex11.drv
either.
- The game was installed via CD-ROM and is up to date with the latest update
(v1.31).
- I use labwc/wlroots as WM.
- Although I'm on Arch Linux, I compile wine manually with these options:
./configure --prefix=/usr --enable-archs=i386,x86_64 --enable-win64. So I'm
using the new WoW64 mode, but this behavior also happens in normal wine.
--
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=53847
Bug ID: 53847
Summary: NfRemote: mouse input ignored
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thelen(a)radiomankato.com
https://www.telosalliance.com/uploads/Omnia%20Products/Software/NfRemote.exe
Say hello to nfremote. It's a little piece of software used to administer a
particular manufacturer's equipment, commonly used at radio and TV stations.
I can confirm it has, and does, work fine under Wine 2.21 - just tested today
on a MacBookPro8,1 running the official binaries
(https://dl.winehq.org/wine-builds/macosx/pool/winehq-staging-2.21.pkg) under
OS 10.13.6.
Meanwhile, I have a new Mac (MacBookPro16,2 - Intel-based), on which I’ve
deployed Wine 7.0 via homebrew under OS 12.6.1.
There I can start nfremote just fine... but it ignores my mouse input.
If I were to start it with the command-line argument "run", it presents me with
a window where both keyboard and mouse input are accepted; there I can type in
the text fields, so I know it's responsive. But when I hover the cursor over
buttons, they do not 'light up’ to indicate such. And when I click, nothing
happens.
Even in years past, I found that newer versions of Wine exhibited the issue I
describe below, so I simply never updated beyond 2.21. Wonder if this might be
a long-undiscovered regression of some sort?
--
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=57821
Bug ID: 57821
Summary: Formlabs PreForm: Balck loading screen
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: skala.antonin(a)gmail.com
Distribution: ---
Created attachment 78032
--> https://bugs.winehq.org/attachment.cgi?id=78032
Wine standart output
Hello, when I start Formlabs PreForm tool for slicing 3D models for printer,
initial loading window is solid black so information about loading progress is
not visible. Running on Ubuntu 24.10 trough Xwayland. Behavior is same for Wine
9.??-10.1
It can be obtained there: https://formlabs.com/eu/software/preform/ (free -
just ask some questions, no registration no SN of device needed)
--
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=57459
Bug ID: 57459
Summary: Wine Regedit and Wine Control don't minimize and
become unresponsive
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: agarplayerarlon(a)gmail.com
Distribution: ---
Created attachment 77457
--> https://bugs.winehq.org/attachment.cgi?id=77457
video of the issue
I've attached a video of the issue
Basically those apps instead of minimizing they compress and become
unresponsive afterwards
--
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.