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.
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=56278
Bug ID: 56278
Summary: wayland: dropdowns is rendered as toplevel
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hugo(a)whynothugo.nl
Distribution: ---
When using the wayland driver, dropdown menus are rendered as their own
toplevel windows.
On tiling window managers (e.g.: swaywm), this results in it being tiled just
like any other window. I can't imagine that they would be placed correctly on
stacking window managers either.
I confirmed with lswt that dropdowns are effectively rendered as toplevels. An
xdg_popup should be used here instead:
https://wayland.app/protocols/xdg-shell#xdg_popup
The weirdness in behaviour can be reproduced with:
- wine reg.exe add HKCU\\Software\\Wine\\Drivers /v Graphics /d wayland
- winecfg
- Go to the desktop integration tab and click on any dropdown
--
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.