https://bugs.winehq.org/show_bug.cgi?id=58038
Bug ID: 58038
Summary: Keyboard input lost after alt-tabbing in virtual
desktop
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: 30fa691d99df7d6dfe37d16fe708d603919f9fd1
Distribution: ---
After alt-tabbing out and back to the application in virtual desktop mode the
keys that you pressed appear in the terminal instead of the application.
You can run 'wine notepad' to reproduce this.
Reverting commit 30fa691d99df7d6dfe37d16fe708d603919f9fd1
fixes the problem for me.
XFCE/XFWM 4.20
wine-10.4-112-gcf6bdfd2260
--
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=57919
Bug ID: 57919
Summary: Rally Trophy: Keyboard key is not configurable
anymore, regression
Product: Wine
Version: 10.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: jettis(a)gmail.com
Distribution: ---
Created attachment 78171
--> https://bugs.winehq.org/attachment.cgi?id=78171
Log from wine version one commit before breaking
On Rally Trophy before it was possible to map keys on keyboard to an action in
game, but not anymore after commit 7b3f3d60782c63edd621353a635616f4cea029da.
Steps to reproduce:
1. install Rally Trophy demo
2. ensure that you don't have other input devices connected than keyboard and
mouse, otherwise this breaks even before that commit
3. start Rally Trophy
4. go to device configuration
5. set key 's' to have action 'shift up'
6. save device configurations
7. go to in game with manual transmission
8. press key 's' in game and notice that gear does not change
--
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=57940
Bug ID: 57940
Summary: ntoskrnl.exe tests can trigger BSOD
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: amorozov(a)etersoft.ru
Created attachment 78188
--> https://bugs.winehq.org/attachment.cgi?id=78188
MEMORY.DMP analysis with WinDbg
I have seen BSOD on Windows 10 Pro 1709 x64, Windows 10 Pro 22H2, Windows 11
Home 21H2 x64.
On Windows 10 testsigning was enabled with
bcdedit -set testsigning on
Windows 11 was loaded without driver signature check.
--
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=57943
Bug ID: 57943
Summary: Critical program error in CorelDraw 2024 Setup.exe
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: d.astra(a)yopmail.com
Distribution: ---
Created attachment 78189
--> https://bugs.winehq.org/attachment.cgi?id=78189
The crash dump from CorelDraw 2024 Setup.exe
I manually downloaded the real CorelDraw Setup (not the CDGS2024.exe, which
gets a connection timeout while trying to download from the corel servers) to
install the program. Neither the Setup.exe in the root directory
(CorelDRAWGraphicsSuite2024Installer), nor the Setup_x64.msi work. They crash
nearly instantly with a critical error. I provide the crash dump from the main
Setup.exe, as both dumps are the same.
--
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=58047
Bug ID: 58047
Summary: Videos in (game) Assault Spy Either Don't Display or
Do but Incorrectly
Product: Wine
Version: 10.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nekoNexus(a)protonmail.ch
Distribution: ---
Created attachment 78303
--> https://bugs.winehq.org/attachment.cgi?id=78303
Vanilla Wine 10.4 Log
Distro: Gentoo Linux (x86_64)
Desktop Environment: KDE Plasma 6.2.5 (Wayland)
CPU: Ryzen 3700X @ 4.98 GHz
RAM: 32GBs @ 3600 MHz
GPU: AMD RX 7800 XT
Mesa Version: 25.0.2
Game Version: 4.18.3.0 (latest GOG release, as of writing)
-----
Many videos in the game don't display properly.
Namely: the main menu video plays as a black screen if you wait a short period
of time without pressing any keys (audio plays but there's no video), and many
in-game videos show their content as seemingly offset (some of it can be seen
when it happens but most of it is not visible due to being out of frame) and
interlaced like as if shown on a bad CRT display. This is immediately apparent
when the game shows its first tutorial, and later also easily reproducible when
viewing attack unlock options at upgrade stations and in the game's pause menu
to view what is currently unlocked. What's strange about this, though, is that
some (a minority) of videos do play properly while most don't.
I've also noticed that when this happens, this pops up in Wine's log:
(wine:26205): GStreamer-Video-CRITICAL **: 21:52:01.667:
gst_video_info_from_caps: assertion 'gst_caps_is_fixed (caps)' failed
I'm not sure if this is the only issue involved, but I figured it was worth
noting.
--
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=58044
Bug ID: 58044
Summary: Realm Grinder freezes/crashes after a very long run
Product: Wine
Version: 10.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
Created attachment 78299
--> https://bugs.winehq.org/attachment.cgi?id=78299
output of two failed runs
This I strongly suspect is a regression, yet I can't really pin down the time
when this started happening. The problem happens with little to no human
interaction, yet the timeframes make it unreasonable to actively reproduce.
I suspect it started around 10.0 release, but with a -/+ 2 months margin (so
close to useless).
Anyway, what's the problem ?
If Realm Grinder is run for long enough (but 'long enough' here is measured in
*days*), it tends to eventually either freeze with a completely black window or
crash with an X server error.
The attachment has output of two such runs, second chunk is when it just froze,
the first when it crashed.
'fixme:d3d:swapchain_blit_gdi Using GDI present.' at the end of both seems to
be the moment the problem triggers.
It seems to be some kind of a resource leak, but it doesn't affect any other
apps running besides it, not even those run by wine.
No user action is really required to trigger this - I've seen it freeze after a
desktop switch, I've seen it crash when the window was just displayed, but not
really interacted with.
(Realm Grinder here is still at v4.2.27.0, though I'll likely update it shortly
for Easter event)
--
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=58056
Bug ID: 58056
Summary: vbscript: Directly indexing a Split returns Empty
Product: Wine
Version: 10.4
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: ---
test.vbs
Dim s: s = "1;2"
Dim a: a = Split(s, ";")(0)
Wscript.Echo "a: " & TypeName(a)
Wscript.Echo "a = " & a
Dim b: b = Split(s, ";")
Dim c: c = b(0)
Wscript.Echo "c: " & TypeName(c)
Wscript.Echo "c = " & c
❯ /opt/wine-devel/bin/wine cscript test.vbs
a: Empty
a =
c: String
c = 1
--
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=56941
Bug ID: 56941
Summary: EA app fails to launch game if total size of
environment variables exceeds ~32000 characters
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)gmail.com
Distribution: ---
### Steps to reproduce
Preparation:
- Have the EA app installed:
https://origin-a.akamaihd.net/EA-Desktop-Client-Download/installer-releases…
- I installed it through Bottles, which installs the following Winetricks
dependencies:
https://github.com/bottlesdevs/programs/blob/main/Games/eaclient.yml
Reproducing:
- Set a very long environment variable, before launching the EA app
- From the EA app, launch any game
- Alternatively, execute the game directly, it will automatically launch the
EA app to launch the game
- If you don't have any game, "The Sims 4" is free
- The game won't launch, an error popup from the EA app will appear (see notes)
### Notes
It doesn't matter whether these ~32000 characters are from a single environment
variable, or from the combination of many of them.
I didn't test on Windows. It may be impossible to test there, since the
environment block there has a limit of 32760 characters (which may probably be
the reason for this issue in the first place).
I say "~32000", because the issue starts occurring a little before 32760
characters. However, my counting method was imprecise (I simply typed `set` in
`wine cmd`, then counted the characters), and there's also the fact that the EA
app also sets its own environment variables.
The issue also occurs with games bought from Steam (thus launched with Proton)
that also have to go through the EA app (thanks EA).
This issue existed before, and the weird thing is that the error popup from the
EA app is different from some time ago (I imagine due to the app being
updated).
Before it was: "Failed to launch game. An error on our end caused the launch to
fail. Try again a little later."
Now it's: "The game hasn't released yet" (which is obviously untrue).
Is it a stack overflow issue?
Logs obtained with `WINEDEBUG=EADesktop.exe:+relay` are too big to attach, even
compressed. Let me know what `WINEDEBUG` parameters I should use instead.
I can see that the app calls `GetEnvironmentStringsW`, shortly followed by a
`WideCharToMultiByte` for each variable (key and value separately). This is
done three times.
--
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=58028
Bug ID: 58028
Summary: Separable Subsurface Scattering fails to launch
Product: vkd3d
Version: 1.15
Hardware: x86-64
URL: https://web.archive.org/web/20240118021209if_/https://www.iryoku.com/separable-sss/downloads/Separable-SSS-D
X10-v1.0.exe
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 78287
--> https://bugs.winehq.org/attachment.cgi?id=78287
shader
vkd3d:0024:err:hlsl_type_from_fx_type ../vkd3d/libs/vkd3d-shader/fx.c:2418:
Unreachable code reached.
1.15-180-g110edf32
--
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.