https://bugs.winehq.org/show_bug.cgi?id=56318
Bug ID: 56318
Summary: Totem Arts Launcher.exe does not open
Product: Wine
Version: 9.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 6chars(a)proton.me
Distribution: Mint
Created attachment 76047
--> https://bugs.winehq.org/attachment.cgi?id=76047
The log after trying to launch the .exe
After successfully installing "Totem-Arts-Launcher-latest.exe", when I go to
the installation directory and try to launch "Totem Arts Launcher.exe" (so that
I can install the game Renegade X), the application does not open.
Download link for "Totem-Arts-Launcher-latest.exe":
https://totemarts.games/forums/files/file/1-renegade-x/
SHA1 sum:
d9b7f056103183c5a50003b4c164a23cdf605e95 Totem-Arts-Launcher-latest.exe
My system: Linux Mint 21.3 x86_64, Kernel 6.5.0-17-generic, NVIDIA Geforce GTX
1050 driver 535.154.05, wine-9.2 (Staging).
--
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=53635
Bug ID: 53635
Summary: not implemented dll
Product: Wine
Version: 7.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rafalohaki(a)gmail.com
Distribution: ---
Created attachment 73033
--> https://bugs.winehq.org/attachment.cgi?id=73033
backtrace
not implemented
--
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=54155
Bug ID: 54155
Summary: wxwork failed to launch
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: ayafcc(a)163.com
Distribution: ---
Created attachment 73682
--> https://bugs.winehq.org/attachment.cgi?id=73682
log
1、download the application from attachment
2、install it to any path
3、execute command: wine path/WXWork.exe
it shows:0024:err:sync:RtlReleaseSRWLockExclusive Lock 0F4BD460 is not owned
exclusive!
--
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=48085
Bug ID: 48085
Summary: Wine error trying to install Mono after a version
update
Product: Wine
Version: 4.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ronen.rozner(a)gmail.com
Distribution: ---
Created attachment 65637
--> https://bugs.winehq.org/attachment.cgi?id=65637
Backtrace file
It started after an update a few versions ago (4.xx branch, currently running
4.19).
When launching an application, wineconfig will initially run, prompting to
update Mono. Then it will prompt an error (see trace).
The Win application runs normally, so I guess it might not be a severe 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=40613
Bug ID: 40613
Summary: WhatsApp Desktop application not working
Product: Wine
Version: 1.9.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: sh.yaron(a)gmail.com
Distribution: ---
Created attachment 54470
--> https://bugs.winehq.org/attachment.cgi?id=54470
Stack trace as appears on cli
WhatsApp for Windows Desktop was released and I tried to install it.
Apparently it requires Windows 8 and greater, I've set it correctly in Winecfg.
Trying to run the WhatsApp installation (ver 0.2.684) renders the error in the
attached file.
--
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=56458
Bug ID: 56458
Summary: ntdll tests skipped on win7 & win8: missing entry
point kernel32.RtlPcToFileHeader
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: fgouget(a)codeweavers.com, gijsvrm(a)gmail.com,
julliard(a)winehq.org
Regression SHA1: 38fb2f41ad1347b6e35dc87f6dc358a13d8905cb
Distribution: ---
ntdll_test.exe imports kernel32.RtlPcToFileHeader, which does not exist on
Windows 7 and 8.
The culprit is the direct import, which resolves to kernel32's forwarder. It
should use pRtlPcToFileHeader variable (which stores GetProcAddress result)
instead.
This causes all ntdll tests to be skipped on win7 & win8 VMs:
info.c:0: Tests skipped: missing entry point (details below)
| ntdll_test.exe - Entry Point Not Found
| The procedure entry point RtlPcToFileHeader could not be located in the
dynamic link library C:\Users\winetest\Documents\ntdll_test.exe.
0adc:info: 0 tests executed (0 marked as todo, 0 as flaky, 0 failures), 1
skipped.
ntdll:info:0adc done (0) in 0s
https://test.winehq.org/data/4860fbe7b5355bfa4a5e98bb2446f69d1c484666/win81…https://test.winehq.org/data/4860fbe7b5355bfa4a5e98bb2446f69d1c484666/win7_…
Originally reported by Gijs Vermeulen.
--
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=56450
Bug ID: 56450
Summary: Non-input USB HID devices stopped working in 9.1
Product: Wine
Version: 9.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: bugzilla-wine(a)opinsys.fi
Regression SHA1: 814d2c176d23c581353ba5679977415d2218d0c5
Distribution: Debian
Non-input USB HID devices stopped working in 9.1.
Wine 9.0 + LoggerPro 3.16.2 + USB HID thermometer (08f7:0002 Vernier
EasyTemp/Go!Temp): LoggerPro detects the device and starts collecting
temperature measurements automatically.
Wine 9.1 + LoggerPro 3.16.2 + USB HID thermometer (08f7:0002 Vernier
EasyTemp/Go!Temp):
LoggerPro does not detect the device.
Host system detects the device and assigns hid-generic driver to it and a
hidraw device is created. The device is not an input device and hence input
subsystem is not used for this device (event devices are not created).
My understanding is that commit 814d2c176d23c581353ba5679977415d2218d0c5 causes
the regression, because it changes the policy to not use hidraw by default and
requires devices to be explicitly listed in EnableHidraw bus option to be used
by hidraw backend.
Further changes to winebus.sys have been made to allow hidraw to be used in
certain scenarios (some gamepads and when evdev and SDL is disabled), but these
do not cover the case when non-input HID device is used in default environment.
This bug still exists in 9.4.
I am working on a patch set which fixes the bug. I'll create a merge request.
--
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=56406
Bug ID: 56406
Summary: wineserver crashes in set_input_desktop()
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The wineserver crashes when running the Wine test suite on my Debian 12 PC. The
crash happens during the dxgi:dxgi test.
Here is some information collected by attaching gdb to wineserver while running
the tests:
Program received signal SIGSEGV, Segmentation fault.
0x56683005 in set_input_desktop (winstation=0x576aea90, new_desktop=0x576af890)
at /home/fgouget/wine/wt23/src/server/winstation.c:246
246 set_rawinput_process( thread->process, 0 );
(gdb) p thread
$1 = (struct thread *) 0x52fff4
(gdb) p thread->process
Cannot access memory at address 0x530034
(gdb) bt
#0 0x56683005 in set_input_desktop (winstation=0x576aea90,
new_desktop=0x576af890)
at /home/fgouget/wine/wt23/src/server/winstation.c:246
#1 0x5664afac in req_send_hardware_message (req=0x577995c0, reply=0xff829300)
at /home/fgouget/wine/wt23/src/server/queue.c:2808
#2 0x566561c9 in call_req_handler (thread=thread@entry=0x577994d0)
at /home/fgouget/wine/wt23/src/server/request.c:305
#3 0x5665720c in read_request (thread=0x577994d0) at
/home/fgouget/wine/wt23/src/server/request.c:339
#4 0x566627a1 in thread_poll_event (fd=0x5778c070, event=1) at
/home/fgouget/wine/wt23/src/server/thread.c:388
#5 0x5662faf6 in fd_poll_event (event=<optimized out>, fd=<optimized out>)
at /home/fgouget/wine/wt23/src/server/fd.c:505
#6 main_loop_epoll () at /home/fgouget/wine/wt23/src/server/fd.c:599
#7 0x5662fd9f in main_loop () at /home/fgouget/wine/wt23/src/server/fd.c:955
#8 0x5661fa80 in main (argc=1, argv=0xff829b04) at
/home/fgouget/wine/wt23/src/server/main.c:238
(gdb) info registers
eax 0x5fae9a2c 1605278252
ecx 0x576aea90 1466624656
edx 0x53002c 5439532
ebx 0x566c0ff4 1449922548
esp 0xff8291e4 0xff8291e4
ebp 0x52fff4 0x52fff4
esi 0x576eedb0 1466887600
edi 0x576af890 1466628240
eip 0x56683005 0x56683005 <set_input_desktop+101>
eflags 0x10296 [ PF AF SF IF RF ]
cs 0x23 35
ss 0x2b 43
ds 0x2b 43
es 0x2b 43
fs 0x0 0
gs 0x63 99
(gdb) p *winstation->input_desktop
$23 = {obj = {refcount = 1466843598, handle_count = 2691322373, ops = 0x73006f,
wait_queue = {next = 0x66006f,
prev = 0x200074}, name = 0x68004a, sd = 0x6e0065, is_permanent = 1,
obj_list = {next = 0x690065,
prev = 0x550020}}, flags = 5439561, winstation = 0x470045, input_time =
20548038376620111, entry = {
next = 0x54002e, prev = 0x460054}, threads = {next = 0x53002c, prev =
0x670065}, top_window = 0x65006f,
msg_window = 0x550020, global_hooks = 0x49, hotkeys = {next = 0x49004d, prev
= 0x47004e},
close_timeout = 0x49004c, foreground_input = 0x2e0055, users = 5505108,
cursor = {x = 2883651, y = 6881357,
clip = {left = 6750318, top = 6881356, right = 85, bottom = 5439565},
last_change = 4718681, win = 5505070},
keystate = "T\000C\000,\000M\000i\000c\000r\000o\000s\000o\000f\000t\000
\000Y\000a\000H\000e\000i\000
\000U\000I\000\000\000M\000E\000I\000R\000Y\000O\000.\000T\000T\000C\000,\000M\000e\000i\000r\000y\000o\000
\000U\000I\000\000\000M\000A\000L\000G\000U\000N\000.\000T\000T\000F\000,\000M\000a\000l\000g\000u\000n\000
\000G\000o\000t\000h\000i\000c\000\000\000Y\000U\000G\000O\000T\000H\000M\000.\000T\000T\000C\000,\000Y\000u\000
\000G\000o\000t\000h\000i\000c\000
\000U\000I\000\000\000S\000E\000G\000U\000I\000S\000Y\000"...}
So it looks like it is the first input_desktop->threads entry which is wrong.
The crashes started on 2024-02-28 and they happen most clearly when running the
tests in a pure 32-bit environment[1]. Furthermore a bisect shows that the
crashes started with the commit below:
commit c43b1ecbc3e8509b1f4778d799f9759eb64dda40 (HEAD)
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Sun Feb 25 09:53:09 2024 +0100
server: Keep a list of processes that can receive rawinput messages.
[1] When run in a 64-bit environment the tests succeed, and the 64-bit tests
get stuck but there is no 'wineserver crashed' message in the logs.
--
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=56435
Bug ID: 56435
Summary: capture mouse dont work in virtual desktop (work on
wine 9.3)
Product: Wine
Version: 9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrdeathjr28(a)yahoo.es
Distribution: ---
using wine 9.3 mouse capture in virtual desktop work but in wine 9.4 dont work
and compiling git, mouse capture work until this commit
https://gitlab.winehq.org/wine/wine/-/commit/ad921b3c561c428ce36a2a3e0f44de…
in my case after this dont work
at simple seek i think about lastest patchs of Rémi Bernon about input can be
related with this issue
maybe this bug could be stay affected for lastest input patchs:
https://bugs.winehq.org/show_bug.cgi?id=56429
--
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=56411
Bug ID: 56411
Summary: Failure to build wine 9.4 due to EGL 64-bit
development files not found
Product: Wine
Version: 9.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: timo.gurr(a)gmail.com
Distribution: ---
Trying to update our distribution package to the latest release configure fails
for me on Exherbo Linux with:
[...]
checking for -lGL... libGL.so.1
checking for wayland-client.h... yes
checking for wl_display_connect in -lwayland-client... yes
checking for wayland-scanner... /usr/bin/wayland-scanner
checking for xkbcommon/xkbcommon.h... yes
checking for xkb_context_new in -lxkbcommon... yes
checking for xkbcommon/xkbregistry.h... yes
checking for rxkb_context_new in -lxkbregistry... yes
checking for EGL/egl.h... (cached) yes
checking for -lEGL... libEGL.so.1
checking for wayland-egl.h... yes
checking for wl_egl_window_create in -lwayland-egl... yes
configure: error: EGL 64-bit development files not found, the Wayland driver
won't support OpenGL
This is an error since --with-opengl was requested.
despite the checks reporting "yes" and having (lib)wayland-egl installed
--- [ignor] /usr/x86_64-pc-linux-gnu/lib/libwayland-egl.so.1.22.0
--- [ignor] /usr/x86_64-pc-linux-gnu/lib/libwayland-egl.so.1
--- [ignor] /usr/x86_64-pc-linux-gnu/lib/libwayland-egl.so
cat /usr/x86_64-pc-linux-gnu/lib/pkgconfig/wayland-egl.pc
prefix=/usr
includedir=${prefix}/x86_64-pc-linux-gnu/include
libdir=${prefix}/x86_64-pc-linux-gnu/lib
Name: wayland-egl
Description: Frontend wayland-egl library
Version: 18.1.0
Requires: wayland-client
Libs: -L${libdir} -lwayland-egl
Cflags: -I${includedir}
Gentoo suffers the same issue and they just apply a patch removing the
additional
WINE_NOTICE_WITH(opengl, [test -z "$ac_cv_lib_soname_EGL" -o -z
"$HAVE_LIBWAYLAND_EGL"],
check:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ddfba238cc0b1ab4056f6d…
--
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=56380
Bug ID: 56380
Summary: Rocket League crashes with Wine 9.3 after BakkesMod
(trainer app) injects into the game
Product: Wine
Version: 9.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: oguilherme(a)protonmail.com
Distribution: ---
Created attachment 76126
--> https://bugs.winehq.org/attachment.cgi?id=76126
Wine 9.3 output (where Rocket League crashes if BakkesMod is running)
As of Wine 9.3, I can not use BakkesMod[1] (a Rocket League[2] trainer
), to inject into the game anymore.
git bisect indicates commit bb872831deb48382e4733979e00243e5122385d0 is the
culprit.
Without BakkesMod running, the game runs just fine.
---
Steps to reproduce:
1. Launch BakkesMod
2. Launch Rocket League
3. Wait
4. Rocket League crashes
---
System information:
Wine v9.3
NVIDIA driver 470.239.06 (GPU: NVIDIA GTX 660)
DXVK 1.10.3
BakkesMod v190 (Injector version 31)
Rocket League (from Epic, version BC2_Update48+441123)
---
Ref:
[1] https://github.com/bakkesmodorg/BakkesModInjectorCpp
[2] https://store.epicgames.com/en-US/p/rocket-league
--
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=56379
Bug ID: 56379
Summary: d2d1 regression unable to build after:
https://gitlab.winehq.org/wine/wine/-/commit/167103114
389c7f487f7d6aa398f56abf9cc5572
Product: Wine
Version: 9.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dofficialgman(a)gmail.com
Distribution: ---
Regression after
https://gitlab.winehq.org/wine/wine/-/commit/167103114389c7f487f7d6aa398f56…
unable to build with the following errors:
i686-w64-mingw32-gcc -c -o dlls/d2d1/i386-windows/effect.o
../wine-9.3/dlls/d2d1/effect.c -Idlls/d2d1 -I../wine-9.3/dlls/d2d1 -Iinclude \
-I../wine-9.3/include -I../wine-9.3/include/msvcrt -D_UCRT -D__WINESRC__
-D__WINE_PE_BUILD -Wall \
-fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self \
-Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits
-Wunused-but-set-parameter -Wvla \
-Wwrite-strings -Wpointer-arith -Wlogical-op -fno-omit-frame-pointer
-mpreferred-stack-boundary=2 \
-gdwarf-4 -g -O2
../wine-9.3/dlls/d2d1/effect.c: In function 'd2d_effects_init_builtins':
../wine-9.3/dlls/d2d1/effect.c:296:41: error: initializer element is not
constant
{ &CLSID_D2D12DAffineTransform, _2d_affine_transform_description },
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../wine-9.3/dlls/d2d1/effect.c:296:41: note: (near initialization for
'builtin_effects[0].description')
../wine-9.3/dlls/d2d1/effect.c:297:46: error: initializer element is not
constant
{ &CLSID_D2D13DPerspectiveTransform,
_3d_perspective_transform_description},
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../wine-9.3/dlls/d2d1/effect.c:297:46: note: (near initialization for
'builtin_effects[1].description')
../wine-9.3/dlls/d2d1/effect.c:298:33: error: initializer element is not
constant
{ &CLSID_D2D1Composite, composite_description },
^~~~~~~~~~~~~~~~~~~~~
../wine-9.3/dlls/d2d1/effect.c:298:33: note: (near initialization for
'builtin_effects[2].description')
../wine-9.3/dlls/d2d1/effect.c:299:28: error: initializer element is not
constant
{ &CLSID_D2D1Crop, crop_description },
^~~~~~~~~~~~~~~~
../wine-9.3/dlls/d2d1/effect.c:299:28: note: (near initialization for
'builtin_effects[3].description')
../wine-9.3/dlls/d2d1/effect.c:300:30: error: initializer element is not
constant
{ &CLSID_D2D1Shadow, shadow_description },
^~~~~~~~~~~~~~~~~~
../wine-9.3/dlls/d2d1/effect.c:300:30: note: (near initialization for
'builtin_effects[4].description')
../wine-9.3/dlls/d2d1/effect.c:301:33: error: initializer element is not
constant
{ &CLSID_D2D1Grayscale, grayscale_description },
^~~~~~~~~~~~~~~~~~~~~
../wine-9.3/dlls/d2d1/effect.c:301:33: note: (near initialization for
'builtin_effects[5].description')
Makefile:27950: recipe for target 'dlls/d2d1/i386-windows/effect.o' failed
make: *** [dlls/d2d1/i386-windows/effect.o] Error 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.
http://bugs.winehq.org/show_bug.cgi?id=29523
Bug #: 29523
Summary: CDBurnerXP hangs on right-clicking empty space in the
file browser
Product: Wine
Version: 1.3.36
Platform: x86-64
URL: http://cdburnerxp.se/download?more-options
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: RandomAccountName(a)mail.com
Classification: Unclassified
Created attachment 38233
--> http://bugs.winehq.org/attachment.cgi?id=38233
Terminal output
Right-clicking in an empty section of the file browser causes CDBurnerXP to
become unresponsive. On Windows, this brings up a context menu.
Steps to reproduce:
1. winetricks dotnet20
2. Install and run CDBurnerXP
3. Choose "data disc" from the main menu
4. Right-click in some empty space within the file browser (top-right section)
The problem is also present in 1.2.
--
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=56085
Bug ID: 56085
Summary: Guitar Pro 8.1.1 Build 17 crashes once hitting Design
Button
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vmustin(a)gmail.com
Distribution: ---
Created attachment 75748
--> https://bugs.winehq.org/attachment.cgi?id=75748
System Information
Error is reproducible since several Versions (7.0, 7.5, 8.0, 8.1.1)
Using Linux Mint 21.2 (see system information)
--
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=52401
Bug ID: 52401
Summary: Improper synchronization in sock_recv/sock_send leads
to arbitrary reordering of completion of I/O requests
Product: Wine
Version: 7.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
Distribution: ---
The sock_recv function (dlls/ntdll/unix/socket.c) issues a 'recv_socket' call
to
the server to complete the I/O request.
Prior to calling the server, the function attempts to serve the I/O request
locally first by calling try_recv().
The consequence is that there are two types of asynchronous I/O request
(hereinafter "Async") sent to the server:
1. Eager: try_recv() call has succeeded before 'recv_socket'. There is no more
I/O to be done.
2. Deferred: the request is still pending. When the server senses an incoming
packet, async_recv_proc() (in client side) will be called to complete the
I/O.
The problem is that eager Asyncs are _not_ prioritized before deferred Asyncs.
Therefore, deferred Asyncs may be completed before eagar Asyncs.
The following scenario illustrates the problem:
1. The socket's incoming buffer is initially empty.
2. Client: The application calls WSARecv(). In sock_recv(), try_recv() fails
with STATUS_DEVICE_NOT_READY; therefore, a deferred Async is queued to the
server. WSARecv() returns with error ERROR_IO_PENDING.
3. The socket receives packet [A] in the meantime. The socket's incoming buffer
is no longer empty.
4. Client: The application calls WSARecv() again. In sock_recv(), try_recv()
succeeds with packet [A]; therefore, an eager Async is queued to the
server.
5. The socket receives packet [B] in the meantime.
6. Server: the poll() loop detects this, and calls async_wake_up(
&sock->read_q,
status ). This causes APC_ASYNC_IO for deferred Async to be called to the
client process.
6. Client: While still in the second sock_recv(), the client does wait_async()
on the returned wait handle. This causes the APC_ASYNC_IO (a system APC)
to be dequeued.
7. Client (select loop): The client does a server select call. This returns
STATUS_KERNEL_APC with APC_ASYNC_IO. The client calls try_recv() (from
async_recv_proc), which succeeds with packet [B]. The client process
completes the deferred Async with this packet.
8. Client (select loop): The client re-issues the select call after the APC.
8. Server: the wait on the async wait handle is satisfied, causing
async_satisified() to be called. This in turn calls async_set_result(),
which completes the eager Async (with packet [A]).
9. Client: The client exits sock_recv() and in turn WSARecv(), which reports
immediate success.
(Ditto for sock_send and other similar asynchronous I/O requests.)
If the application uses a completion port, it will observe the deferred Async
first, and the eager Async second. The deferred Async carries packet [B],
while the eager Async carriers packet [A]. This results in the application
receiving the packets in the wrong order.
--
Three possible solutions comes to mind:
1. Replace the call to try_recv()/try_send() in sock_recv()/sock_send() with
STATUS_DEVICE_NOT_READY. This may slightly reduce performance, since it
always defers all I/O requests and forces them to go through the poll()
loop.
2. Make async_handoff() immediately call async_set_result() if the status and
data are already set (i.e. the I/O has completed synchronously). Since this
affects other asynchronous operations as well, I'm not sure this approach
is semantically correct.
3. Prioritize immediately satiable async wait handles _before_ system APCs when
waiting for objects. This approach too changes semantics, and appears much
uglier than other solutions.
--
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=56050
Bug ID: 56050
Summary: NtContinue does not set integer registers without
CONTEXT_AMD64 flag
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: moonshadow565(a)hotmail.com
Distribution: ---
Created attachment 75703
--> https://bugs.winehq.org/attachment.cgi?id=75703
NtContinue without CONTEXT_AMD64
When calling NtContinue without CONTEXT_AMD64 flag set, NtContinue ignores
integer registers.
This will result in incorrect values in register.
This does not match behaviour observed on windows.
--
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=56456
Bug ID: 56456
Summary: Steven Speilberg's Director's Chair: wont open at all
Product: Wine
Version: unspecified
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nicholasdecelles(a)aol.com
Created attachment 76216
--> https://bugs.winehq.org/attachment.cgi?id=76216
this backtrace.txt is the bug report i was told to attach to this report, Good
Luck and Wishes!
I put windows 95 for the dc.exe app under winecfg and when i start it through
the terminal on Big Sur macOS an Application Error comes up saying
The instruction at feacf578 referenced memory at 00000030
The memory could not be read from
Click on OK to terminate the application
--
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=56417
Bug ID: 56417
Summary: You must install or update. NET to run this
application.
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: HalanoSiblee(a)gmail.com
Distribution: ---
Created attachment 76180
--> https://bugs.winehq.org/attachment.cgi?id=76180
Screenshot of the bug
I'm trying to run W3D HUB LAUNCHER https://w3dhub.com/
But it's seems the application can't detect dotnet 7 even i've install wine
mono and dotnet 7 x64
The problem still exist program can't detect it many dotnet windows software
run on my system just fine expect this one
idk what's wrong for this specific application.
--
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=36547
Bug ID: 36547
Summary: 3DMark 2003 installer has no taskbar/Alt Tab
representation
Product: Wine
Version: 1.7.19
Hardware: x86
URL: http://www.futuremark.com/benchmarks/legacy
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P1
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: t.artem(a)mailcity.com
Created attachment 48641
--> http://bugs.winehq.org/attachment.cgi?id=48641
Installing 3DMark03_v360_1901.exe
Download and try to run 3DMark03_v360_1901.exe.
3DMark03 installer won't be registered in the Alt-Tab list, or taskbar.
See the attached screenshot.
--
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=8067
--- Comment #27 from Nathan Kidd <nathan(a)spicycrypto.ca> ---
Still reproduces with 9.0
00f0:err:local:LOCAL_GetBlock not enough space in local heap 0307 for 1400
bytes
~/Games/kq6$ sha256sum *.exe *.dll
204bea956a560f7b081ada2afa2b992abecd835fd58a18018e8ce005a48c52cf sciwv.exe
ec75d4567a775f1503017d662b450aea3455f4a6b48d209ebfc516a7ad045047 mmaware.dll
fa8bf838e013d5a88256ce15352fcd504b3c42122f497b2264f7f1c0757512a4 proglib.dll
70fd4190fb0b42dc6857735ebe5c94279176aa50a37cce85db7201fcf8d4d75a rave.dll
f1837dee9a76197c287e04caec2bc7cf11728232a1ec3974bad385345916c53c scidll.dll
~/Games/kq6$ strings sciwv.exe | grep 6
SCIKQ6V
Windows version of SCI for KQ6
...
--
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=49299
Bug ID: 49299
Summary: PowerToys for Windows 10 crashes on unimplemented
function KERNEL32.dll.GetPackageFamilyName
Product: Wine
Version: 5.9
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
The program installs, but crashes when you try to run PowerToys.exe.
$ sha256sum PowerToysSetup-0.18.1-x64.msi
83b2f088f6a0ef7066ba8303ad51e2a270123fe127991486b715ac55f84da19b
PowerToysSetup-0.18.1-x64.msi
--
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=39669
Bug ID: 39669
Summary: D3DERR_NOTAVAILABLE in Dishonored - Steam
Product: Wine
Version: 1.8-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: miachm3(a)gmail.com
Distribution: ---
Dishonored crashes at start with Steam Launcher:
1º Install Steam.
2º Install Dishonored from Steam.
3º Launch, not additional options required.
Anothers D3X9 games works 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.