https://bugs.winehq.org/show_bug.cgi?id=57923
Bug ID: 57923
Summary: MEmu Android Emulator STUCK IN 99%
Product: Wine
Version: 10.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: pocomal112(a)codverts.com
Distribution: ---
MEmu Android Emulator STUCK IN 99%
Here is the link to the software's website to know what software it is
https://www.mumuplayer.com/index.html
--
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=57993
Bug ID: 57993
Summary: winedevice.exe Hangs After Exiting Games
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: nekoNexus(a)protonmail.ch
Distribution: ---
Created attachment 78253
--> https://bugs.winehq.org/attachment.cgi?id=78253
Vanilla Wine version 10.3 Log
Distro: Gentoo Linux (x86_64)
DXVK Version: 2.6
Gamescope Version: 3.16.2
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.1
Explanation:
-------------
When launching games like Sherlock Holmes: Crimes and Punishments (GOG),
exiting the game (even just launching the game and closing via the main menu
not long after) causes winedevice.exe to just hang (and this causes a zombie
window to remain open) and I'm forced to run "pkill -9 winedevice.exe" (this
problem is consistent)
It doesn't seem to show up at the end of my log, either, for some reason.
I'll still share my log (although, this specific log exhibits a separate issue
I'm about to file) for reference, however
--
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=57991
Bug ID: 57991
Summary: ULTRAKILL (ver. 16c): Graphical issues causing very
blue gameplay
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: amongusus.sinuous664(a)slmails.com
Distribution: ArchLinux
Created attachment 78248
--> https://bugs.winehq.org/attachment.cgi?id=78248
Terminal output text file
I am trying to play Ultrakill on my t430 thinkpad on Arch Linux. While it is
technically playable, the main problem is that major graphical glitches occur,
which can be seen in the attached screenshots. In the screenshots there is an
excess of blue where there shouldn't be, making it difficult to play the game
normally. The issue occurs when I launch ULTRAKILL via wine, go past the intro
screen, and load up any level with 3D graphics.
Link to the game's storepage (where I got the game):
https://store.steampowered.com/app/1229490/ULTRAKILL/
CPU: Intel i7-3632QM
GPU: Intel HD Graphics 4000
Video driver version: Mesa 25.0.1-arch1.2
Kernel version: 6.13.7-arch1-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=57978
Bug ID: 57978
Summary: Running winetest crashes VMWare Fusion
Product: Wine-Testbot
Version: unspecified
Hardware: aarch64
OS: Windows
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robert.lippmann.development(a)gmail.com
I'm running winetest, and Fusion says it has encountered an error and must shut
down.
I know, not supported, and probably a Fusion bug. But I figured I'd document
it here.
--
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=57984
Bug ID: 57984
Summary: Gunner, HEAT, PC! hangs before starting an actual
gameplay
Product: vkd3d
Version: 1.15
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
0bbc:fixme:d3d:wined3d_shader_resource_view_vk_generate_mipmap Ignoring view
format WINED3DFMT_R8_UNORM.
VUID-vkCmdBlitImage-filter-02001(ERROR / SPEC): msgNum: 328973095 - Validation
Error: [ VUID-vkCmdBlitImage-filter-02001 ] Object 0: handle = 0x7f208c47e780,
type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xef7b000000ef7b, type
= VK_OBJECT_TYPE_IMAGE; | MessageID = 0x139bbb27 | vkCmdBlitImage(): srcImage
(VkImage 0xef7b000000ef7b[]) was created with format VK_FORMAT_R8_SINT and
tiling VK_IMAGE_TILING_OPTIMAL which have VkFormatFeatureFlags2
(VK_FORMAT_FEATURE_2_SAMPLED_IMAGE_BIT|VK_FORMAT_FEATURE_2_STORAGE_IMAGE_BIT|VK_FORMAT_FEATURE_2_COLOR_ATTACHMENT_BIT|VK_FORMAT_FEATURE_2_BLIT_SRC_BIT|VK_FORMAT_FEATURE_2_BLIT_DST_BIT|VK_FORMAT_FEATURE_2_TRANSFER_SRC_BIT|VK_FORMAT_FEATURE_2_TRANSFER_DST_BIT|VK_FORMAT_FEATURE_2_SAMPLED_IMAGE_FILTER_MINMAX_BIT|VK_FORMAT_FEATURE_2_STORAGE_READ_WITHOUT_FORMAT_BIT|VK_FORMAT_FEATURE_2_STORAGE_WRITE_WITHOUT_FORMAT_BIT|VK_FORMAT_FEATURE_2_HOST_IMAGE_TRANSFER_BIT)
which in turn is missing the required feature
VK_FORMAT_FEATURE_2_SAMPLED_IMAGE_FILTER_LINEAR_BIT.
The Vulkan spec states: If filter is VK_FILTER_LINEAR, then the format features
of srcImage must contain VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT
(https://docs.vulkan.org/spec/latest/chapters/copies.html#VUID-vkCmdBlitImag…)
Objects: 2
[0] 0x7f208c47e780, type: 6, name: NULL
[1] 0xef7b000000ef7b, type: 10, name: NULL
VUID-vkCmdCopyBufferToImage-dstImage-parameter(ERROR / SPEC): msgNum: 271201052
- Validation Error: [ VUID-vkCmdCopyBufferToImage-dstImage-parameter ] Object
0: handle = 0x7d7d27fc4080, type = VK_OBJECT_TYPE_INSTANCE; | MessageID =
0x102a331c | vkCmdCopyBufferToImage(): dstImage Invalid VkImage Object 0x0.
The Vulkan spec states: dstImage must be a valid VkImage handle
(https://docs.vulkan.org/spec/latest/chapters/copies.html#VUID-vkCmdCopyBuff…)
Objects: 1
[0] 0x7d7d27fc4080, type: 1, name: NULL
0bbc:err:d3d:wined3d_context_vk_allocate_vram_chunk_memory Failed to allocate
memory, vr VK_ERROR_OUT_OF_DEVICE_MEMORY.
0bbc:err:d3d:wined3d_context_vk_create_image Failed to allocate image memory.
0bbc:err:d3d:wined3d_view_vk_create_vk_image_view Failed to prepare texture.
VUID-VkImageViewCreateInfo-image-parameter(ERROR / SPEC): msgNum: 315335852 -
Validation Error: [ VUID-VkImageViewCreateInfo-image-parameter ] Object 0:
handle = 0x7d7d27fc4080, type = VK_OBJECT_TYPE_INSTANCE; | MessageID =
0x12cba4ac | vkCreateImageView(): pCreateInfo->image Invalid VkImage Object
0x0.
The Vulkan spec states: image must be a valid VkImage handle
(https://docs.vulkan.org/spec/latest/chapters/resources.html#VUID-VkImageVie…)
Objects: 1
[0] 0x7d7d27fc4080, type: 1, name: NULL
0bbc:err:msvcrt:_wassert (L"!status &&
\"vkCreateImageView\"",L"../wine/dlls/winevulkan/loader_thunks.c",3216)
1.15-179-g21e08955
--
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=57981
Bug ID: 57981
Summary: 0758:err:virtual:virtual_setup_exception nested
exception on signal stack in thread 0758 addr
0x3f0003f4af stack 0x7fedf170
Product: Wine
Version: 7.0.2
Hardware: aarch64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: liunixfinal(a)gmail.com
Distribution: ---
Created attachment 78234
--> https://bugs.winehq.org/attachment.cgi?id=78234
debugging logs generated after running the application under Wine
My program uses WaitForMultipleObjects to monitor multiple pipes. It runs
normally in a Windows environment, but under Wine, after running for some time,
WaitForMultipleObjects stops working. When data is written to the pipe, it does
not return, and simultaneously, the Wine debug log reports the following error:
0758:err:virtual:virtual_setup_exception nested exception on signal stack in
thread 0758 addr 0x3f0003f4af stack 0x7fedf170
After that, it continuously prints the following log:
04b8:err:sync:RtlpWaitForCriticalSection section 0308D388 "?" wait timed out in
thread 04b8, blocked by 048c, retrying (60 sec)
01f8:err:sync:RtlpWaitForCriticalSection section 0308D388 "?" wait timed out in
thread 01f8, blocked by 048c, retrying (60 sec)
and this is my code:
while (true)
{
DWORD dwWait = WaitForMultipleObjects(pPipeThread->chnNum + 1, // number
of event objects
pPipeThread->hEvents, // array of event objects
FALSE, // does not wait for all
INFINITE); // waits indefinitely
if (dwWait == WAIT_FAILED)
{
DWORD dwError = GetLastError();
char errorMsg[512];
FormatMessageA(FORMAT_MESSAGE_FROM_SYSTEM |
FORMAT_MESSAGE_IGNORE_INSERTS,
NULL, dwError, 0, errorMsg, sizeof(errorMsg), NULL);
cerror("CPipeWrapper WaitForMultipleObjects failed, Error Code: %u,
Error Message: %s", dwError, errorMsg);
}
int i = dwWait - WAIT_OBJECT_0; // determines which pipe
if (i < 0 || i > PIPE_NUM_PER_THREAD)
{
_dout("WaitForMultipleObjects threadidx(%d) chnNum(%d) Index out of
range(%d).", pPipeThread->threadIdx, pPipeThread->chnNum, i);
continue;
}
if (i == 0)
{
if (CPipeMgr::Instance()->IsQuit())
{
_dout("PipeReadThread quit threadidx(%d) chnNum(%d)",
pPipeThread->threadIdx, pPipeThread->chnNum);
return 0;
}
HandleChnCfgUpdate(pPipeThread);
_dout("PipeReadThread config update threadidx(%d) chnNum(%d)",
pPipeThread->threadIdx, pPipeThread->chnNum);
continue;
}
--i;
unsigned int chnID = pPipeThread->chnIDs[i];
CNamePipe* pPipe = CPipeMgr::Instance()->GetPipe(chnID);
int rdLen = pPipe->GetOverlapReadedNum();
int reminderLen = pPipe->GetReminderLen();
if (rdLen > 0)
{
reminderLen = CMemDataMgr::Instance()->DecodeDrvData(chnID,
pPipe->GetReadedBuf(), reminderLen + rdLen);
}
int readed = 0;
pPipe->ReadPipe(reminderLen, readed);
}
--
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=57977
Bug ID: 57977
Summary: Wine-Stable 10.0 SampleRate fixed at 48KHZ no higher
Values available
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: Starfoxfs(a)gmx.net
Distribution: ---
I have tested a lot with Wine-Stable and Wine-Staging and cant get SampleRates
of Audio Programms higher than 48000HZ. Its always fixed at 48000HZ if i play
files with 44100HZ its also 48000HZ.
The Problem is in Winepulse.drv or Winealsa.drv i tested both.
In Pipewire.conf theres a Option to allow all the Samplerates but Wine didnt
use it.
--
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=56145
Bug ID: 56145
Summary: Wine lacks VR support ( OpenVR/OpenXR runtime shim)
Product: Wine
Version: 9.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xeno(a)x-s.com.pl
Distribution: ---
Currently VR support in Linux gets to the point where it becomes viable option.
Linux native apps tend to do just fine , but there's no way for VR capable
windows apps running trough Wine to detect/use VR devices.
VR is supposed to be supported on Proton and hacky Wine-Proton hybrids, where
first option limits support to apps from Steam and second one is a bit
cumbersome to get it working.
To solve this issue wine environment could provide thin VR runtime environment
that catches calls from apps and direct those to linux native VR runtime that
is installed on user system. Wine OpenXR library shouldn't be that complex as
it'd be simple 1:1 mapping of OpenXR API. For Valve OpenVR API there are two
possible approaches, one similar to OpenXR where wine just forward calls to
SteamVR or it could translate calls to OpenXR, like OpenComposite does, then
call OpenXR runtime on Linux side.
--
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=56378
Bug ID: 56378
Summary: Microsoft Edge and Edge-based WebView2 do not function
without --no-sandbox option
Product: Wine
Version: 9.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: asdfghrbljzmkd(a)outlook.com
Distribution: ---
Microsoft Edge will freeze about 1-3 seconds after launching.
Steps to reproduce:
1. Download and install WebView2 (which includes Edge) from
https://developer.microsoft.com/en-us/microsoft-edge/webview2/
2. Run:
wine "/PATH/TO/PREFIX/drive_c/Program Files
(x86)/Microsoft/EdgeCore/VERSIONNUMBER/msedge.exe" --disable-gpu --no-first-run
Edge will not launch. If you add --no-sandbox to the launch options, it will
launch, but freeze after a second or so
(https://bugs.winehq.org/show_bug.cgi?id=56377)
--disable-gpu is required wine wined3d, it can be dropped if using DXVK.
--no-first-run disables the first run prompting you to sign in and such, it has
no bearing on this bug itself.
This also affects applications using WebView2, e.g. the Adobe Creative Cloud
setup application:
WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--disable-gpu" wine
'/PATH/TO/Creative_Cloud_Set-Up.exe'
Using this at least allows the window to open, though it is blank for reasons
currently unknown:
WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--disable-gpu --no-sandbox" wine
'/PATH/TO/Creative_Cloud_Set-Up.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=57972
Bug ID: 57972
Summary: Certain display modes (e.g. 1152x864) not available in
virtual desktop mode
Product: Wine
Version: 10.2
Hardware: x86-64
URL: https://archive.org/download/BloodRayne2Demo/BloodRayn
e2Demo.rar
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: 8f85c444596154c876c7aff3a2866407ea508974
Distribution: ArchLinux
In Bloodrayne 2 video options the display mode 1152x864 is available as a valid
mode, yet the game fails to start with the error "Can't find valid video mode
for 1152x864".
This happens in virtual desktop mode when the size of the VD is set to anything
but 1152x864.
In other games the display mode 1152x864 is now completely missing from their
video options.
This used to work before
commit 8f85c444596154c876c7aff3a2866407ea508974
win32u: Generate fake resolution list from the host modes.
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 570.124.04
wine-10.3-101-g245d3230271
--
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.