http://bugs.winehq.org/show_bug.cgi?id=58551
Bug ID: 58551
Summary: Aerofoil (Glider PRO) renders some regions as just
white
Product: Wine
Version: 10.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: denilsonsa(a)gmail.com
Distribution: ---
How to reproduce:
1. Get Aerofoil from https://galeforcegames.itch.io/aerofoil or from
https://github.com/elasota/Aerofoil/releases
2. Get the 1.1.2 zip file, unzip it somewhere.
3. Run: wine Aerofoil.exe
What happens:
On some Wine versions (e.g. the one from Lutris, and using Proton 9.0.4), the
entire game is white when in fullscreen. Pressing Alt+Enter makes it windowed,
and then we can see the title screen graphics. However, trying to interact with
the menus is buggy (the menus are rendered white), and the pop-up dialogs are
also white.
On Wine 10.12, the main title screen renders fine, but some menus are still
rendered fully white.
Changing the Options → Preferences → Display to "32-bit color (Requires
restart)" makes the bug change from white to black. Several sections of the
in-game UI will now be fully black.
If you manage to get into the actual game, it seems to render just fine. Only
the in-game UI things (dialogs and menus) seem to be buggy.
I got these messages on the terminal:
0024:fixme:d3d:wined3d_swapchain_init Unimplemented swap effect 0x3.
01a4:fixme:d3d:wined3d_render_target_view_gl_cs_init Swapchain views not
supported.
0024:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters
00007FFFFE1FF958.
0024:fixme:dxgi:d3d11_swapchain_GetFrameStatistics iface 00007FFFFE82A520,
stats 00007FFFFE1FF978 stub!
01a4:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
0024:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters
00007FFFFE1FF958.
0024:fixme:dxgi:d3d11_swapchain_GetFrameStatistics iface 00007FFFFE82A520,
stats 00007FFFFE1FF978 stub!
0024:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters
00007FFFFE1FF938.
0024:fixme:dxgi:d3d11_swapchain_GetFrameStatistics iface 00007FFFFE82A520,
stats 00007FFFFE1FF958 stub!
(those last couple of messages repeat forever)
--
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=58526
Bug ID: 58526
Summary: GetQueuedFinishionStatus bug
Product: Wine
Version: 10.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: hahamotor(a)126.com
Distribution: ---
The server program adopts Windows' completion port technology. When the remote
client unexpectedly disconnects, on the native Windows operating system, the
GetQueuedFinishionStatus function returns False. At this time, the error code
indicating the remote connection has been disconnected can be queried through
GetLastError. However, in the Wine 10.12 version, this function returns TRUE to
indicate successful operation, causing the program to be unable to detect
remote connection disconnections. Other versions have been tested and all have
the same error.
--
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=58546
Bug ID: 58546
Summary: World of Warcraft (Vanilla) (WoW.exe 1.12.1) renders
no ground textures on wine-staging 10.12
Product: Wine-staging
Version: 10.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq.org(a)ulf-gebhardt.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 79045
--> http://bugs.winehq.org/attachment.cgi?id=79045
wine-10.8 (Staging) rendering ground textures
World of Warcraft (Vanilla) (WoW.exe 1.12.1) renders no ground textures on
wine-staging 10.12 while 10.8 still works as expected.
Running `wine-10.8 (Staging)` everything is running properly (see log), ground
textures are rendered (see screenshot)
```
002c:fixme:winediag:loader_init wine-staging 10.8 is a testing version
containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing
bug reports on winehq.org.
00bc:fixme:wineusb:query_id Unhandled ID query type 0x5.
0024:fixme:winediag:loader_init wine-staging 10.8 is a testing version
containing experimental patches.
0024:fixme:winediag:loader_init Please mention your exact version when filing
bug reports on winehq.org.
info: Game: WoW_tweaked.exe
info: DXVK: v2.7
info: Build: x86 gcc 15.1.0
info: Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x79e61a40
info: Extension providers:
info: Platform WSI
info: OpenVR
info: OpenVR: could not open registry key, status 2
info: OpenVR: Failed to locate module
info: OpenXR
info: Enabled instance extensions:
info: VK_EXT_surface_maintenance1
info: VK_KHR_get_surface_capabilities2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: Found device: NVIDIA GeForce 940MX (NVK GM108) (NVK 25.1.6)
info: Found device: Intel(R) HD Graphics 630 (KBL GT2) (Intel open-source Mesa
driver 25.1.6)
info: D3D9: VK_FORMAT_D16_UNORM_S8_UINT -> VK_FORMAT_D24_UNORM_S8_UINT
info: Process set as DPI aware
```
Running `wine-10.12 (Staging)` ground textures are not rendered properly (see
second screenshot) and a warning appears in the log.
```
002c:fixme:winediag:loader_init wine-staging 10.12 is a testing version
containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing
bug reports on winehq.org.
00c0:fixme:wineusb:query_id Unhandled ID query type 0x5.
0024:fixme:winediag:loader_init wine-staging 10.12 is a testing version
containing experimental patches.
0024:fixme:winediag:loader_init Please mention your exact version when filing
bug reports on winehq.org.
00fc:err:environ:init_peb starting
L"Z:\\home\\dornhoeschen\\.data\\games\\wow-1.12.1-nostalgeek-new\\WoW_tweaked.exe"
in experimental wow64 mode
info: Game: WoW_tweaked.exe
info: DXVK: v2.7
info: Build: x86 gcc 15.1.0
info: Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x79e41d70
info: Extension providers:
info: Platform WSI
info: OpenVR
info: OpenVR: could not open registry key, status 2
info: OpenVR: Failed to locate module
info: OpenXR
info: Enabled instance extensions:
info: VK_EXT_surface_maintenance1
info: VK_KHR_get_surface_capabilities2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: Found device: NVIDIA GeForce 940MX (NVK GM108) (NVK 25.1.6)
info: Found device: Intel(R) HD Graphics 630 (KBL GT2) (Intel open-source Mesa
driver 25.1.6)
info: D3D9: VK_FORMAT_D16_UNORM_S8_UINT -> VK_FORMAT_D24_UNORM_S8_UINT
info: Process set as DPI aware
00fc:fixme:opengl:wow64_map_buffer Doing a copy of a mapped buffer (expect
performance issues)
```
It seems to be that the ground textures are rendered initially and then
disappear.
--
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=37780
Bug ID: 37780
Summary: After running a bash script from cmd, no prompt is
printed
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: gm89(a)hotmail.it
Distribution: ---
If I run a bash script from wine's cmd, after execution the prompt is not
printed.
I believe this is the cause of an hang in my use case, I'm trying to interface
a windows program with my android phone by making it use the native adb binary;
the trick I used was to replace the provided "adb.exe" with a similarly named
bash script with this content:
#!/bin/bash
/usr/bin/adb $*
If I manually call adb.exe from cmd, the output of commands is correct but no
prompt is printed afterwards.
Tested with wine 1.7.33 under ubuntu 14.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=57202
Bug ID: 57202
Summary: steam client stops working on wine 8.19+ on Slackware
15.0 due to mono 8.10 update
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: steampunque8(a)gmail.com
Distribution: ---
Created attachment 77100
--> https://bugs.winehq.org/attachment.cgi?id=77100
last step of bisect for steam client launch failure
I recently tried to run steam client on upstream wines and found that the
client will not start on any wine version 8.19 or above. I bisected the
problem to the update to mono 8.1.0. The last stage of bisect is attached.
When starting the client a ton of processes get created and then "Maximum
number of clients reached" messages get spammed infinitely on the console.
OS: Linux 5.15.140 Dist: Slackware 15.0 64 CPU: 9900k GPU: RTX 4070
I found a workaround to the problem to shut off mono as follows:
export WINEDLLOVERRIDES="mscoree="
This workaround seems OK since I don't think steam client itself relies on mono
but I am not sure some of the apps it launches wont.
Any tips or ideas what might be happening here would be appreciated. No issues
with the older wine versions up to 8.18 ran steam with mono enabled fine so I
am pretty sure some update in mono 8.10 is triggering the problem. There is a
good chance this is related to Slackware 15.0 distribution and has nothing to
do with wine or mono issue but I don't know where to start looking for the
breakage.export WINEDLLOVERRIDES="mscoree="
--
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=58112
Bug ID: 58112
Summary: Unimplemented function
KERNEL32.dll.InitializeSynchronizationBarrier
Product: Wine
Version: 10.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: git.ceeac(a)gmail.com
Distribution: ---
I am developing a cross-platform application that uses barriers as a
synchronization primitive.
This works fine when the application is started on Windows, however when
started on Linux (Arch) + WINE (10.5), the application crashes with
wine: Unimplemented function KERNEL32.dll.InitializeSynchronizationBarrier
called at address 00006FFFFFC695E8 (thread 012c)
Presumably, all of the following functions are unimplemented in WINE:
- InitializeSynchronizationBarrier
- DeleteSynchronizationBarrier
- EnterSynchronizationBarrier
--
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=58547
Bug ID: 58547
Summary: Roblox Studio has a strange window behavior on
winewayland driver
Product: Wine
Version: 10.12
Hardware: x86-64
URL: https://setup.rbxcdn.com/RobloxStudioInstaller.exe
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: wilsontulus5(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: c756ea4e801d7eae32bc8a00efa26fc0f0f47819
Distribution: ArchLinux
Created attachment 79047
--> http://bugs.winehq.org/attachment.cgi?id=79047
Terminal logs without reverting the guilty commit. Almost no difference on the
post-revert version.
Wine version 10.11 had introduced a new update to winewayland driver that makes
Roblox Studio on Wayland more usable, sometimes more than it's X11 counterpart
due to lesser microstutters and almost non-existent flickering (most likely due
to buggy implementation of the Vulkan child windowing system).
Ever since the patch introduced in c756ea4e801d7eae32bc8a00efa26fc0f0f47819,
Studio on winewayland is broken again like <=10.10 (e.g. invisible home screen,
out-of-place teamcreate/contribute button, 3D workspace layer overriding GUIs
including the script viewer, etc).
Since the issue is only viewable after logging in, it's recommended to use
Vinegar (from Flathub or by source: https://github.com/vinegarhq/vinegar - the
launcher does allow specifying a custom wineroot), but the official installer
can also be used if the EdgeWebView2 installer payload returns success to the
official installer.
--
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=58548
Bug ID: 58548
Summary: user32/menu: Sub‑menus always open instantly –
TrackPopup/TrackMenu code ignores SPI_GETMENUSHOWDELAY
and MenuShowDelay in registry
Product: Wine
Version: 7.7
Hardware: aarch64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: falcon4(a)gmail.com
Observed:
Registry setting HKEY_CURRENT_USER\Control Panel\Desktop\MenuShowDelay is set
to the intended default value (400).
SystemParametersInfoW(SPI_GETMENUSHOWDELAY) returns the configured value (e.g.
400 ms).
Yet any Win32 app (Task Manager, Notepad++, etc.) opens sub‑menus with zero
delay; mousing past them collapses/opens instantly.
Expected:
Menu pop‑ups wait <MenuShowDelay> ms before showing, matching Windows behaviour
since Win 95.
This bug leads to having to "tightrope" sub-menu selections, carefully moving
the cursor along a selection to prevent the sub-menu from collapsing.
This was reported back in 2009 by a user that was advised to file a Bugzilla
report, but none seems to have ever been made:
https://forum.winehq.org/viewtopic.php?t=4147
At a quick glance through /wine/dlls/win32u/menu.c, it seems like menu-show
delays were never implemented at all, and I can only hope this is worth fixing
to improve user experience after all these years :)
--
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=51847
Bug ID: 51847
Summary: fixme:advapi
Product: Wine
Version: 6.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: danielrosario92(a)gmail.com
Distribution: ---
Created attachment 70741
--> https://bugs.winehq.org/attachment.cgi?id=70741
problems
not installing programs
--
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=56921
Bug ID: 56921
Summary: MusicBee: Random moments of lag when scrolling,
seemingly related to rendering of rating stars.
Product: Wine-staging
Version: 9.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: v_winebugs(a)outlook.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 76742
--> https://bugs.winehq.org/attachment.cgi?id=76742
Log from terminal
Tested on Wine 9.5-staging, on Fedora 40 KDE Plasma Spin
MusicBee will have these random moments of lag when scrolling on views and
playlists that have rating stars enabled. It seems to be related to how the
stars are being rendered, since when they are hidden the lag goes away, and
this lag is not present when running MusicBee under Windows. To make it worse,
this lag persists after the app is restarted.
Attached is a log from the terminal done while using MusicBee with the lag.
--
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.