https://bugs.winehq.org/show_bug.cgi?id=50968
Bug ID: 50968
Summary: Indiana Jones and the Infernal Machine GOG 1.2:
Load/Save Game dialogs don't render correctly
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: pokeyprogrammer(a)yahoo.com
Distribution: ---
Created attachment 69798
--> https://bugs.winehq.org/attachment.cgi?id=69798
Console log w/ commdlg,dialog channels enabled + screen shots from Wine 6.6 and
Win10
Config:
Ubuntu 20.10
linux 5.8.0-48-generic (x86_64)
Wine 6.6 (from Ubuntu winehq-devel package)
GOG Indiana Jones and the Infernal Machine 1.2 (23840)
Store page: https://www.gog.com/game/indiana_jones_and_the_infernal_machine
Repro steps:
1. Download setup_indiana_jones_and_the_infernal_machine_1.2_(23840).exe from
GOG.
2. Run the installer from step (1) in wine.
3. Once the installer is finished, run "$HOME/.wine/drive_c/GOG\
Games/Infernal\ Machine/Jones3D.exe".
4. In the launcher that appears, click the "Resume Play" button.
5. Wait for the "Load Game" dialog to appear.
Reproducibility: always
Notes:
- I've attached screenshots of the "Load Game" dialog's appearance running
under Wine as well as Win10, in addition to a console log w/
WINEDEBUG=+commdlg,+dialog.
- In the "Load Game" dialog, I can use the TAB key to switch between controls
even though it's not rendered correctly. If I TAB to the filename box and type
in a save game filename, the game does load the file correctly and it's
playable.
- It looks like the "Jones3D.exe" that we originally launch is launching the
real game in "$HOME/.wine/drive_c/GOG\ Games/Infernal\
Machine/Resource/Indy3D.exe" and that the "Load Game" dialog is actually being
created from Indy3D.exe rather than Jones3D.exe, but launching Indy3D.exe
directly doesn't work.
- I have been able to reproduce the same issue in PlayOnMac w/ Wine 4.12.1
(19.0.0-cx) x86on64), and PlayOnLinux w/ Wine 4.12.1, 5.0, and 6.5 as well.
--
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=52644
Bug ID: 52644
Summary: Audacity: keyboard shortcut that opens dialog window
also inputs into that window
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: s_chriscollins(a)hotmail.com
Distribution: ---
In Audacity, if I use a keyboard shortcut to activate an effect, it pops up a
dialog window with the effect's settings. In Wine, however, the keyboard
shortcut that brings up the window also gets inputted into the window's active
dialog box. This does not happen on Windows.
STEPS TO REPRODUCE
1. Install and start Audacity (latest version is 3.1.3, but this bug happens in
any version I have tested).
2. Go to Edit -> Preferences... -> Keyboard.
3. Search for "amplify" and assign it the keyboard shortcut "1". Click OK.
4. Create or import some audio (you can go to Generate -> Tone to create some
audio).
5. Select the track, then press the "1" key.
RESULT
The "Amplify" effect dialog window pops up with the amplification amount set to
the shortcut key, "1".
EXPECTED RESULT
The "Amplify" effect dialog should not be receiving the previously-pressed
shortcut key as input. Instead, the amplification amount is supposed to be set
to normalize the audio to 100% volume. If you generated a tone in step 4 using
the default settings, this likely will be "1.938".
I discovered this bug because I use CTRL+SHIFT+V as the shortcut for the
Amplify effect, and in Wine, this results in a paste operation taking place
into the amplification dialog box.
--
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=52633
Bug ID: 52633
Summary: Some buttons from Free Virtual Keyboard's setting
dialog are unthemed.
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: uxtheme
Assignee: wine-bugs(a)winehq.org
Reporter: jactry92(a)gmail.com
Distribution: ---
Created attachment 71957
--> https://bugs.winehq.org/attachment.cgi?id=71957
A screenshot of the issue on Wine 7.3.
Steps to reproduce:
1. `wine FreeVK.exe`.
2. Open its setting dialog by clicking the key between the right Alt and the
right Ctrl.
These three buttons are unthemed:
"Online help..."
"About Free Virtual Keyboard 5.0.0.0..."
"About Hot Virtual Keyboard..."
--
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=48952
Bug ID: 48952
Summary: NVDA hangs on start
Product: Wine
Version: 5.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)jookia.org
Distribution: ArchLinux
Both the NVDA application and its setup menu hang due to
CoEnableCallCancellation being unimplemented, and likely hangs on shut down due
to CoDisableCallCancellation being unimplemented. Removing these function calls
in NVDA causes the program to boot with no visible issues.
--
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=48953
Bug ID: 48953
Summary: IAccessible windows lack children
Product: Wine
Version: 5.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: oleacc
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)jookia.org
Distribution: ArchLinux
Created attachment 66927
--> https://bugs.winehq.org/attachment.cgi?id=66927
Test program to print IAccessible objects on desktop
When assistive technologies iterate over all accessible objects on the desktop
using the IAccessible API Wine returns E_NOTIMPL for window objects, stopping
discovery of widgets.
--
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=48948
Bug ID: 48948
Summary: EVENT_OBJECT_FOCUS
Product: Wine
Version: 5.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)jookia.org
Distribution: ArchLinux
Created attachment 66925
--> https://bugs.winehq.org/attachment.cgi?id=66925
Test program to print events
In order for NVDA and other assistive technologies to work they need to be able
to track focus. This is done using the WinEvent hook EVENT_OBJECT_FOCUS. The
hook itself fires whenever focus is changed and contains a reference to the
window and accessibility child. Currently this is unimplemented.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=18905
Summary: Nvda In Wine
Product: Wine
Version: unspecified
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bluescale1976(a)aol.com
This is more of a feature request, I hope I completed the form correctly. I
was wondering if it would be possible to either add the screen reader NVDA in
to a default installation of Wine, or make it so that NVDA can be installed in
to Wine. NVDA would give blind Linux users access to applications in Wine. It
does not use video hooks, so it is probably the best choice for a Wine screen
reader. It is open source and can be found at:
http://www.nvda-project.org/
The installer talks, so if it could be made to work, installing it with out
sighted assistance would be no problem.
Thanks
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=48949
Bug ID: 48949
Summary: NVDA requires AccessibleObjectFromEvent for focus
events
Product: Wine
Version: 5.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: oleacc
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)jookia.org
Distribution: ArchLinux
In order to track focus NVDA hooks into the EVENT_OBJECT_FOCUS event and uses
its values to query AccessibleObjectFromEvent for the associated IAccessible
object. The current value returned crashes NVDA.
--
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=52591
Bug ID: 52591
Summary: Dragon NaturallySpeaking 15 does not install
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: susancragin(a)earthlink.net
Distribution: ---
Created attachment 71918
--> https://bugs.winehq.org/attachment.cgi?id=71918
Last 1500 lines of installation log
Dragon NaturallySpeaking 15 does not install. It hangs up right near the end
and repeats the following message:
0330:err:sync:RtlpWaitForCriticalSection section 7DD0AE80
"/var/tmp/portage/app-emulation/wine-staging-7.2/work/wine-7.2/dlls/combase/combase.c:
registered_classes_cs" wait timed out in thread 0330, blocked by 0ad4, retrying
(60 sec)
A log file is attached.
To reproduce:
Create 32-bit prefix. (This step is probably not essential, but it is a 32-bit
program, with "handles" to run 64-bit.)
Remove wine's mono. NatSpeak installs its own dotnet.
I will do any testing you request that I am capable of.
System: Gentoo.
--
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=52408
Bug ID: 52408
Summary: Number of gamepads limited and multiple gamepads
broken
Product: Wine
Version: 7.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: tomashnyk(a)gmail.com
Distribution: ---
I first discussed this here: https://forum.winehq.org/viewtopic.php?f=8&t=36088
but eventually came to a conclusion this is a bug. It has two sides:
1) Wine will only register 4 gamepads even if more are connected.
2) When multiple gamepads are connected, Wine loses atleast some of their
input.
Ad 1). I used Gamepad Tool from https://generalarcade.com/gamepadtool/ to check
how many gamepads are connected. I used (unknowingly) kbct:
https://github.com/samvel1024/kbct to create 4 virtual gamepads in addition to
my real one. I am sure there are other ways to add more gamepads, either just
connecting them physically or somehow fakeing them. With KBCT, one just needs
to add an appropriate number of devices to grab. Kbct will produce a fake
gamepad for each grabbed device, as it will list each device as being able to
emit basically all keys linux knows, including gamepad keys.
So a minimal config.yaml would be on my system like this:
- keyboards: ["Logitech K800", "AT Translated Set 2 keyboard", "Logitech MX
Vertical", "ThinkPad Extra Buttons"]
- one just needs to list some devices available when running evtest.
This bug is not about kbct - that is just a way to trigger this bug, which I
believe is presetn in Wine. Linux otherwise does not have any problem detecting
moredevices.
2) When I reduced the number of faked devices to two (and one real one), my
game (Worms WMD) would register just the left axis of the gamepad and not other
controls. Curiously, when I tried GamePad tool, it would register the presses.
No idea how Windows would behave, but I do not see a reason why the game would
not be able to use multiple gamepads.
--
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.