https://bugs.winehq.org/show_bug.cgi?id=51537
Bug ID: 51537
Summary: Mouse does not work in civilization VI
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: voker57(a)gmail.com
Distribution: ---
Created attachment 70376
--> https://bugs.winehq.org/attachment.cgi?id=70376
complete log
Mouse does not work in Sid Meier's Civilization VI, menu loads but it is not
possible to do anything further.
This comment https://bugs.winehq.org/show_bug.cgi?id=49315#c9 suggests a cause
of this bug.
--
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=57635
Bug ID: 57635
Summary: Battle.net Launcher invisible/black with the Wayland
driver
Product: Wine
Version: 10.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)xarov.net
Distribution: ArchLinux
Created attachment 77764
--> https://bugs.winehq.org/attachment.cgi?id=77764
Black window with Wayland driver
Works fine with the X11 driver. Is completely black with the Wayland driver.
--
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=57697
Bug ID: 57697
Summary: PeekMessage + GetMessage issue with multiple windows
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: oldcastlehq(a)protonmail.com
Distribution: ---
Created attachment 77885
--> https://bugs.winehq.org/attachment.cgi?id=77885
Video showing the issue.
When you drag-drop a color MuLab starts a modal event loop and polls the
PeekMessage + GetMessage functions for mouse move and mouse click events. When
the mouse moves over different windows this should deliver mouse move events
with the respective window handle of the window under the mouse. If there are
several floating windows then Wine doesn't deliver such events, which is odd.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=57637
Bug ID: 57637
Summary: Regression: Crash on exit in Age of Empires
Product: Wine
Version: 9.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dplay
Assignee: wine-bugs(a)winehq.org
Reporter: krkos(a)mail.muni.cz
Distribution: ---
Created attachment 77765
--> https://bugs.winehq.org/attachment.cgi?id=77765
AoE exit crash backtrace
The bug affects original Age of Empires with UPatch HD 1.2 Release 3.
Upon program exit, it crashes with page fault on write access to 0x00000005,
see attached backtrace.
This was bisected to be caused by 490d5f0fcf8556548743ad65a2a9951c2f503809
"dplayx: Merged IDirectPlayLobby/2A in to IDirectPlayLobby3A.", which seems
strange as the backtrace indicates something audio related, but was reproduced
repeatedly.
The bug manifests on wow64 32bit (configure --enable-win64
--enable-archs=i386,x86_64), compiled with both mingw and clang. I did not test
pure 32b wine.
The bug is still present in wine 10.0-rc4.
--
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=57734
Bug ID: 57734
Summary: PHP8 Fatal Errrors
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jnewman(a)codeweavers.com
Distribution: ---
While scanning the logs, I see these fatal errors due to the upgrade of PHP8.
PHP Fatal error: Uncaught Error: Non-static method
testData::objectGetFilterInfo() cannot be called statically in
include/testData_queue.php:161
PHP Fatal error: Uncaught Error: Undefined constant "iTestingId" in
include/testData.php:972
PHP Fatal error: Uncaught TypeError: sizeof(): Argument #1 ($value) must be of
type Countable|array, null given in include/vendor.php:306
--
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=57676
Bug ID: 57676
Summary: Dn-FamiTracker 0.5.1.1: most of instrument editor is
blank
Product: Wine
Version: 10.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)pineight.com
Distribution: ---
When opening an instrument for editing, most controls in the instrument editor
don't get drawn, leaving a blank space where they should be.
Wine version: 10.0-rc5 from dl.winehq.org repository
Distribution: Xubuntu 24.04 amd64
Graphics: X.Org X Window System 7.7+23ubuntu3, Mesa Intel(R) HD Graphics 5500
(BDW GT2), Mesa 24.0.9-0ubuntu0.3
Program identifiers
Download page:
https://github.com/Dn-Programming-Core-Management/Dn-FamiTracker/releases/t…
SHA-1 hashes:
97024e66beed59c61580ea4a23bea25185440323
/<redacted>/Dn-FamiTracker_v0511_x64_Release.7z
201990bcb93c72d47061fe69eb3fc6599518d5e1 /<redacted>/Dn-FamiTracker.exe
Steps to reproduce:
1. Download Dn-FamiTracker_v0511_x64_Release.7z and extract it to a new folder.
2. Open Dn-FamiTracker.exe.
3. At top right is a list of instruments that begins with "[2A03] 00 -".
Double-click the "00 -" to open the instrument editor.
4. The "Instrument editor" floating window appears. It has two panes, with tabs
"2A03 settings" and "DPCM samples".
Behavior on Windows and Wine 9.x:
To the left side is an "Instrument settings" group containing a list of effects
"Volume, Arpeggio, Pitch, Hi-pitch, Duty / Noise", button "Select next empty
slot", and a combo box labeled "Sequence #". To the right is a "Sequence
editor" group with a graph, "Size: [-] 0 [+]" and a text input to enter a
volume sequence as numbers. At bottom is a piano keyboard.
Behavior on Wine 10.0-rc5:
Everything in pane "2A03 settings" other than the graph and the piano keyboard
is blank. Switching to pane "DPCM samples" and back to pane "2A03 settings"
reveals the hidden controls.
--
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=56542
Bug ID: 56542
Summary: winewayland.drv: In-game VSync capped at 59FPS on 60Hz
monitors
Product: Wine
Version: 9.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: faridzelli(a)gmail.com
Distribution: ---
The in-game VSync is capped at 59FPS in Cyberpunk 2077 on 60Hz displays. This
game in particular allows the player to adjust the VSync frame rate target, the
given options change to [59 29 19 14] as opposed to [60 30 20 15] under
XWayland.
Benchmark results:
- XWayland + VSync 60 (3 runs): 59.5FPS
- winewayland.drv + VSync 59 (3 runs): 58.4FPS
System information:
- Specs: Ryzen 5 3600 / Radeon 6700XT / 3840x2160 60Hz
- OS: openSUSE Tumbleweed
- DE: GNOME 46
- Display scaling: none
- Wine version: 9.6 (reproducible on all 9.X builds)
--
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.