https://bugs.winehq.org/show_bug.cgi?id=57435
Bug ID: 57435
Summary: D2D1GeometrySinc::AddArc() doesn't properly mark end
of the figure segment
Product: Wine
Version: 9.21
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: source, testcase
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Distribution: ---
Created attachment 77431
--> https://bugs.winehq.org/attachment.cgi?id=77431
Rounded rect under Wine
If an application creates a rounded rect geometry manually using a sequence of
calls ::AddLine() and ::AddArc() instead of ::CreateRoundedRectangleGeometry()
then the created rectangle is distorted under Wine.
While D2D1GeometrySinc::AddArc() is currently a stub, it tries to be smart and
calls d2d_figure_add_vertex() to add a terminating arc point to the figure,
however this doesn't work, and next call to ::AddLine() draws the line from the
point where previous line was terminated instead of an added vertex, and this
leads to drawing a distorted rectangle.
A simple implementation of ::AddArc() that calculates points of two arc
quadrants and calls d2d_geometry_outline_add_arc_quadrant() helper also suffers
from the same problem: added arc quadrants don't seem to properly mark end of
the figure segment. This seems to be caused by difference between how
::AddLines() and d2d_geometry_outline_add_line_segment() (used by
d2d_rounded_rectangle_geometry_init() helper called from
::CreateRoundedRectangleGeometry()) create line segments.
Attached test applications (source + binary) use both described above
approaches:
::CreateRoundedRectangleGeometry() and ::AddLine() + ::AddArc().
See screenshots for the Windows vs. Wine comparison.
--
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=54482
Bug ID: 54482
Summary: RtlCaptureStackBackTrace cause segv
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: ake.rehnman(a)gmail.com
Distribution: ---
Created attachment 74033
--> https://bugs.winehq.org/attachment.cgi?id=74033
patch attempt
RtlCaptureStackBackTrace crash on segmentation fault because the unwinding
keeps going beyond the stack end. It seems on x86-64 the stack actually starts
at least 32 bytes below StackBase so the compariston with context.rsp to
StackBase will never hit but we get a context.rpc value of 0 which obviously
SEGV:s.
I made a patch attempt and just check if rcp = 0 and end the unwinding.
--
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=41392
Bug ID: 41392
Summary: directory.c: match_filename always false if mask
contains "*?"
Product: Wine
Version: 1.9.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: lcmecmac(a)gmail.com
Distribution: ---
A mask containing '*' followed by '?' will not match any files.
For example, "dir *?" does not show any files in a non-empty directory.
--
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=42407
Bug ID: 42407
Summary: LdrUnloadDll may recursion unload same dll
Product: Wine
Version: 1.9.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: xiewei(a)deepin.com
Distribution: ---
Created attachment 57219
--> https://bugs.winehq.org/attachment.cgi?id=57219
LdrUnloadDll log file
It may cause QQ crash.LdrUnloadDll funcation recursion unload Flash.ocx,and
dsound.dll ldr.LoadCount to 0,then dsound.dll be unload.But QQ process is still
using dsound.dll.
Type: EXCEPTION_ACCESS_VIOLATION
Error: Read address 0x7985C309
Address: 7985C309
--
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=40972
Bug ID: 40972
Summary: RtlVerifyVersionInfo returns wrong results
Product: Wine
Version: 1.9.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: marcinwiaz(a)poczta.onet.pl
Distribution: ---
Created attachment 55126
--> https://bugs.winehq.org/attachment.cgi?id=55126
Tiny test program - EXE and source
(Note: this a different problem than in Bug 36143)
Steps to reproduce:
1) Download and unpack Reproduce.exe, which is attached to this bug report
2) Configure Wine to emulate Windows 2003 (which has version number 5.2) for
Reproduce.exe
3) Launch Reproduce.exe - you will see in the console window:
CurrentOS is: 5.2
RequestedOS is >= than: 5.19
CurrentOS is < than RequestedOS (which is WRONG!)
4) Run true Microsoft Windows 2003 Server
5) Launch Reproduce.exe - you will see in the console window:
CurrentOS is: 5.2
RequestedOS is >= than: 5.19
CurrentOS is >= than RequestedOS
Explanation:
Minor version numbers should be treated similarly to digits after a decimal
point - so when comparing software versions:
version 5.1 is < than version 5.2
version 5.11 is < than version 5.2 (note that 11 is > than 2 !)
version 5.19 is < than version 5.2 (note that 19 is > than 2 !)
So when comparing for VER_MINORVERSION or VER_SERVICEPACKMINOR inside the
"VerifyVersionInfo" API, Microsoft uses a lexical comparison - which works as:
lstrcmp(tostring(dwMinorVersion1),tostring(dwMinorVersion2))
or
lstrcmp(tostring(wServicePackMinor1),tostring(wServicePackMinor2))
Please note, that it's still different than comparing real numbers, because:
5.20 = 5.2
but
lstrcmp("5.20","5.2") != 0
So lstrcmp-like function must be used for VER_MINORVERSION and
VER_SERVICEPACKMINOR checking inside the "RtlVerifyVersionInfo" function (which
is called by the "VerifyVersionInfo" API in Wine) to be compatible with
Microsoft Windows.
Possible fix: in "version.c" file, add a new "version_compare_values_lexical"
function. It should be based on the original "version_compare_values" function,
but should use "lstrcmp" calls instead of integer comparisons. This
"version_compare_values_lexical" function should be called instead of
"version_compare_values" when checking for VER_MINORVERSION and
VER_SERVICEPACKMINOR inside the "RtlVerifyVersionInfo" function.
--
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=49828
Bug ID: 49828
Summary: MSVC 2019 executables with ASAN enabled fail to start
Product: Wine
Version: 5.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nyanpasu64(a)tuta.io
Distribution: ---
Recent versions of MSVC allow building Windows .exes with ASAN (it may have
already been possible using Clang.):
https://devblogs.microsoft.com/cppblog/addresssanitizer-asan-for-windows-wi…
I took an old Win32/MFC application and built it using MSVC ASAN on Windows 10,
to try to discover memory bugs on Windows and Wine.
- Program download at
https://cdn.discordapp.com/attachments/653168829891084298/75454092297227479…
.
- Source at https://github.com/nyanpasu64/Dn-FamiTracker/tree/b3ba802f
(permalink at
https://cdn.discordapp.com/attachments/653168829891084298/75454082852061186…
).
- To build, copy cmake_user_begin.cmake.example to cmake_user_begin.cmake, then
run CMake in MSVC 32-bit Release mode. It may be possible using Visual Studio's
.json file or msbuild, but I haven't tried yet.
On Windows, the program starts without problems. On wine-5.17, when I try to
run this program, it crashes during the loading process.
nyanpasu64@dell-arch ~/apps> wine Dn_FamiTracker_ASAN.exe
0024:fixme:ntdll:EtwEventRegister ({6c6c766d-3846-4e6a-a4fb-5b530bd0f3fa},
00401030, 00884590, 008845A8) stub.
0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0084A41C, 34) stub
==32==AddressSanitizer CHECK failed:
D:\agent\_work\3\s\src\vctools\crt\asan\llvm\compiler-rt\lib\asan\asan_rtl.cc:401
"((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0)
<empty stack>
`winedbg Dn_FamiTracker_ASAN.exe` doesn't work, it gets stuck on
`0x00000000005c9701 EntryPoint+0xffffffffffffffff in dn_famitracker_asan: ret`.
If I instead `winedbg --gdb Dn_FamiTracker_ASAN.exe`, I get a pile of identical
SIGTRAP with different backtraces. These are non-fatal and can be continued. I
think these correspond to asan errors that would normally terminate the
program, but unfortunately it doesn't print log messages when running in
winedbg. I don't know how to fix that.
0x005c9701 in _sanitizer_print_stack_trace () from
/home/nyanpasu64/.wine/dosdevices/z:/home/nyanpasu64/apps/Dn_FamiTracker_ASAN.exe
The last SIGTRAP is different:
0x7bc52379 in DbgBreakPoint@0 () from
/home/nyanpasu64/.wine/dosdevices/c:/windows/syswow64/ntdll.dll
Afterwards the program starts. (It used to crash, but works with lib32-libpulse
and lib32-mpg123 installed, unsure if that's why.)
--
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=43262
Bug ID: 43262
Summary: Drag&Drop not working between wine explorer and other
applications
Product: Wine
Version: 2.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mintos(a)discard.email
Distribution: ---
https://pastebin.com/39uSnrR7 console output
--
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=55336
Bug ID: 55336
Summary: Touhou 6 : Full-screen with Alt-tabbing or using DXVK
breaks inputs
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: riyu12383(a)gmail.com
Distribution: ---
-The Game
Here is a very small demo version of the game from archive.orghttps://archive.org/compress/KoumaTr013/formats=ARCHIVE%20BITTORRENT,METADA…
To launch this version, you'll need to add Japanese locale like this :
LANG=ja_JP.UTF-8 wine 東方紅魔郷.exe
-The bug
When launching the game in Full-screen and Alt-Tabbing or using DXVK, the game
inputs breaks, its scrolls the menu infinitely or quit the game by itself, the
user can't control anything anymore. On the demo version it seems the user only
loose the control.
Interestingly on Windows, since Windows 10, the game has an exaggerated
speed/framerate in full-screen. Which was fixed using this dx8 to dx9 converter
: http://enbdev.com/convertor_dx8_dx9_v0036.htm However this doesn't change
anything with wine.
I originally discovered this bug here :
https://github.com/AlpyneDreams/d8vk/issues/155
--
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=52215
Bug ID: 52215
Summary: MSTSC (Remote Desktop) 7.0 cannot find its MUI files
when Windows version is set to 7
Product: Wine
Version: 7.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Created attachment 71279
--> https://bugs.winehq.org/attachment.cgi?id=71279
Error. File not found. C:\windows\system32\<LANG_NAME>\mstsc.exe.MUI
A workaround is to set the Windows version to XP but I don't like it because
Wine as far as I know doesn't allow to set a per application Windows version
and my default Windows version is set to 7.
strace shows that Wine doesn't even attempt to find MUI files as if some
resolution inside it breaks completely when Windows != XP.
--
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=57007
Bug ID: 57007
Summary: Sequence Editor from Legendary Explorer of ME3Tweaks
Mod Manager triggers GDI assert
Product: Wine
Version: 9.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: raulvior.bcn(a)gmail.com
Distribution: ---
Created attachment 76845
--> https://bugs.winehq.org/attachment.cgi?id=76845
Log generated with WINEDEBUG=warn
Sequence Editor 6.4.18 from Legendary Explorer of ME3Tweaks Mod Manager 9.0
(Tools->Legendary Explorer) triggers assert from Wine code base
"err:msvcrt:_wassert (L"graphics->hdc_refs ==
0",L"dlls/gdiplus/graphics.c",2621)". Executing with WINEDEBUG=warn+heap shows
the following warning "warn: Using GDI for swapchain presentation. This will
impact performance." which belongs to
https://github.com/doitsujin/dxvk/blob/master/src/d3d9/d3d9_swapchain.cpp#L…
The assert is triggered when trying to add a BioSeqVar_StoryManagerX variable
where X is one of {Bool,Float,Int,StateId}. I have not tried all other object
types. But from the Variables tab it only crashes when double clicking in any
of those four.
The PCC file opened with the Sequence Editor can be downloaded here:
https://drive.proton.me/urls/GSMNK9XPF8#MHMpgEs2uYHe
You have to configure Wine to emulate a virtual desktop. Otherwise tooltips and
menus appear as black rectangles.
### Software information
Legendary Explorer 6.4.18 from ME3Tweaks Mod Manager 9.0.
### System information
- GPU: AMD Radeon VII (RADV VEGA20)
- Driver: radv 24.1.3
- Wine version: wine-9.13
### Apitrace file(s)
https://drive.proton.me/urls/DGQS3343J4#0BDgJCGU0pfz
--
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.