https://bugs.winehq.org/show_bug.cgi?id=39930
Bug ID: 39930
Summary: HtmlHelp() shows blank page when '\\' is used as path
separator after '::'
Product: Wine
Version: 1.9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hhctrl.ocx
Assignee: wine-bugs(a)winehq.org
Reporter: foka(a)debian.org
Distribution: ---
Despite the fact that Microsoft documentation clearly states that
Anything after the double colon (::) must use forward slashes (/),
in accordance with URL standards.
(see https://support.microsoft.com/en-us/kb/235226), Windows developers tend to
forget(?) that rule and use backslashes (\) after the double colon.
For example, running UFile 2013 under Wine, opening the tutorial comes up with
a blank window, and the trace/fixme messages are logged:
trace:htmlhelp:HtmlHelpW (0x1006e,
L"ubxkbE.chm::\\tutorial/pages/1intro.htm>DT_HTML_TUT",
command=HH_DISPLAY_TOPIC, data=0)
trace:htmlhelp:NavigateToChm 0x208ba0 L"C:\\Program Files\\UFile
2013\\ubxkbE.chm" L"\\tutorial/pages/1intro.htm"
trace:htmlhelp:AppendFullPathURL L"C:\\Program Files\\UFile
2013\\ubxkbE.chm" 0x31dc98 L"\\tutorial/pages/1intro.htm"
trace:htmlhelp:navigate_url L"mk:@MSITStore:C:\\Program Files\\UFile
2013\\ubxkbE.chm::/\\tutorial/pages/1intro.htm"
fixme:ieframe:handle_navigation_error Navigate to error page
But of course, as a retail product, UFile 2013's tutorial of course shows
correctly in Windows.
Apparently, Microsoft knows how often developers get confused by '/' and '\',
and silently accepts such erroneous backslashes so that the relevant HTML Help
can be displayed.
The current Wine implementation of HTML Help, however, does not account for
such developer errors, leading to such blank HTML Help windows in (slightly)
buggy programs like UFile 2013.
--
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=53897
Bug ID: 53897
Summary: Programmer's File Editor MDI windows initially open
with doubled-up scroll bars
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine_bugzilla(a)sctb.ch
Distribution: ---
Created attachment 73438
--> https://bugs.winehq.org/attachment.cgi?id=73438
Screenshot of doubled-up scroll bars.
I've been using Programmer's File Editor (PFE), a text editor from 1999, with
WINE, since the beginning of time.
There has always been a problem that when the editor starts, the scroll bars
(vertical and horizontal) are doubled up. It's an MDI interface, which I think
is the problem.
Clicking on a scrollbar, tiling the windows, etc - anything which makes them do
something - returns the scrollbars to the normal state.
Screenshot attached.
--
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=54122
Bug ID: 54122
Summary: Call of Juarez - Bound in Blood in-menu videos don't
work
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: VladimirVSC(a)yandex.ru
Distribution: ---
Created attachment 73655
--> https://bugs.winehq.org/attachment.cgi?id=73655
The output of missing videos
The video-animated background into the main menu doesn't work. The same for 7.0
and 8.0-rc1. The output included.
--
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=54031
Bug ID: 54031
Summary: user32:msg - test_SendMessage_other_thread() broken by
WM_WINDOWPOSCHANGING on Windows dual-monitor configs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_SendMessage_other_thread() sometimes gets an unexpected
WM_WINDOWPOSCHANGING message:
msg.c:19053: Test failed: wrong status 00480048
msg.c:19091: Test failed: SendMessage from other thread 5: 0: the msg sequence
is not complete: expected 0000 - actual 0046
msg.c:19091: Failed sequence SendMessage from other thread 5:
msg.c:19091: 0: expected: nothing - actual: MsgCheckProc: 006F025C
WM_WINDOWPOSCHANGING wp 00000000 lp 0022fc40 after 00000000 x 100 y 100 cx 200
cy 200 flags SWP_NOACTIVATE|SWP_NOZORDER (flags 19)
msg.c:19091: 1: expected: nothing - actual: MsgCheckProc: 006F025C 0024 wp
00000000 lp 0022f700 (flags 39)
msg.c:19059: Failed sequence SendMessage from other thread 1:
msg.c:19059: 0: expected: msg 0402 - actual: MsgCheckProc: 007102CA 0402 wp
00000000 lp 00000000 (flags 19)
msg.c:19059: 1: expected: msg 0400 - actual: MsgCheckProc: 007102CA 0400 wp
00000000 lp 00000000 (flags 19)
msg.c:19079: Failed sequence SendMessage from other thread 3:
msg.c:19079: 0: expected: msg 0403 - actual: MsgCheckProc: 007102CA 0403 wp
00000000 lp 00000000 (flags 19)
msg.c:19079: 1: expected: msg 0401 - actual: MsgCheckProc: 007102CA 0401 wp
00000000 lp 00000000 (flags 19)
[53435] msg.c:19087: Test failed: wrong status 00400040
msg.c:19091: Failed sequence SendMessage from other thread 5:
msg.c:18487: Failed sequence SetFocus on a desktop window:
msg.c:18497: Failed sequence SetFocus on another thread window:
msg.c:18517: Failed sequence SetActiveWindow on a desktop window:
msg.c:18527: Failed sequence SetActiveWindow on another thread window:
msg.c:18592: Failed sequence SetFocus on a child window:
msg.c:18592: 0: expected: hook 0009 - actual: CBT: hook 9 (HCBT_SETFOCUS) wp
005e0252 lp 002f0278
msg.c:12896: QS_RAWINPUT not supported on this platform
msg.c:12921: Test failed: wrong qstatus 00000000
See https://test.winehq.org/data/patterns.html#user32:msg
This seems to only happen on dual-monitor configurations, most frequently on
w1064-2qxl but also regularly on w7u-2qxl.
--
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=52571
Bug ID: 52571
Summary: batch token parsing regression
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: dragonwarriorxtreme(a)gmail.com
Distribution: ---
This is easily demonstrated with vcvars script batch files in Visual Studio
2015, on amd64.
>)
>)
>)
>)
>)
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\;C:\windows\system32;C:\win
dows;C:\windows\system32\wbem;C:\windows\system32\WindowsPowershell\v1.0' as an
internal or external
command, or batch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Windows Kits\NETFXSDK\4.6.1\include\um;' as an internal or external command, or bat
ch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Windows Kits\NETFXSDK\4.6.1\lib\um\x86;' as an internal or external command, or bat
ch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
>Can't recognize '\Microsoft Visual Studio 14.0\Team Tools\Performance Tools\x64;C:\Program Files ' as
an internal or external command, or batch script.
>Can't recognize 'x86' as an internal or external command, or batch script.
... etc ...
1. Install Visual Studio 2015 (latest Wine-git works around ncrypt limitations)
or the v140/v141 build tools using 2017 (already works).
What I did personally (was attempting to compile x86 programs on an x64 install
before I hit this bug):
2. cd C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64_x86
3. wine cmd /K vcvarsamd64_x86.bat
--
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=55031
Bug ID: 55031
Summary: experimental wow64 mode: crashes in some 3d graphics
code
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: idarktemplar(a)mail.ru
Distribution: ---
Created attachment 74591
--> https://bugs.winehq.org/attachment.cgi?id=74591
wine.crash.log
When I'm trying to run Spellforce 2 with experimental wow64 wine mode, it
crashes. When I'm running it using normal multilib setup, everything runs fine,
at least until main menu, didn't check again further.
Same happens when I'm trying to run Torchlight 2 from Steam. Demo available on:
https://store.steampowered.com/app/200710/Torchlight_II/
Crashing wine build options: ./configure --with-mingw
--enable-archs='i386,x86_64' --prefix=/tmp/wineinstall
Suspicious log lines just before crash:
0114:fixme:opengl:wow64_map_buffer GL_MAP_PERSISTENT_BIT not supported!
wine: Unhandled page fault on write access to 5BFFF000 at address 6AB23144
(thread 0114), starting debugger...
OS: Gentoo Linux amd64 (64bit)
Graphics: X11
Videocard information:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro K1000M/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.182.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
--
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=55246
Bug ID: 55246
Summary: ntdll:om - The 64-bit test_object_types() crashes on
Windows 8+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:om - The 64-bit test_object_types() crashes on Windows 8+:
om.c:2325: this is the last test seen before the exception
1c98:om: unhandled exception c0000005 at 00007FFFC32A60AB
See https://test.winehq.org/data/patterns.html#ntdll:om
Where c0000005 == STATUS_ACCESS_VIOLATION
This started on 2023-07-10 which corresponds to the GitLab CI switch to Debian
12 for builds which means it is caused by the commit below:
commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Jul 10 17:18:49 2023 +0200
gitlab: Upgrade the Debian image to bookworm.
Note that, to this day, the 64-bit binaries produced by the TestBot still run
successfully on Windows because they are built on Debian 11. But the nightly
WineTest runs fail because they use the official WineTest binaries produced by
the GitLab CI which uses Debian 12.
--
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=54331
Bug ID: 54331
Summary: Game "Antecrypt": Black screen after launch
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stabilergriller(a)gmail.com
Distribution: ---
Created attachment 73894
--> https://bugs.winehq.org/attachment.cgi?id=73894
Output when running "wine beam.exe"
This shooting game from https://punkcake.itch.io/antecrypt just opens up a
window which is completely black.
I confirm that this game runs on Windows 10.
My set up:
OS: Arch 64-Bit
GPU: Intel HD Graphics 610
Mesa: 22.3.3
Kernel version: 6.1.5
--
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=55237
Bug ID: 55237
Summary: oleaut32:usrmarshal - test_marshal_VARIANT() gets bad
values for wv[5&6] on Windows 8+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
oleaut32:usrmarshal - test_marshal_VARIANT() gets bad values for wv[5&6] on
Windows 8+:
usrmarshal.c:1628: Test failed: wv[5] c560c9d1
usrmarshal.c:1697: Test failed: wv[6] c560cad1
See https://test.winehq.org/data/patterns.html#oleaut32:usrmarshal
Note that the hash values change with every run, thus causing false positives.
--
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=42809
Bug ID: 42809
Summary: GPS Track Editor: arrows not shown
Product: Wine
Version: 1.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joao.eiras(a)gmail.com
Distribution: ---
Created attachment 57847
--> https://bugs.winehq.org/attachment.cgi?id=57847
Example GPX file
1. Please download and install "GPS Track Editor" from
http://www.gpstrackeditor.com/download (7.6 MB isntaller)
2. Open the program
3. Open a GPX file (use the attached one, over the brooklyn bridge)
4. Notice how do don't see anything over the bridge but if you hover with the
mouse you'll see some dots appearing. The dots also appear if you click the
entries in the table on the right side. See attached screenshot.
5. Compare how it should look like on windows (another 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=55366
Bug ID: 55366
Summary: The GitLab CI sometimes tries to link winscard with
libpcsclite on macOS
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The GitLab CI sometimes tries to link winscard with libpcsclite on macOS and
fails.
For instance in MR!3459:
ld: library not found for -lpcsclite
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [dlls/winscard/winscard.so] Error 1
This issue started with commit f74c4af257e0 but the root cause looks more like
it has to do with the way the GitLab CI caches the configure information.
MR!3389 may have more details.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3389
--
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=54945
Bug ID: 54945
Summary: ntdll:exception - test_virtual_unwind() fails on
Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:exception - test_virtual_unwind() fails on Windows 11:
exception.c:2132: Test failed: 0/8: wrong frame
000000000076F598/000000000076F480
exception.c:2132: Test failed: 0/9: wrong frame
000000000076F478/000000000076F480
exception.c:2132: Test failed: 0/10: wrong frame
000000000076F470/000000000076F480
There are also a lot of possibly related traces.
See https://test.winehq.org/data/patterns.html#ntdll:exception
The addresses changes sometimes, thus causing false positives. These failures
above are also not systematic and only happen in the 64-bit tests. They also
seem to be unrelated to the ntdll:exception crashes (see bug 54944).
--
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=51561
Bug ID: 51561
Summary: Wine's built-in gdiplus.dll lags in Paint.NET compared
to native (Win 7) gdiplus.dll
Product: Wine
Version: 6.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: kle(a)bluewin.ch
Distribution: ---
After intensive testing I can confirm that the built-in gdiplus.dll "lags" in
Paint.NET 3.5.11 and Wine 6.13 / 6.14.
When the native gdiplus.dll from Windows 7 is used (through winetricks) the
performance is clearly better, no lag is present. Unfortunately the native
gdiplus.dll works not stable, Paint.NET 3.5.11 crashes reproducible after some
time. So this is therefore not an usable alternative.
Maybe this bug report here is related to bug 24653:
https://bugs.winehq.org/show_bug.cgi?id=24653
--
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=55244
Bug ID: 55244
Summary: mshtml:misc - The 32-bit test_HTMLStorage() crashes in
Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
mshtml:misc - The 32-bit test_HTMLStorage() crashes in Wine:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x10045300).
Backtrace:
=>0 0x10045300 in xul (+0x45300) (0x000000d2)
0x10045300 xul+0x45300: movl $0x25c, 0x00000000
See https://test.winehq.org/data/patterns.html#mshtml:misc
A bisect shows that the failures started with the commit below:
commit 24a2b625545f1875b5c3177f2b9da1b7299b864f
Author: Victor Chiletto <vchiletto(a)codeweavers.com>
Date: Thu Jun 8 15:14:57 2023 -0300
msvcrt: Use snames instead of LCIDs in create_locinfo.
And adding traces shows that the crash happens when releasing doc2:
535: IHTMLDocument2_Release(doc2);
Sometimes the backtrace is more useful:
Backtrace:
=>0 0x6ab1c9b5 in ucrtbase (+0x5c9b5) (0x0a26e4a0)
1 0x033d6536 Cert_clone+0xb6(context=<is not available>, store=<is not
available>, use_link=<is not available>) [/home/fgo
uget/wine/wt23/src/dlls/crypt32/cert.c:148] in crypt32 (0x0a26e4a0)
2 0x034280a4 MemStore_addContext+0x24(store=083F6948, list=<internal error>,
orig_context=<internal error>, existing=<is not available>, ret_context=<is not
available>, use_link=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/crypt32/store.c:149] in crypt32 (0x0a26e4f0)
3 0x033d9406 add_cert_to_store+0xf6(store=083F6948, cert=00000001,
add_disposition=<internal error>, use_link=<is not available>, ret_context=<is
not available>) [/home/fgouget/wine/wt23/src/dlls/crypt32/cert.c:267] in
crypt32 (0x0a26e570)
4 0x033d99e3 CertAddCertificateContextToStore+0x1b(ppStoreContext=<internal
error>, dwAddDisposition=<internal error>, pCertContext=<internal error>,
hCertStore=<internal error>)
[/home/fgouget/wine/wt23/src/dlls/crypt32/cert.c:289] in crypt32 (0x0a26e5c0)
5 0x033d99e3 CertAddEncodedCertificateToStore+0x53(hCertStore=<is not
available>, dwCertEncodingType=<is not available>, pbCertEncoded=<is not
available>, cbCertEncoded=<is not available>, dwAddDisposition=<is not
available>, ppCertContext=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/crypt32/cert.c:64] in crypt32 (0x0a26e5c0)
6 0x0fcf6aa0 ensure_remote_cert+0x190(ctx=<internal error>)
[/home/fgouget/wine/wt23/src/dlls/secur32/schannel.c:1131] in secur32
(0x0a26e640)
7 0x0fcfa74d schan_QueryContextAttributesW+0xcd(context_handle=<is not
available>, attribute=<is not available>, buffer=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/secur32/schannel.c:1207] in secur32
(0x0a26eab0)
8 0x6c1320a9 netcon_secure_connect_setup+0x509(connection=<internal error>,
compat_mode=<internal error>)
[/home/fgouget/wine/wt23/src/dlls/wininet/netconnection.c:545] in wininet
(0x0a26ed00)
9 0x6c133438 NETCON_secure_connect+0x38(connection=<is not available>,
server=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/wininet/netconnection.c:615] in wininet
(0x0a26ed20)
10 0x6c11fc03 HTTP_HttpSendRequestW+0x1293(request=<internal error>,
lpszHeaders=<internal error>, dwHeaderLength=<internal error>, lpOptional=<is
not available>, dwOptionalLength=<is not available>, dwContentLength=<is not
available>, bEndRequest=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/wininet/http.c:5093] in wininet (0x0a26fdb0)
11 0x6c120adf AsyncHttpSendRequestProc+0x3f(hdr=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/wininet/http.c:5356] in wininet (0x0a26fde0)
12 0x6c124e78 INTERNET_WorkerThreadFunc+0x18(lpvParam=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/wininet/internet.c:4029] in wininet
(0x0a26fe00)
13 0x7bc5b6fb process_rtl_work_item+0x1b(instance=<is not available>,
userdata=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/ntdll/threadpool.c:410] in ntdll (0x0a26fe30)
14 0x7bc5c7b2 tp_object_execute+0x3a2(object=<register EBX not accessible in
this frame>, wait_thread=<internal error>)
[/home/fgouget/wine/wt23/src/dlls/ntdll/threadpool.c:2221] in ntdll
(0x0a26fed0)
15 0x7bc5cb88 threadpool_worker_proc+0x198(param=<is not available>)
[/home/fgouget/wine/wt23/src/dlls/ntdll/threadpool.c:2356] in ntdll
(0x0a26ff30)
--
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=55227
Bug ID: 55227
Summary: wtsapi32:wtsapi - check_wts_process_info() fails to
get the user token on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: wtsapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
wtsapi32:wtsapi - check_wts_process_info() fails to get the user token on
Windows 7:
wtsapi.c:94: Test failed: pid 0x544: failed to get token user, error 998
wtsapi.c:95: this is the last test seen before the exception
0fc0:wtsapi: unhandled exception c0000005 at 772ADF96
See https://test.winehq.org/data/patterns.html#wtsapi32:wtsapi
Where 998 == ERROR_NOACCESS
--
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=55225
Bug ID: 55225
Summary: kernel32:thread - test_stack() gets an unexpected
values for -2 & -3 indexes on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:thread - test_stack() gets an unexpected stack[-2] value on Windows:
thread.c:1180: Test failed: wrong data 0358FFF8 = 00000000
thread.c:1181: Test failed: wrong data 0358FFF4 = 00000000
See https://test.winehq.org/data/patterns.html#kernel32:thread
Where the first value depends on the stack pointer and changes with every run,
thus causing false positives.
--
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=54683
Bug ID: 54683
Summary: shlwapi:ordinal - test_SHFormatDateTimeA() fails due
to daylight saving time on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shlwapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shlwapi:ordinal - test_SHFormatDateTimeA() fails due to daylight saving time on
Windows:
ordinal.c:1734: Test failed: expected (12:00 PM), got (11:00 AM)
ordinal.c:1741: Test failed: expected (12:00:00 PM), got (11:00:00 AM)
ordinal.c:1749: Test failed: expected (12:00:00 PM), got (11:00:00 AM)
ordinal.c:1779: Test failed: expected (12:00 PM), got (11:00 AM) for time part
ordinal.c:1793: Test failed: expected (12:00:00 PM), got (11:00:00 AM) for time
part
ordinal.c:1811: Test failed: expected (2/14/2023 12:00 PM), got (2/14/2023
11:00 AM)
ordinal.c:1822: Test failed: expected (2/14/2023 12:00:00 PM), got (2/14/2023
11:00:00 AM)
See https://test.winehq.org/data/patterns.html#shlwapi:ordinal
The AM/PM translations can change the failure messages slightly but it's always
the same issue, on all Windows versions... except w10pro64v2004!
This set of failures started on 2023-03-13 which, together with the 1 hour
offset, clearly corresponds to the switch from CST to CDT (there was no
WineTest run on Sunday).
--
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=55317
Bug ID: 55317
Summary: user32:msg - test_hotkey() finds no free WinKey+letter
on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_hotkey() finds no free WinKey+letter on Windows 11:
msg.c:18487: Test failed: Couldn't find any free Windows Key + letter
combination
See https://test.winehq.org/data/patterns.html#user32:msg
--
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=54368
Bug ID: 54368
Summary: ::DrawGeometry doesn't respect stroke style
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Distribution: ---
Created attachment 73938
--> https://bugs.winehq.org/attachment.cgi?id=73938
thick lines
There's an application that uses d2d1 to draw its UI, and when the app scales
its workspace the lines get very thick shapes. This seems to be related to
00d8:fixme:d2d:d2d_stroke_style_init transformType 1 is not supported
00d8:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style
000000001F3D8C80.
According to MSDN transformType 1 refers to D2D1_STROKE_TRANSFORM_TYPE_FIXED:
The stroke does not respect the world transform but it does respect the dpi and
stroke width.
--
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=53435
Bug ID: 53435
Summary: user32:msg - test_SendMessage_other_thread() sometimes
fails on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_SendMessage_other_thread() sometimes fails on Windows 7:
msg.c:18505: Test failed: wrong status 00400040
https://test.winehq.org/data/patterns.html#user32:msg
Where 0x00400040 that there are still QS_SENDMESSAGE messages in the queue and
that one was added since the last call.
This is similar to the Windows 10-only bug 53434 but the status is different
and this failure only happens on Windows 7.
--
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=52196
Bug ID: 52196
Summary: Program desinger.exe stop after starting with error
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: werbung(a)itssh.de
Distribution: ---
Created attachment 71249
--> https://bugs.winehq.org/attachment.cgi?id=71249
Bugreport
The install of this program was completed with no errors. It was installed
along with another program. The main program works wonderfully, but the
sub-program (desinger.exe) does not.
The OS is up to date. Wine is up to date.
In OS windows7 the program works.
--
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=54998
Bug ID: 54998
Summary: DnsQuery(DNS_TYPE_SRV) fails to parse some of the
server answers
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: patch, source
Severity: normal
Priority: P2
Component: dnsapi
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Distribution: ---
Created attachment 74551
--> https://bugs.winehq.org/attachment.cgi?id=74551
patch
An application that uses ActiveDs sometimes fails to get domain DC using
DsGetDcNameW(). That's caused by a failing call to
DnsQuery("_ldap._tcp.dc._msdcs.domain.com", DNS_TYPE_SRV)
which in turn fails because DnsExtractRecordsFromMessage_UTF8() fails to parse
some of the server answers.
It looks like this happens because in the DNS_TYPE_SRV record name is the last
element, and in that case get_name() uses wrong boundary check and returns
NULL.
Just in case it will be useful I'm attaching my version of the fix with some
tests.
It seems that skip_name() also uses wrong boundary check, however usually some
other data follows the skipped name, so it currently doesn't cause failures.
--
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=54655
Bug ID: 54655
Summary: user32:msg - test_InSendMessage() sometimes gets
unexpected flags on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_InSendMessage() sometimes gets unexpected flags on Windows:
msg.c:11738: Tests skipped: cannot set global hook
msg.c:19232: Failed sequence SendMessage from other thread 1:
msg.c:19232: 0: expected: msg 0402 - actual: MsgCheckProc: 00000000008B03E8
0402 wp 00000000 lp 00000000 (flags 19)
msg.c:19232: 1: expected: msg 0400 - actual: MsgCheckProc: 00000000008B03E8
0400 wp 00000000 lp 00000000 (flags 19)
msg.c:19252: Failed sequence SendMessage from other thread 3:
msg.c:19252: 0: expected: msg 0403 - actual: MsgCheckProc: 00000000008B03E8
0403 wp 00000000 lp 00000000 (flags 19)
msg.c:19252: 1: expected: msg 0401 - actual: MsgCheckProc: 00000000008B03E8
0401 wp 00000000 lp 00000000 (flags 19)
msg.c:19264: Failed sequence SendMessage from other thread 5:
msg.c:19292: Test failed: wrong flags a
msg.c:18660: Failed sequence SetFocus on a desktop window:
See https://test.winehq.org/data/patterns.html#user32:msg
Where 0xa == ISMEX_NOTIFY | ISMEX_REPLIED
and the test expected 0x9 == ISMEX_SEND | ISMEX_REPLIED
This happens about once per month and impacts at least Windows 7 & 10,
regardless of locale:
* 2022-08-31 on w7u-pt-PT 32-bit
* 2022-08-31 on w7u 32-bit
* 2022-09-06 on w7u 32-bit
* 2022-09-15 on w7u-pt-PT 32-bit
* 2022-12-12 on w1064 32-bit
* 2023-02-20 on w10pro64-ar 64-bit
* 2023-03-02 on w7u-de 32-bit
--
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=54202
Bug ID: 54202
Summary: user32:msg - subtest_hvredraw() fails on most Windows
7 test configurations
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - subtest_hvredraw() fails on most Windows 7 test configurations
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #2 (0, 0, 50, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #3 (0, 0, -50, -50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos
redraw #4 (-50, -50, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #2 (0, 0, 50, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #3 (0, 0, -50, -50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos
redraw #5 (-50, -50, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #2 (0, 0, 50, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos
redraw #3 (0, 0, -50, -50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 40800000 SetWindowPos
redraw #0 (0, 0, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 40800000 SetWindowPos
redraw #4 (-50, -50, 0, 50): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 40800000 SetWindowPos
redraw #1 (0, 0, 50, 0): Update region shall match expected region
msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 40800000 SetWindowPos
redraw #5 (-50, -50, 50, 0): Update region shall match expected region
msg.c:9764: Test failed: destroy child on thread exit: 1: the msg sequence is
not complete: expected 000f - actual 0000
msg.c:9764: Failed sequence destroy child on thread exit:
msg.c:9764: 0: expected: msg 0082 - actual: MsgCheckProc: 00BC00A0 0082 wp
00000000 lp 00000000 (flags 19)
msg.c:9764: 1: expected: msg 000f - actual: nothing
See https://test.winehq.org/data/patterns.html#user32:msg
These failures appeared as soon as the corresponding tests were introduced but
somehow the TestBot did not detect them when MR!1874 was submitted. So maybe
they are caused by interference from a previous Wine test.
commit b2a9445e155487f1b47a646b70edbe181a905454
Author: Jinoh Kang <jinoh.kang.kr(a)gmail.com>
Date: Thu Dec 22 01:20:59 2022 +0900
user32/tests: Add tests for CS_HREDRAW and CS_VREDRAW.
--
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=55354
Bug ID: 55354
Summary: user32:msg - test_dialog_messages() sometimes gets a
bad sequence on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_dialog_messages() sometimes gets a bad message sequence on
Windows 7:
msg.c:15393: Test failed: CreateDialogParam_1: 17: the msg 0x001c was expected,
but got msg 0x000d instead
msg.c:15393: Test failed: CreateDialogParam_1: 18: the msg 0x0086 was expected,
but got msg 0x0083 instead
msg.c:15393: Test failed: CreateDialogParam_1: 19: the msg 0x0006 was expected,
but got msg 0x800b instead
msg.c:15393: Test failed: CreateDialogParam_1: 20: the msg 0x8005 was expected,
but got msg 0x001c instead
msg.c:15393: Test failed: CreateDialogParam_1: 21: the msg 0x0007 was expected,
but got msg 0x0086 instead
msg.c:15393: Test failed: CreateDialogParam_1: 23: the msg sequence is not
complete: expected 0000 - actual 0006
See https://test.winehq.org/data/patterns.html#user32:msg
Where: 0x0006 == WM_ACTIVATE
0x000d == WM_GETTEXT
0x001c == WM_ACTIVATEAPP
0x0083 == WM_NCCALCSIZE
0x0086 == WM_NCACTIVATE
0x8005 == EVENT_OBJECT_FOCUS
0x800b == EVENT_OBJECT_LOCATIONCHANGE
This first happened on 2023-06-22 and there has been about one instance per
week since, always receiving the same unexpected message sequence:
* 2023-06-22 win7_newtb-w7u-2qxl
* 2023-06-28 win7_newtb-w7u-es
* 2023-07-05 win7_newtb-w7u-2qxl
* 2023-07-27 win7_newtb-w7u-2qxl
--
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.