https://bugs.winehq.org/show_bug.cgi?id=54299
Bug ID: 54299
Summary: d3d12:d3d12 - test_create_device() gets an unexpected
0 refcount on Windows 10 1909+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d12:d3d12 - test_create_device() gets an unexpected 0 refcount on Windows 10
1909+:
d3d12.c:888: Test failed: Got unexpected refcount 0.
See https://test.winehq.org/data/patterns.html#d3d12:d3d12
This test
* is skipped on Windows 10 < 1709,
* succeeds on Windows 10 1709 and 1809,
* and fails on Windows 10 1909+ because the refcount is 0.
The test seems unsure about the exact refcount value since it only tests for
"refcount >= 1".
Maybe it should be something like "refcount == 0 || broken(refcount >= 1)",
possibly with a todo_wine?
Or that test could just be removed entirely?
--
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=54637
Bug ID: 54637
Summary: riched20:txtsrv - test_TxGetNaturalSize fails if
system GUI font's glyph widths are wider than expected
by the test
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: huw(a)codeweavers.com, jzeng(a)codeweavers.com
Regression SHA1: 6e264bbd1ddf0d271d4506462ecd4f20f4a20597
Distribution: ---
Today, test_TxGetNaturalSize() creates a pop-up window with a fixed size
(extent) of 100 x 100. The test function then proceeds to compute the
natural size of rich edit control that fits the sample text
"TestSomeText" and compare it to the RECT calculated by DrawText.
It appears that this test fails if the text width exceeds the width of
the test window's client area. In this case, DrawText() with
DT_WORDBREAK breaks the text into the two lines due to text wrapping;
however, Rich Edit's ITextServices::TxGetNaturalSize implementation does
not seem to perform text wrapping on overflow. This results in extent
mismatch.
In conclusion, the test may fail if the rendered width of the sample
text "TestSomeText" is larger than what the test expects. This depends
on the current font used for DEFAULT_GUI_FONT.
Omitting DT_WORDWRAP for the DrawText() call seems to fix this test failure.
--
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=54506
Bug ID: 54506
Summary: psapi:psapi_main - The 64-bit
test_EnumProcessModulesEx() gets pcs-6464 and pcs-6432
failures on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 64-bit test_EnumProcessModulesEx() gets pcs-6464 and
pcs-6432 failures on Windows 11:
psapi_main.c:303: Test failed: pcs-6464: 2: expecting
C:\windows\system32\notepad.exe but got C:\Program
Files\WindowsApps\Microsoft.WindowsNotepad_10.2102.13.0_x64__8wekyb3
psapi_main.c:303: Test failed: pcs-6464: 0: expecting
C:\windows\system32\notepad.exe but got C:\Program
Files\WindowsApps\Microsoft.WindowsNotepad_10.2102.13.0_x64__8wekyb3
psapi_main.c:303: Test failed: pcs-6464: 3: expecting
C:\windows\system32\notepad.exe but got C:\Program
Files\WindowsApps\Microsoft.WindowsNotepad_10.2102.13.0_x64__8wekyb3
psapi_main.c:448: Test failed: pcs-6432: expecting 32bit modules
psapi_main.c:299: Test failed: pcs-6432: 1: got error 6
psapi_main.c:300: Test failed: pcs-6432: 1: expecting notepad.exe but got e{u
psapi_main.c:302: Test failed: pcs-6432: 1: got error 6
psapi_main.c:303: Test failed: pcs-6432: 1: expecting
C:\windows\syswow64\notepad.exe but got e{u
psapi_main.c:306: Test failed: pcs-6432: 1: got error 6
psapi_main.c:307: Test failed: pcs-6432: 1: expected 00000000DEADBEEF, got
00007FF8DF7EF800
psapi_main.c:309: Test failed: pcs-6432: 1: got entry point 000000000040BDF8
psapi_main.c:303: Test failed: pcs-6432: 0: expecting
C:\windows\syswow64\notepad.exe but got C:\Program
Files\WindowsApps\Microsoft.WindowsNotepad_10.2102.13.0_x64__8wekyb3
psapi_main.c:303: Test failed: pcs-6432: 3: expecting
C:\windows\syswow64\notepad.exe but got C:\Program
Files\WindowsApps\Microsoft.WindowsNotepad_10.2102.13.0_x64__8wekyb3
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
Where 6 == ERROR_INVALID_HANDLE, hence the presumable uninitialized strings
too.
These tests and failures were introduced by the commit below:
commit 84a9a1c8fbc1e8ccc9c34cf0db375813b3ac2955
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Mon Jan 30 13:45:46 2023 +0100
psapi: Add tests for EnumProcessModulesEx().
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
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=54313
Bug ID: 54313
Summary: HS_hevo_gc 8.8.1.1 fails to launch
Product: Wine
Version: 8.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dean-chen(a)qq.com
Distribution: ---
Created attachment 73873
--> https://bugs.winehq.org/attachment.cgi?id=73873
log info copied from terminal
HS_hevo_gc 8.8.1.1 fails to launch
THS_hevo_gc8.8.1.1.exe can be dowloaded from THS web site on Windows system.
http://activity.ths123.com/html/xb/160809/index.html
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54058
Bug ID: 54058
Summary: user32:input - test_ToAscii() fails in the Hindi UTF-8
locale
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
Created attachment 73613
--> https://bugs.winehq.org/attachment.cgi?id=73613
user32/tests: Skip a ToAscii() test in UTF-8 code pages.
user32:input - test_ToAscii() fails in the Hindi UTF-8 locale:
input.c:3133: Test failed: ToAscii for character 'A' didn't return 1 (was 0)
See https://test.winehq.org/data/patterns.html#user32:input
Note that this did not happen before 2022-11-21 because some unknown Windows
quirk caused the UserDefaultLCID and ThreadLocale to be reset to English before
the test was started.
In any case it seems ToAscii() does not depend just on the keyboard layout but
also on the current code page which makes sense. So then maybe we should limit
the test to non-UTF-8 code pages as in the attached patch?
--
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=54020
Bug ID: 54020
Summary: The 32-bit ntdll:wow64 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
The 32-bit ntdll:wow64 fails on Windows 11:
wow64.c:254: Test failed: wrong len 0
wow64.c:255: Test failed: wrong teb 0000004C / 00000000
wow64.c:258: Test failed: GdiBatchCount not set
wow64.c:282: Test failed: wrong peb 00000000 / 00000002
wow64.c:285: Test failed: wrong len 0
wow64.c:295: Test failed: wrong len 0
wow64.c:301: Test failed: wrong ImagePathName ptr 00000000 / 00000000-00000000
wow64.c:302: Test failed: wrong CommandLine ptr 00000000 / 00000000-00000000
wow64.c:303: Test failed: wrong WindowTitle ptr 00000000 / 00000000-00000000
wow64.c:304: Test failed: wrong Desktop ptr 00000000 / 00000000-00000000
wow64.c:305: Test failed: wrong ShellInfo ptr 00000000 / 00000000-00000000
wow64.c:331: Test failed: debugging failed
wow64.c:333: Test failed: wrong len 0
wow64.c:460: cs 0023 ss 002b fs 0053
wow64.c:782: Test failed: unknown module 7ffb1ed00000 L"wow64base.dll" found
wow64.c:782: Test failed: unknown module 7ffb20100000 L"wow64con.dll" found
See https://test.winehq.org/data/patterns.html#ntdll:wow64
The values are pretty stable from one run to the next but do change from time
to time (causing false positives). Note also that the 64-bit version fails on
Windows 11 too but the failures there are pretty different (see bug 54019).
--
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=53818
Bug ID: 53818
Summary: foobar2000 crashes shortly after startup
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matthias.grobarek(a)posteo.de
Distribution: ---
Created attachment 73344
--> https://bugs.winehq.org/attachment.cgi?id=73344
winedbg output
After starting foobar2000, it quickly crashes after a few seconds, no matter
what you do. Wine 7.18 and 7.17 are not affected.
I’m using wine-staging (no matter the version) on Gentoo Linux (kernel 6.0.2),
compiled for both 32bit and 64bit, with the following flags activated: x, alsa,
fontconfig, mshtml, gstreamer, mingw, mscoree, gettext, openal, opengl, sdl,
gnutls, freetype, udev, dbus, unwind, usb, vulkan, xcomposite.
I attached the output of winedbg and also the crash log and dump that
foobar2000 itself produces. If you need any more information, please tell me
what exactly I should do.
--
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=53526
Bug ID: 53526
Summary: kernel32:sync - test_timer_queue() occasionally fails
to delete the timer on Windows 10
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:sync - test_timer_queue() occasionally fails to delete the timer on
Windows 10:
sync.c:1135: Test failed: DeleteTimerQueueTimer
https://test.winehq.org/data/patterns.html#kernel32:sync
This failure happened twice:
* 2022-05-27 w10pro64-de-64
* 2022-08-04 w10pro64-he-64
--
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=53488
Bug ID: 53488
Summary: The dxgi:dxgi output is too big on debiant
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The dxgi:dxgi output is too big in Wine.
It used to be about 24 KB but the commit below pushed it to 34 KB, over the 32
KB limit.
Then on 2022-07-22 another commit improved the situation on debian11 but not on
debiant where the size has not changed since the commit below.
commit 184ff3bfbb4be3e3fbcfaaba3ec7095d2d885882
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Sat Jun 11 19:36:20 2022 +0300
dxgi: Create DXGI resource object, optionally supporting surface
interfaces.
Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com>
dlls/d3d11/d3d11_private.h | 4 +-
dlls/d3d11/tests/d3d11.c | 7 -
dlls/d3d11/texture.c | 130 +++++++-------
dlls/dxgi/Makefile.in | 2 +-
dlls/dxgi/device.c | 24 +--
dlls/dxgi/dxgi_private.h | 11 +-
dlls/dxgi/resource.c | 423 +++++++++++++++++++++++++++++++++++++++++++++
dlls/dxgi/surface.c | 296 -------------------------------
dlls/dxgi/tests/dxgi.c | 34 ++--
include/wine/winedxgi.idl | 7 +-
10 files changed, 526 insertions(+), 412 deletions(-)
create mode 100644 dlls/dxgi/resource.c
delete mode 100644 dlls/dxgi/surface.c
--
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=54553
Bug ID: 54553
Summary: mmdevapi:propstore - The 32-bit
test_setvalue_on_wow64() fails on Windows 10 2004+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mmdevapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mmdevapi:propstore - The 32-bit test_setvalue_on_wow64() fails on Windows 10
2004+:
propstore.c:186: Test failed: Wrong error when opening mmdevices Render key: 0
See propstore.c:186: Test failed: Wrong error when opening mmdevices Render
key: 0
As far as I can tell what this means is that the assumption that "should NOT
find the key in 32-bit view" is incorrect on Windows 10 2004+.
So maybe the old behavior should be considered to be broken() nowadays?
--
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=54078
Bug ID: 54078
Summary: ntdll:pipe - test_blocking() sometimes fails in Wine
when the pipe is not signaled
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:pipe - test_blocking() sometimes fails in Wine when the pipe is not
signaled:
pipe.c:1769: Test marked todo: client is not signaled
pipe.c:1751: Test failed: pipe is not signaled
pipe.c:1769: Test marked todo: client is not signaled
pipe.c:1770: Test failed: pipe is not signaled
See https://test.winehq.org/data/patterns.html#ntdll:pipe
Here is this failure's nightly WineTest run history:
* There was no failure in June and July.
* The first known failure happened on 2022-08-13, the next on 2022-08-18.
* The third failure happened on 2022-09-23.
* The fourth on 2022-11-04 which was followed by 9 more in November.
So it's likely something changed in early August-ish that introduced this
failure. But there has been a further change in November that makes it more
frequent (maybe the latter is because the TestBot now runs two VMs at a time so
the host is more busy, though that started a bit earlier, on 2022-10-25).
This failure also happens in the GitLab CI.
--
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=53974
Bug ID: 53974
Summary: d3drm:d3drm sometimes crashes after failing to create
the IDirect3DRMDevice* interface in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3drm:d3drm sometimes crashes after failing to create the IDirect3DRMDevice*
interface in Wine:
d3drm.c:4600: Test failed: Cannot create IDirect3DRMDevice interface, hr
0x8007000e.
d3drm.c:4602: Test failed: expected ref2 > ref1, got ref1 = 1 , ref2 = 1.
d3drm.c:4604: Test failed: Expected surface_ref2 > surface_ref1, got
surface_ref1 = 1, surface_ref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0040e52b).
[...useless backtrace...]
d3drm.c:4776: Test failed: Cannot create IDirect3DRMDevice2 interface, hr
0x8007000e.
d3drm.c:4778: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1.
d3drm.c:4782: Test failed: Expected surface_ref2 > surface_ref1, got
surface_ref1 = 1, surface_ref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x004106c1).
[...useless backtrace...]
d3drm.c:4407: Test failed: Cannot create IDirect3DRMDevice3 interface, hr
0x8007000e.
d3drm.c:4409: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1.
d3drm.c:4413: Test failed: expected cref2 > cref1, got cref1 = 1 , cref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0041290a).
[...useless backtrace...]
See https://test.winehq.org/data/patterns.html#d3drm:d3drm
The two "expected..." failures are not always present. This has been seen on
debian11, debiant but also fgtb-debian11 and gitlab-debian. So it's not
specific to dual-screen configurations nor to QEmu's QXL driver. But it seems
to only happen on "virtual GPUs" (gitlab-debian uses Xorg's dummy driver).
--
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=53528
Bug ID: 53528
Summary: ntdll:info - test_query_kerndebug() fails on Windows 8
to 10 1709
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:info - test_query_kerndebug() fails on Windows 8 to 10 1709:
info.c:1097: Test failed: Expected STATUS_SUCCESS, got 80000002
info.c:1102: Test failed: Expected STATUS_SUCCESS, got 80000002
https://test.winehq.org/data/patterns.html#ntdll:info
The failures started on 2022-07-26.
--
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=53182
Bug ID: 53182
Summary: shell32:shelllink - A save(NULL, TRUE) fails randomly
in test_load_save() on Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
A save(NULL, TRUE) fails randomly in test_load_save() on Wine:
shelllink.c:775: Test failed: save(NULL, TRUE) failed (0x80070020)
https://test.winehq.org/data/patterns.html#shell32:shelllink
This is probably the same issue as bug 28290, the only difference being that it
does not happen at a point that leads to a NULL pointer access.
--
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=52948
Bug ID: 52948
Summary: gdi32:font - test_EnumFonts() fails on Arial Bold on
Windows in Russian
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:font - test_EnumFonts() fails on Arial Bold on Windows in Russian:
font.c:5409: Test failed: font Arial Bold is not enumerated
font.c:5412: Test failed: expected FW_BOLD got 400
font.c:5419: Test failed: font Arial Bold Italic is not enumerated
font.c:5421: Test failed: expected Arial got Arial Bold
font.c:5422: Test failed: expected FW_BOLD got 400
https://test.winehq.org/data/patterns.html#gdi32:font
Maybe this can happen in other locales, but among those that are tested this
only happens with the Russian one (w10pro64-ru).
--
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=51848
Bug ID: 51848
Summary: Performance Regression in Secondhand Lands
Product: Wine
Version: 6.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: escomk3(a)hotmail.com
Distribution: ---
After 4261369e5d8 [1], FPS will be near zero, and the game area will be black,
with the actual should-be content sometimes appearing and disappearing.
Standard output with default'ish debug channels doesn't show any difference
with a build prior to this commit.
1.
https://source.winehq.org/git/wine.git/commit/4261369e5d8f1d71e8d2074747515…
--
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=54649
Bug ID: 54649
Summary: windows.perception.stub:perception - Windows 10 1607
does not have ISpatialSurfaceObserverStatics2
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
windows.perception.stub:perception - Windows 10 1607 does not have
ISpatialSurfaceObserverStatics2:
perception.c:76: Test failed: got hr 0x80004002.
perception.c:76: this is the last test seen before the exception
088c:perception: unhandled exception c0000005 at 00401483
See
https://test.winehq.org/data/patterns.html#windows.perception.stub:percepti…
Where 0x80004002 == E_NOINTERFACE
This test was introduced in the commit below:
commit 006bc33c57c96bd733147c4088d36bfc14da907e
Author: Mohamad Al-Jaf <mohamadaljaf(a)gmail.com>
AuthorDate: Thu Feb 23 03:50:15 2023 -0500
windows.perception.stub: Add ISpatialSurfaceObserverStatics2 stub
interface.
--
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=54539
Bug ID: 54539
Summary: Starcraft Remastered Game Initialization Failed
Product: Wine
Version: 8.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: uberdude555(a)yahoo.com
Distribution: ---
Created attachment 74080
--> https://bugs.winehq.org/attachment.cgi?id=74080
stdout
I updated from wine 7.0-rc3 to 8.2, and when I try to start StarCraft now I see
an error dialog box with text "Game Initialization Failed: T".
I tried running the exe directly (rather than through the Battle.net client)
and saw the same error with only the four lines attached written to the
terminal.
The AppDB page shows at least three other users experiencing the same issue
from version 8.1 and possibly earlier:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=35171.
--
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=54509
Bug ID: 54509
Summary: psapi:psapi_main - The 64-bit
test_EnumProcessModules() gets unexpected third module
on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 64-bit test_EnumProcessModules() gets unexpected third
module on Windows 11:
psapi_main.c:185: Test failed: third DLL in wow64 should be one of wow*.dll
(kernel32.dll)
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
This test and failure was introduced by the commit below:
commit 00bf7293af13f3766c6c839f0125785ac9084de8
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Tue Feb 14 11:07:01 2023 +0100
psapi: Add more tests for EnumProcessModules().
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
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=54003
Bug ID: 54003
Summary: vbscript:run sometimes fails on Windows UTF-8 locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
vbscript:run sometimes fails on UTF-8 locales:
=== w10pro64_en_AE_u8 (64 bit report) ===
vbscript:
run.c:1206: Test failed: api.vbs: L"Err.number = 0"
run.c:1206: Test failed: api.vbs: L"Err.description = "
run.c:1206: Test failed: api.vbs: L"Err.number = 0"
See https://gitlab.winehq.org/wine/wine/-/merge_requests/1534
Strangely enough so far this has not happened in the nightly WineTest runs but
it did happen in another unrelated merge request (MR!1561).
According to Nikolay (probably s/testChrError/testCStrError/):
> This is happening on utf-8 locale, in testChrError().
> Needs to be fixed, but unrelated to this MR.
--
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=53172
Bug ID: 53172
Summary: advapi32:registry - test_enum_value() has a pair of
rare failures in UTF-8 system locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8
system locales:
registry.c:558: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of
'foobar' or x's, data_count=21
registry.c:576: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of
'foobar' or x's, data_count=21
https://test.winehq.org/data/patterns.html#advapi32:registry
The line 558 and 576 failures happen about with the same frequency (~13% each)
but independently from each other so that most times there is at most one in
the report.
And they only happen in the TestBot's two UTF-8 test configurations:
w10pro64-en-AE-u8 and w10pro64-hi-u8.
--
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=54657
Bug ID: 54657
Summary: kernel32:loader - test_import_resolution() gets bad
tls data on Windows 7
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:loader - test_import_resolution() gets bad tls data on Windows 7:
loader.c:2324: Test failed: wrong tls data 'hello world' at 0000000000320590
See https://test.winehq.org/data/patterns.html#kernel32:loader
--
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=54531
Bug ID: 54531
Summary: jsproxy:jsproxy crashes on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
jsproxy:jsproxy crashes on Windows 11:
jsproxy.c:52: Test failed: got 3735928559
jsproxy.c:56: Test failed: got 3735928559
jsproxy.c:59: Test failed: got 3735928559
jsproxy.c:60: this is the last test seen before the exception
054c:jsproxy: unhandled exception c0000005 at 004013FA
See https://test.winehq.org/data/patterns.html#jsproxy:jsproxy
Where 3735928559 == 0xdeadbeef
So InternetGetProxyInfo() fails but does not set LastError. Furthermore the
proxy pointer is not initialized either so the test crashes when trying to free
it.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54504
Bug ID: 54504
Summary: psapi:psapi_main - The 32-bit
test_EnumProcessModules() gets a partial copy error on
Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 32-bit test_EnumProcessModules() gets a partial copy
error on Windows 11:
psapi_main.c:133: Test failed: got 0, error 299
psapi_main.c:134: Test failed: expected non-NULL module
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
Where 299 == ERROR_PARTIAL_COPY
This failure is specific to the 32-bit tests running on Windows 11, that is the
64-bit test has other (possibly related) failures, and Windows 10 and lower
don't have failures.
Also this failure has been present ever since the Windows 11 VM was added.
--
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=54019
Bug ID: 54019
Summary: The 64-bit ntdll:wow64 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
The 64-bit ntdll:wow64 fails on Windows 11. There are two failure modes:
wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 /
00000013640C5000
wow64.c:273: Test failed: wrong len 0
wow64.c:290: Test failed: wrong len 0
wow64.c:312: Test failed: wrong len 0
wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 75cec0-75d884
wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210
wow64.c:321: Test failed: wrong CommandLine ptr 0 / 75cec0-75d884
wow64.c:321: Test failed: wrong CommandLinelen 0 / 66
wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 75cec0-75d884
wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210
wow64.c:323: Test failed: wrong Desktop ptr 0 / 75cec0-75d884
wow64.c:323: Test failed: wrong Desktoplen 0 / 30
wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 75cec0-75d884
wow64.c:326: Test failed: wrong size 0 / 3222
wow64.c:338: Test failed: wrong len 0
wow64.c:339: Test failed: BeingDebugged is 0
or with 2 extra failures and different values:
wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 /
000000A7ECDDA000
wow64.c:273: Test failed: wrong len 0
wow64.c:290: Test failed: wrong len 0
wow64.c:291: Test failed: BeingDebugged is 117
wow64.c:309: Test failed: wrong ptr32 0000000000000000 / 00000298B3F80000
wow64.c:312: Test failed: wrong len 0
wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 0-9c4
wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210
wow64.c:321: Test failed: wrong CommandLine ptr 0 / 0-9c4
wow64.c:321: Test failed: wrong CommandLinelen 0 / 66
wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 0-9c4
wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210
wow64.c:323: Test failed: wrong Desktop ptr 0 / 0-9c4
wow64.c:323: Test failed: wrong Desktoplen 0 / 30
wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 0-9c4
wow64.c:326: Test failed: wrong size 0 / 3112
wow64.c:338: Test failed: wrong len 0
wow64.c:339: Test failed: BeingDebugged is 117
See https://test.winehq.org/data/patterns.html#ntdll:wow64
The values are pretty stable from one run to the next but do change from time
to time (causing false positives). Note also that the 32-bit version fails on
Windows 11 too.
--
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=52895
Bug ID: 52895
Summary: advapi32:service - EnumServicesStatusA() does not
support UTF-8 on Windows?
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:service fails on Windows with a UTF-8 codepage:
service.c:1283: Test failed: Expected success, got error 8
service.c:1285: Test failed: Expected some returned services
service.c:1312: Test failed: Expected the needed buffer size for this one
service
service.c:1313: Test failed: Expected fewer services to be returned
service.c:1314: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1326: Test failed: Expected the needed buffer size for this one
service
service.c:1327: Test failed: Expected fewer services to be returned
service.c:1328: Test failed: Expected a resume handle
service.c:1329: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1340: Test failed: Expected success, got error 8
service.c:1342: Test failed: Expected 559038737 services to be returned
service.c:1610: Test failed: Expected success, got error 8
service.c:1627: Test failed: Expected the needed buffer size
service.c:1628: Test failed: Expected fewer services to be returned
service.c:1629: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1641: Test failed: Expected the needed buffer size
service.c:1642: Test failed: Expected fewer services to be returned
service.c:1643: Test failed: Expected a resume handle
service.c:1644: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1655: Test failed: Expected success, got error 8
service.c:1657: Test failed: Expected 559038737 services to be returned
service.c:1702: Test failed: Expected success 8
https://test.winehq.org/data/patterns.html#advapi32:service
The first failure is an ERROR_NOT_ENOUGH_MEMORY in this call:
services = HeapAlloc(GetProcessHeap(), 0, needed);
bufsize = needed;
needed = 0xdeadbeef;
returned = 0xdeadbeef;
SetLastError(0xdeadbeef);
ret = EnumServicesStatusA(scm_handle, SERVICE_WIN32, SERVICE_STATE_ALL,
services, bufsize, &needed, &returned, NULL);
Where needed was calculated from a previous call (30890 in my case). So the
buffer should be big enough but EnumServicesStatusA() fails anyway. I tried
increasing the buffer size to the max 256KB but EnumServicesStatusA() still
complains about insufficient memory which does not make sense.
Later, when given a resume handle, the tests return RPC_X_BAD_STUB_DATA (1783)
instead of ERROR_MORE_DATA (234).
So this looks like the underlying RPC code that accesses the service control
manager is buggy and does not support UTF-8. So win_skip() the whole thing on
the first failure? Move the resume test with the RPC_X_BAD_STUB_DATA first and
skip if that fails?
--
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=53461
Bug ID: 53461
Summary: advapi32:service - test_EventLog() fails on Windows 10
2004 and 2009
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:service - test_EventLog() fails on Windows 10 2004 and 2009:
service.c:2751: Test failed: got 0x1 --> SERVICE_STOPPED
service.c:2753: Test failed: got 0
service.c:2757: Test failed: got 0x42b --> ERROR_PROCESS_ABORTED
service.c:2761: Test failed: got 0
https://test.winehq.org/data/patterns.html#advapi32:service
The failures appear to be happening because the EventLog service is stopped
following some sort of error (crash?).
These failures are systematic when running WineTest.exe but don't happen when
running advapi32:service on its own. So it seems likely that some other test is
causing EventLog to crash.
--
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=53460
Bug ID: 53460
Summary: advapi32:service regularly fails on Windows when
services stop / start
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:service regularly fails on Windows when services stop / start.
Because this may happen at any time the failures can take many forms:
service.c:1729: Test failed: Expected a process id for this running service
(sppsvc)
service.c:1746: Test failed: Active services mismatch 4294967295
service.c:1747: Test failed: Inactive services mismatch 1
or
service.c:1729: Test failed: Expected a process id for this running service
(SgrmBroker)
...
or
service.c:1746: Test failed: Active services mismatch 1
service.c:1747: Test failed: Inactive services mismatch 4294967295
or
service.c:1342: Test failed: Expected 114 services to be returned
service.c:1612: Test failed: Expected the same number of service from this
function
or
service.c:1729: Test failed: Expected a process id for this running service
(edgeupdate)
or
service.c:1729: Test failed: Expected a process id for this running service
(MapsBroker)
or
service.c:1729: Test failed: Expected a process id for this running service
(W32Time)
or
service.c:1729: Test failed: Expected a process id for this running service
(BITS)
or
service.c:1729: Test failed: Expected a process id for this running service
(DoSvc)
https://test.winehq.org/data/patterns.html#advapi32:service
The service names give a hint as to what happened:
* An Edge update got triggered: edgeupdate, probably BITS too.
* A time synchronization happened: W32Time.
* Some application caused the on-demand "Downloaded Maps Broker" service to
start: MapsBroker.
* Something caused Windows Update Delivery Optimization to start (despite it
being disabled in the settings): DoSvc.
* The 'System Guard Runtime Monitor Broker Service' got started for some
reason: SgrmBroker.
* The 'Microsoft Software Protection Platform Service' which is involved in the
license checking got started: sppsvc.
So I don't think it would be reasonable to disable all these services. We would
still likely have a steady trickle of other services causing trouble, and we'd
have the problem again when a new Windows version introduces another service.
Instead advapi32:service should be more resilient. That may mean accepting
small variations in the number of running services, or checking that a service
is still running before complaining that it does not have a pid.
--
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=54694
Bug ID: 54694
Summary: Marvel's Spider-Man Remastered requires Windows 10
version 1909, build 18363 (or newer)
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
As the title says.
8.3-258-g81976e5c3f4
--
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=53562
Bug ID: 53562
Summary: SWAT 4: mouse wrapping issues
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matheus.venturini(a)acad.ufsm.br
Distribution: ---
When beginning a mission in SWAT 4, the mouse will (most often) not allow you
to fully rotate your vision in 360 degrees. This can be "fixed" by simply
right-clicking, which will cause it to start acting normal.
I've had times where this did not occur when starting a mission so I can't say
it's a "can always reproduce" issue, and sometimes, very sporadically, the
mouse starts acting faulty again during gameplay for seemingly no reason.
Doing a search, I found an entry for the same issue in Codeweavers' forum:
https://www.codeweavers.com/compatibility/crossover/forum/swat-4?msg=108881
The fix suggested in that page, to set "MouseWarpOverride" to "force_edge" in
the registry, was not necessary since doing a right-click will make it go back
to normal.
Apparently some other games are also affected (GTA Vice City and Bioshock
according to the discussion in https://forum.winehq.org/viewtopic.php?t=29663).
I will try to reproduce the issue and attach the log 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=54419
Bug ID: 54419
Summary: RICHED20: Word Break Procedure of Rich TextBox should
consider punctuation
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: katayama.hirofumi.mz(a)gmail.com
Distribution: ---
Created attachment 73977
--> https://bugs.winehq.org/attachment.cgi?id=73977
the patch to the word break procedure of rich textbox
The default word break procedure of rich textbox didn't consider punctuation.
This patch will add punctuation check to the default word break procedure.
--
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=33008
Bug #: 33008
Summary: UDP listening on specific IP address does not work
properly
Product: Wine
Version: 1.5.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: decimusmaximus(a)seznam.cz
Classification: Unclassified
Wine updated from 1.5.6 to 1.5.24.
My app uses UDP listening on specific address (not 0.0.0.0). It is running on
machine with NAT, there are two interfaces with IP A.A.A.A (public) and IP
B.B.B.B (private) My app is set to listen only on one IP address, IP A.A.A.A
It works properly on Wine 1.5.6. Traffic from subnet B.B.B.B is NATed to
A.A.A.A interface and application running in wine receives it correctly.
After update to 1.5.24 it does not work anymore.
Application does not receive data from private subnet B.B.B.B, however it works
properly for traffic incoming on A.A.A.A interface.
Please see attached schema.
results of "netstat --listening"
with Wine 1.5.6 it is listening on A.A.A.A address correctly.
with Wine 1.5.24 it is listening on 0.0.0.0 (obviously incorrect, socket
binding is set to A.A.A.A address in application and although it is saying
0.0.0.0 app does not receive any data from B.B.B.B network)
This application has to be listening only on one interface and do not mix
public and private addresses. In this case it is not accessible for clients in
private network, so it is critical bug.
Main strange thing is, that it is listening on all addresses 0.0.0.0 although
socket binding in application is set to address A.A.A.A
--
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=54671
Bug ID: 54671
Summary: netcap.exe crashes on unimplemented function
npptools.dll.CreateBlob
Product: Wine
Version: 8.3
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 74187
--> https://bugs.winehq.org/attachment.cgi?id=74187
Console output
netcap.exe is the "Microsoft Network Monitor capture utility". It was included
in the Windows XP Service Pack 2 Support Tools.
Steps to reproduce:
1. Create a 32-bit Wine bottle and set the Windows version to XP.
2. Run `wine WindowsXP-KB838079-SupportTools-ENU.exe`.
3. Run `wine 'C:\Program Files\Support Tools\netcap.exe'`.
The program will not start.
$ sha256sum WindowsXP-KB838079-SupportTools-ENU.exe
7927e87af616d2fb8d4ead0db0103eb845a4e6651b20a5bffea9eebc3035c24d
--
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=22675
Summary: TechSmith Camtasia player fails to open.
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mattj10973(a)hotmail.co.uk
Created an attachment (id=27925)
--> (http://bugs.winehq.org/attachment.cgi?id=27925)
The program (MATHSWATCH), it's embedded player, the Tech Smith Camtasia player
(Clip 102 etc.), and the error message.
I recently purchased a revision CD for my GCSE Mathematics course, and it
states the CD is compatible with Windows 98SE/Me/2000/XP/Vista. I try to run it
through Lucid Lynx, but I get an error message. I'm new to Linux and open
source software in general, and have pretty much zilch coding or advanced
knowledge of my new system, so sorry in advance if I've done anything
incorrectly, or failed to understand some of the site's instructions. Error
message attached, thanks :)
--
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=54635
Bug ID: 54635
Summary: libwine backward compatibility
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winecrt0
Assignee: wine-bugs(a)winehq.org
Reporter: a.heider(a)gmail.com
Distribution: ---
v8.3 finally removed libwine.
Older winegcc builds automatically link against it (just
__wine_dll_register(a)WINE_1.0 in out case).
Newer winegcc builds don't link against it anymore, it looks like since
f6a363bc4108f3d45b7a5bac706d10579f4d2772 "winecrt0: Get rid of constructor
support." v5.7.
We build downloadable releases and would like to keep maximum binary
compatibility.
Building with >=v5.7 would likely avoid the issue, but I guess binaries won't
work on older WINE versions then.
For the record: Ubuntu 18.04 LTS is about to go unsupported, 20.04 LTS ships
v5.0. Our current CI setup uses 20.04, so v5.0, to build releases.
Is there something we can do to make built binaries work on >=v5.0?
Any suggestions how to archive that? Something on our end? Or maybe WINE can
get a compatibility addition to skip the
libwine.so.1/__wine_dll_register(a)WINE_1.0 symbol or something?
Thanks!
Andre
--
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=37056
Bug ID: 37056
Summary: Rapture3D requires native dsound.dll in order to
change sound layout.
Product: Wine
Version: 1.7.23
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dsound
Assignee: wine-bugs(a)winehq.org
Reporter: El_Diablo2(a)gmx.de
Created attachment 49248
--> http://bugs.winehq.org/attachment.cgi?id=49248
Error message with builtin dsound.dll
With builtin dsound UserLayout.exe complains it cannot change the soundcard
configuration.
No interessting (default channels) debug 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=54686
Bug ID: 54686
Summary: LibvirtTool sometimes fails to update the time
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
When reverting to a live snapshot it is necessary to update the VM's time so
certificate checks and more work as expected. This is handled by LibvirtTool.pl
via using the SetTime TestAgent RPC.
However there are some cases where this fails as is evidenced by job 130592:
w10pro64v2004 LocalTime: 2023-03-14 2 10:47:10.744
w10pro64 LocalTime: 2022-12-11 0 14:18:16.343
w10pro64_fr LocalTime: 2023-03-14 2 10:46:42.143
So the time did not get updated on w10pro64 while it did get updated on all of
that job's 4 other VMs. Furthermore there is evidence that during that day's
nightly WineTest runs it is w10pro64v2004 that did not get a time update (or
the time reverted back?).
Failure to update the time can cause test failures so it needs to be reliable.
--
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=54685
Bug ID: 54685
Summary: The localized VMs don't have a localized timezone
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The base VM configurations are all in the Minnesota timezone (CST / CDT).
But the localized ones should be in the timezone corresponding to the country.
For instance the French test configuration should be in the CET / CEST
timezone.
But SetWinLocale does not support changing the timezone.
--
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=54659
Bug ID: 54659
Summary: d3d8:device & d3d9:device sometimes get floating point
underflow in GenerateRampFromGamma() in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d8:device & d3d9:device sometimes get an floating point underflow exception
in GenerateRampFromGamma() in Wine:
d3d8:device start dlls/d3d8/tests/device.c
Unhandled exception: floating point underflow in 32-bit code (0x7e91438f).
[...]
Backtrace:
=>0 0x7e91438f in libm.so.6 (+0x2538f) (0x0069ef68)
1 0x7e922d3b in libm.so.6 (+0x33d3b) (0x0069ef68)
2 0x7e55c181 GenerateRampFromGamma+0x51(ramp=00197C4C, gamma=0.000300)
[Z:\home\winetest\tools\testbot\var\wine\dlls\winex11.drv\xvidmode.c:336] in
winex11.so (0x0069ef68)
3 0x7e55c9b2 X11DRV_XF86VM_GetGammaRamp+0x60(ramp=<internal error>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\winex11.drv\xvidmode.c:519] in
winex11.so (0x0069ef68)
4 0x7e55c9b2 X11DRV_GetDeviceGammaRamp+0x82(dev=<couldn't compute location>,
ramp=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\winex11.drv\xvidmode.c:569] in
winex11.so (0x0069ef68)
5 0x7ea32408 NtGdiGetDeviceGammaRamp+0x88(hdc=<couldn't compute location>,
ptr=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\win32u\dc.c:1247] in win32u.so
(0x0069efb8)
6 0x64a8d74c NtGdiGetDeviceGammaRamp+0x2c(hdc=<couldn't compute location>,
ptr=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\win32u\wrappers.c:280] in win32u
(0x0069efe8)
7 0x6ccf9d3d wined3d_output_get_gamma_ramp+0x4d(output=00140E10,
ramp=00197C4C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\directx.c:1741] in
wined3d (0x0069f028)
8 0x6cd5fcb0 wined3d_swapchain_get_gamma_ramp+0x30(swapchain=00197C30,
ramp=00197C4C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\swapchain.c:385] in
wined3d (0x0069f058)
9 0x6cd61190 wined3d_swapchain_init+0x3c0(swapchain=<register EBX not
accessible in this frame>, device=<register EDI not accessible in this frame>,
desc=<internal error>, state_parent=00140D5C, parent=00140D50,
parent_ops=67CDE7D4, swapchain_ops=6CE6933C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\swapchain.c:1633] in
wined3d (0x0069f168)
10 0x6cc8d9f3 adapter_gl_create_swapchain+0x73(device=0017B3E8,
desc=0069F2BC, state_parent=00140D5C, parent=00140D50, parent_ops=67CDE7D4,
swapchain=0069F1FC)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\adapter_gl.c:4701] in
wined3d (0x0069f1b8)
11 0x6cd5fdd1 wined3d_swapchain_create+0x41(device=0017B3E8, desc=0069F2BC,
state_parent=00140D5C, parent=00140D50, parent_ops=67CDE7D4,
swapchain=00140D58)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\swapchain.c:1724] in
wined3d (0x0069f208)
12 0x67ccfe84 swapchain_init+0x48(swap_interval=<internal error>,
desc=<internal error>, device=<internal error>, swapchain=<internal error>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\swapchain.c:180] in d3d8
(0x0069f248)
13 0x67ccfe84 d3d8_swapchain_create+0x84(device=001468F0, desc=0069F2BC,
swap_interval=0xffffffff, swapchain=0069F290)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\swapchain.c:199] in d3d8
(0x0069f248)
14 0x67ccc467 device_init+0x217(device=001468F0, parent=00140A90,
wined3d=00140AB0, adapter=0, device_type=D3DDEVTYPE_HAL, focus_window=0003004A,
flags=0x42, parameters=0069F53C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\device.c:3744] in d3d8
(0x0069f478)
15 0x67ccd649 d3d8_CreateDevice+0xa9(iface=<couldn't compute location>,
adapter=<couldn't compute location>, device_type=<couldn't compute location>,
focus_window=<couldn't compute location>, flags=<couldn't compute location>,
parameters=<couldn't compute location>, device=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\directx.c:438] in d3d8
(0x0069f4e8)
16 0x004010ce in d3d8_test (+0x10ce) (0x0069f588)
...
This does not happen in the nightly Wine test runs but impacted at least two
merge requests:
* MR2072, repeatedly
* MR2217, repeatedly
There are three immediate questions:
* Where does the 0.000300 gamma come from?
I don't think such a value makes sense so I suspect it's caused by a bug
somewhere.
* Should xvidmode.c's GenerateRampFromGamma() crash in case of underflow (or
overflow for that matter)?
If not, ComputeGammaFromRamp() should probably be fixed too. Which other
functions have the same issue? (not just in xvidmode.c)
* By default underflows don't cause exceptions. So which piece of code in
d3d8:device does a _control87(0, _EM_UNDERFLOW) ?
Then, why does this failure not happen more often?
The debian11 VM ran the tests multiple times in a row to test various locales:
en -> success
ar:MA -> success
de -> success
fr -> underflow
he:IL -> underflow
hi:IN -> underflow
ja:JP -> underflow
zh:CN -> underflow
While the wineprefix is recreated for each test, all the tests run on the same
X server session. So my theory is that one of the tests in the first three runs
progressively degraded the gamma at the X level, such that all the tests that
followed got a bad gamma from the X server and crashed. Furthermore note that
the first plain 32-bit run ran the full Wine test suite. That may have been a
factor too.
MR2217 caused the following tests to run so the guilty party should be among
them:
d3d8:device d3d9:device ddraw:ddraw1 ddraw:ddraw2 ddraw:ddraw4 ddraw:ddraw7
That explains why this failure does not happen in the nightly Wine test runs:
each is done after restoring the VM to a clean state. Similarly, other merge
requests may run fewer tests so that the gamma does not get degraded that much.
That leaves a mystery though: I don't get this issue on my desktop (fg-deb64)
despite running the tests every night and not ever restarting the X server
(thankfully!). Maybe this gamma issue is caused by a bug that only happens with
the VM environment (likely QXL GPU or dual screen configuration, such that it
does not happen on single-screen Intel GPUs)?
--
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=53553
Bug ID: 53553
Summary: F.E.A.R. won't work with DSOAL surround sound
restoration DLL replacement
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dsound
Assignee: wine-bugs(a)winehq.org
Reporter: mr.matt.eastwood(a)gmx.de
Distribution: ---
Steps to Reproduce:
1. Install F.E.A.R. (e.g., "Fear Platinum" from GOG)
2. Get DSOAL from https://github.com/kcat/dsoal and compile dsound.dll
3. Get latest OpenAL-Soft bin from https://openal-soft.org/
4. Unzip soft_oal.dll from its bin\Win32 directory
5. Rename that file to dsoal-aldrv.dll
6. Place both dsoal-aldrv.dll and DSOAL's dsound.dll in same directory as
FEAR.exe
7. Run game
8. Enter sound menu
Expected Results:
When running F.E.A.R. with the DLL replacement DSOAL for surround sound
restoration, the advanced sound options "Enable HW mixing", "Enable EAX 2.0"
and "Enable EAX Advanced HD" should be available in the sound menu and surround
sound including EAX effects should work.
Current Results:
The sound options remain greyed-out.
Observations:
F.E.A.R. won't load dsound.dll from anywhere but syswow64. If one places the
DSOAL dsound.dll there (replacing Wine's own), and then sets dsound.dll to
"native" e.g. through winecfg, everything works. Screenshot:
If one sets dsound.dll to "native" e.g. through winecfg and then loads the game
without replacing Wine's dsound.dll in syswow64 (but with the DSOAL files in
the F.E.A.R. folder): "Failed to initialize sound driver 'SndDrv.dll' on
startup. Screenshot: https://paste.pics/I4DO0. No sound during game or menus,
only during intro movie. Available sound options: https://paste.pics/I4DOD
--
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=49915
Bug ID: 49915
Summary: can not register COM server
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ysong2180(a)yahoo.com
Distribution: ---
Created attachment 68286
--> https://bugs.winehq.org/attachment.cgi?id=68286
two log files. one is the winecfg log. The other one is the application log
I tried to install an windows application on Ubuntu 20.04. The installer can
run and install files. But it fails at the end when it tries to register COM
servers. It is a win32 application. I used winecfg to create a win32
wineprefix and used the win32 wineprefix to start the installer.
--
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=54677
Bug ID: 54677
Summary: Wine cannot find tools in tool dir when cross
compiling
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: ale.schenberg(a)yandex.com
Distribution: ---
Created attachment 74193
--> https://bugs.winehq.org/attachment.cgi?id=74193
config.log
Hello. When trying to cross build wine, configure's execution breaks due to it
to not find wine tools in the tools dir.
My building command:
LDFLAGS=-Wl,--dynamic-link=/usr/lib32/ld-2.17.so ./configure
--host=i686-gnu-linux --with-wine-tools=tools/
I attached config.log, although it appears to contain no useful information.
The bug applies to wine 8.3 and any other wine version that I tested (such as
1.9)
I think its worthy to mention that cross build it is more a necessity imposed
by the configure script than my wish. As I am forced to pass
"LDFLAGS=-Wl,--dynamic-link=/usr/lib32/ld-2.17.so" to configure (if not, the
building won't be able to run any auxiliary 32bit components, such as makedep,
unless I statically build them), configure demands the use of host, and then of
--with-wine-tools
--
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=47000
Bug ID: 47000
Summary: Make WineHQ available as flatpak in Flathub
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: yousifjkadom(a)yahoo.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
Hi.
I would like, here, to suggest to make WineHQ available as flatpak in Flathub.
This will be very useful since flatpak is secure & sandboxed, so user will be a
way from infect heir/his PC by a virus or spywar. If flatpak Wine run a virus,
then it will be like if Wine sandboxed by firejail run such virus.
Moreover, flatpak can minimize time & efforts in packaging because it is a
generic package working in many Linux distro regardless OS version.
Also, Wine contain huge number of 32 bit packages that are, mostly, not needed
by any other 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=54674
Bug ID: 54674
Summary: Add Flatpak to Download page
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: peter.eszlari(a)gmail.com
Distribution: ---
Since February 2022 Wine has been available as a Flatpak.
To try it:
0. ($ apt install flatpak)
1. $ flatpak remote-add flathub https://flathub.org/repo/flathub.flatpakrepo
2. $ flatpak install org.winehq.Wine
3. $ flatpak run org.winehq.Wine prog.exe
build manifest source: https://github.com/flathub/org.winehq.Wine
I think it would make sense to add this to list of binary packages on:
https://wiki.winehq.org/Download
(Note: Wine cannot be found on the Flathub web interface at
https://flathub.org, because only GUI apps are listed there, not CLI apps.)
--
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=37640
Bug ID: 37640
Summary: Opening Windroy and it crashes.
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fholiveira1(a)hotmail.com
Distribution: ---
Created attachment 50094
--> https://bugs.winehq.org/attachment.cgi?id=50094
Extract from Wine report of bug.
I was trying to open Windroy and it crashes. The system open a bug report,
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=54508
Bug ID: 54508
Summary: psapi:psapi_main - The 64-bit
test_EnumProcessModulesEx() gets unexpected snapshot
counts on Windows 7 and 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 64-bit test_EnumProcessModulesEx() gets unexpected
snapshot counts on Windows 7 and 11:
w7pro64:
psapi_main.c:483: Test failed: pcs-6432: Wrong count 23 in C:\Windows\SysWOW64
psapi_main.c:488: Test failed: pcs-6432: Wrong count 2 in C:\Windows\system32
w11pro64:
psapi_main.c:488: Test failed: pcs-6432: Wrong count 0 in C:\Windows\system32
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
These failures don't happen on Windows 8 to Windows 10!
These tests and failures were introduced in the following commit:
commit e38455a2181ab5ce0bf842f2c9a638b3ee9b538c
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Tue Feb 14 11:06:57 2023 +0100
psapi/tests: Test directory of enumerated loaded modules.
Showing that Wine incorrectly reports, for a Wow64 process, the system
DLLs from within the wow64 directory while they should be from system32.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
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=54662
Bug ID: 54662
Summary: The winscard tests are not run on the TestBot Wine VMs
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The winscard tests are not run on the TestBot Wine VMs:
winscard missing
See the newtb-debian11-*, newtb-debian11b-* and newtb-debiant-* Linux results
on:
http://winetest.dolphin/data/tests/winscard:winscard.html
The reason is that the VMs are missing the libpcsclite libraries and maybe
other infrastructure needed to actually run the tests: if one just installs the
libraries the tests immediately get an SCARD_E_NO_SERVICE error and bail out:
can't establish context, make sure pcscd is running
--
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=54658
Bug ID: 54658
Summary: gdi32:driver -
test_D3DKMTCheckVidPnExclusiveOwnership() sometimes
fails due to occlusion error on Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:driver - test_D3DKMTCheckVidPnExclusiveOwnership() sometimes fails due to
INVALID_VIDEO_PRESENT_SOURCE error on Windows 8:
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 0.
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 1.
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 2.
[... same for tests 3 -> 58 ...]
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 59.
driver.c:481: Test failed: Got unexpected return code 0xc01e0304.
driver.c:505: Test failed: Got unexpected return code 0xc01e0006.
driver.c:556: Test failed: Got unexpected return code 0xc01e0006 at test 0.
[... same for tests 1 -> 16 ...]
driver.c:523: Test failed: Got unexpected return code 0xc01e0304 at test 17.
[... more code 0xc01e0304 errors ...]
driver.c:754: Test failed: Got unexpected return code 0xc01e0304.
driver.c:766: Test failed: Got unexpected return code 0.
[... more code 0 errors ...]
driver.c:785: Test failed: Got unexpected return code 0.
driver.c:807: Test failed: Got unexpected return code 0xc01e0006.
See https://test.winehq.org/data/patterns.html#gdi32:driver
Where:
0xc01e0006 == STATUS_GRAPHICS_PRESENT_OCCLUDED
0xc01e0304 == STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE
The oldest known instance was on 2023-12-09 and there has been about one per
month since:
* 2022-12-09 on w864 64-bit
* 2023-02-06 on w864 64-bit
* 2023-03-09 on w864 64-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=54476
Bug ID: 54476
Summary: Sims 3 Crash at launch
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pardisetm(a)gmail.com
Distribution: ---
Created attachment 74028
--> https://bugs.winehq.org/attachment.cgi?id=74028
screenshot of error dialog (in french, translated in description)
When launching the sims 3, it crash and display an error:
"impossible to start the game"
"Initialization of service (0x0175d824) failed"
--
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=54654
Bug ID: 54654
Summary: urlmon:protocol - The "http protocol from urlmon" test
sometimes gets unexpected BSCF_FIRSTDATANOTIFICATION
on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:protocol - The "http protocol from urlmon" test sometimes gets
unexpected BSCF_FIRSTDATANOTIFICATION on Windows:
protocol.c:3557: Testing http protocol (not from urlmon)...
protocol.c:1122: Test failed: grcfBSCF = 00000001
protocol.c:3561: Testing http protocol (from urlmon)...
See https://test.winehq.org/data/patterns.html#urlmon:protocol
Where:
00000001 == BSCF_FIRSTDATANOTIFICATION
This happens a bit over once per month on average but with sometimes month-wide
gaps. This also impacts all Windows versions, from Windows 7 to Windows 11.
--
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=54081
Bug ID: 54081
Summary: urlmon:protocol - The "http protocol direct read test"
sometimes causes a timeout in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
urlmon:protocol - The "http protocol direct read" test sometimes causes a
timeout in Wine:
protocol.c:3576: Testing http protocol (direct read)...
protocol.c:1083: Test failed: unexpected call ReportData2
protocol.c:1085: Test failed: grfBSCF = 00000001
protocol.c:1093: Test failed: Read returned: 00000000, expected E_FALSE
protocol.c:1094: Test failed: read = 14096
protocol.c:693: Test failed: expected ReportData
protocol.c:3438: Test failed: wait timed out
protocol.c:3439: Test failed: expected Switch
protocol.c:348: Test failed: unexpected call OnResponse
protocol.c:839: Test failed: unexpected call ReportProgress_MIMETYPEAVAILABLE
protocol.c:1083: Test failed: unexpected call ReportData2
protocol.c:1085: Test failed: grfBSCF = 00000002
protocol.c:1093: Test failed: Read returned: 00000000, expected E_FALSE
protocol.c:1094: Test failed: read = 14096
protocol.c:693: Test failed: expected ReportData
urlmon:protocol:06f4 done (258) in 120s
See https://test.winehq.org/data/patterns.html#urlmon:protocol
This always happens in "Testing http protocol (direct read)...", never in the
https or "from urlmon" variants.
The first known instance happened on 2022-08-05 on debiant-wow32 (there was no
such failure in the previous 2 months) and the nightly WineTest runs have had
about one failure per month since.
--
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=54652
Bug ID: 54652
Summary: urlmon:url - The "http protocol direct read test"
sometimes get an unexpected ref count on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:url - The "http protocol direct read test" sometimes get an unexpected
ref count on Windows:
protocol.c:3576: Testing http protocol (direct read)...
protocol.c:3525: Test failed: ref=3
protocol.c:3580: Testing http protocol (redirected)...
See https://test.winehq.org/data/patterns.html#urlmon:protocol
With only 5 instances over the past 8 months this is pretty rare but may be
getting more frequent:
* 2022-08-08 on w8adm 32-bit
* 2022-08-11 on w8adm 32-bit
* 2023-01-09 on w10pro64-hi-u8 64-bit
* 2023-01-13 on w10pro64-ko 64-bit
* 2023-03-06 on w864 32-bit
Like many other refcount tests:
* Is this a race condition? Could it be some windows thread holding references
to the object?
* Is this test really needed?
--
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=54651
Bug ID: 54651
Summary: user32:input - test_rawinput() sometimes gets
unexpected (RIM|WM)_INPUT messages 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:input - test_rawinput() sometimes gets unexpected (RIM|WM)_INPUT
messages on Windows:
input.c:2921: Test failed: 6: unexpected WM_INPUT message
input.c:2924: Test failed: 6: unexpected RIM_INPUT message
See https://test.winehq.org/data/patterns.html#user32:input
This happened on w11pro64 back in October but that was with test 12 and I think
it stopped when I fixed disabling Windows update.
More recently it started happening on Windows 10:
* 2023-03-08 on w10pro64-ja 64-bit
* 2023-03-08 on w10pro64-zh-CN 64-bit
* 2023-03-06 on MR2334 w10pro64_ja & w10pro64_zh_CN
See also bug 53205 and bug 54437 where the test 15 is missing these messages.
--
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=54641
Bug ID: 54641
Summary: CheckPoint VPN installation gives "Windows update for
SHA-2 code signing support is not installed. See
kb3033929"
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: drpeidos(a)gmail.com
Distribution: ---
While trying to install Check Point Endpoint Security VPN using the command
'wine "CheckPoint82.40.msi"' I get the error 'Windows update for SHA-2 code
signing support is not installed. See kb3033929', in the terminal there is the
following log:
wine "CheckPoint82.40.msi"  ✔
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0108:err:winediag:gnutls_process_attach failed to load libgnutls, no support
for encryption
0108:err:winediag:process_attach failed to load libgnutls, no support for pfx
import/export
0108:fixme:file:NtLockFile I/O completion on lock not implemented yet
0108:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
0114:err:winediag:gnutls_process_attach failed to load libgnutls, no support
for encryption
0114:err:winediag:process_attach failed to load libgnutls, no support for pfx
import/export
008c:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub
008c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub
0108:fixme:imm:ImeSetActiveContext (00010056, 1): stub
0108:fixme:imm:ImmReleaseContext (0001006A, 00010056): stub
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping begin
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
0108:err:richedit:ReadStyleSheet skipping optional destination
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{00000001-0000-0104-ad23-7f548e9283ef}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{00000001-0000-0104-ad23-7f548e9283ef}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{00000001-0000-0104-ad23-7f548e9283ef}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{00000001-0000-0104-ad23-7f548e9283ef}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001b-0000-0104-b3f6-268013bd3b02}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001b-0000-0104-b3f6-268013bd3b02}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001b-0000-0104-b3f6-268013bd3b02}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001b-0000-0104-b3f6-268013bd3b02}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001c-0000-0104-b3a5-f876a75e4d58}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001c-0000-0104-b3a5-f876a75e4d58}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001c-0000-0104-b3a5-f876a75e4d58}
012c:err:ole:get_stub_manager_from_ipid not found for ipid
{0000001c-0000-0104-b3a5-f876a75e4d58}
01b8:fixme:msi:MsiGetLastErrorRecord
I tried installing Windows6.1-KB3033929-x86.msu, but Wine also gives an error.
--
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=54644
Bug ID: 54644
Summary: Ofice 2021 Pro Plus 32/64 bit: installer doesn't work
Product: Wine-staging
Version: 8.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: romulasry(a)protonmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I launched from
https://softcomputers.org/en/download/download-microsoft-office/download-mi…
Doesn't launch.
I can't get the log file though, could someone help?
--
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=54643
Bug ID: 54643
Summary: the toolbar icon of filedialog is too small when using
the 4k display
Product: Wine
Version: 6.0.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: 34810581(a)qq.com
Distribution: ---
Created attachment 74173
--> https://bugs.winehq.org/attachment.cgi?id=74173
toolbar icon too small
the toolbar icon of filedialog is too small when using the 4k display
--
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=54475
Bug ID: 54475
Summary: Hardwar UIM6.0 crashes in 8.0, doesn't in 6.0.3
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nickmarko(a)gmail.com
Distribution: ---
Created attachment 74024
--> https://bugs.winehq.org/attachment.cgi?id=74024
debug output of crash
Ran in Virtual Desktop mode to test version F2.0, which has no windowed mode
option and won't display full screen but does display in the virtual desktop.
F2.0 gets past the loading screen and the game doesn't crash.
I updated Wine from 6.0.3 (the version that is in the default Ubuntu repos) to
8.0 from the official WineHQ repos for Ubuntu Jammy and now UIM6.0 crashes when
the loading bar reaches 100%.
I downgraded to 6.0.3 and UIM6.0 no longer crashed. I updated back to 8.0 and
UIM6.0 crashes again.
Terminal output running F2.0: https://pastebin.com/mfLVj3Xd
Terminal output installing and running UIM6.0: https://pastebin.com/mDHSzMyM
--
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=54628
Bug ID: 54628
Summary: Opening files in Microsoft Word/Excel/Office 2010
results in opening an empty document
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kle(a)bluewin.ch
Distribution: ---
When I double-click a MS Office file then Word/Excel/Office 2010 starts up with
an empty document. So the page/sheet is blank and it looks that the file
doesn't contains any data.
However, there is no problem with the documents, they are fine. Instead it
looks that there is a problem in the way how the files are opened. When the
corresponding Word/Excel/Office 2010 file is opened out from the program then
everything is okay and it is displayed correctly.
So this problem only happens when the Office 2010 file is opened by a double
click.
Long story short, there exist a trivial workaround by disabling the hardware
acceleration in Office 2010. Microsoft was so kind to provide the solution for
that problem here:
https://learn.microsoft.com/en-us/office/troubleshoot/excel/excel-opens-bla…
In the end it looks that this problem can happen in some circumstances also on
Windows. ;-)
For the record, this problem is present also on older Wine 7.x releases. So
this is not a new regression and I am unsure if this ever worked before.
(However, it took a while until I have found the workaround.)
--
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=7585
Jeff Zaroyko <jeffz(a)jeffz.name> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #72 from Jeff Zaroyko <jeffz(a)jeffz.name> ---
Two reports that the issue is fixed. Resolving.
--
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=7585
mirh <mirh(a)protonmail.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mirh(a)protonmail.ch
--- Comment #71 from mirh <mirh(a)protonmail.ch> ---
Can be closed as per last comment.
--
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=4713
--- Comment #35 from temp82(a)luukku.com ---
still freezes wine 8.3.
--
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=54626
Bug ID: 54626
Summary: Saving files in Microsoft Word/Excel 2010 creates
useless shortcut files
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: kle(a)bluewin.ch
Distribution: ---
Here follows a new bug report regarding the problem observed in old bug report
15480.
It was told me that I should open a new bug report. ;-)
Okay, the issue regarding the creation of useless shortcut files is back in
Wine 8.0 (stable).
When I open a *.xlsx file at the desktop and save it (with the same name) to an
*.ods file then Excel 2010 will create two files. One is a *.lnk (which points
to the original xlsx) and the other is a shortcut regarding the ods file but
also with *.ods ending.
As mentioned, both of them are non-functional.
--
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=54639
Bug ID: 54639
Summary: some wine libraries are too old for KDE Neon 5.27.2
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bugcoder(a)gmail.com
Distribution: ---
Some libraries like libjpeg-turbo8:386 are too old for install wine on KDE NEON
2.27
--
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=52983
Bug ID: 52983
Summary: d3d8:device - test_wndproc() fails systematically on
Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d8:device - test_wndproc() fails systematically on Wine:
device.c:3212: Test failed: Expected message 0x3 for window 0, but didn't
receive it, i=49.
device.c:3359: Test failed: Expected message 0x3 for window 0x1, but didn't
receive it.
https://test.winehq.org/data/patterns.html#d3d8:device
As far as I can tell the missing "message 0x3 for window 0x1" is present every
time, while the one for "window 0" is only present most of the time but not
necessarily on the same iteration.
--
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=33069
Bug #: 33069
Summary: Visual Basic 6 can't load any component
Product: Wine
Version: 1.5.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: german_ant_82(a)yahoo.com
Classification: Unclassified
Created attachment 43719
--> http://bugs.winehq.org/attachment.cgi?id=43719
Fixme errors list for the components that can't be loaded
Visual Basic comes with a set of preloaded standard components and a set of
loadable extra components. These extra components can't be loaded.
List of components that can't be loaded:
AxBrowser
Cdlg
Microsoft ADO Data Control 6.0 (OLEDB)
Microsoft Calendar Control 8.0
Microsoft Chart Control 6.0 (OLEDB)
Microsoft Comm Control 6.0
Microsoft Common Dialog Control 6.0
Microsoft Data Bound Grid Control 5.0 (SP3)
Microsoft Data Bound List Controls 6.0
Microsoft DataGrid Control 6.0 (OLEDB)
Microsoft DataList Controls 6.0 (OLEDB)
Microsoft DataRepeater Control 6.0 (OLEDB)
Microsoft FlexGrid Control 6.0
Microsoft Hierarchical FlexGrid Control 6.0 (OLEDB)
Microsoft Internet Transfer Control 6.0
Microsoft MAPI Controls 6.0
Microsoft Masked Edit Control 6.0
Microsoft Multimedia Control 6.0
Microsoft PictureClip Control 6.0
Microsoft RemoteData Control 6.0
Microsoft Rich Textbox Control 6.0
Microsoft Script Control 1.0
Microsoft SysInfo Control 6.0
Microsoft Tabbed Dialog Control 6.0
Microsoft Windows Common Controls 5.0 (SP2)
Microsoft Windows Common Controls 6.0
Microsoft Windows Common Controls-2 5.0 (SP2)
Microsoft Windows Common Controls-2 6.0
Microsoft Windows Common Controls-3 6.0
Microsoft Winsock Control 6.0
MSFlexGrid Wizard 6.0
Package and Deployment Wizard
VB6 Application Wizard
VB6 Data Form Wizard 6.0
VB6 MSChart Wizard 6.0
VisModelBrowser
--
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=54636
Bug ID: 54636
Summary: fusion:asmenum - test_enumerate() fails on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: fusion
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
fusion:asmenum - test_enumerate() fails on Windows 11:
asmenum.c:367: Test failed: Assembly not enumerated: Microsoft.Ink,
Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.Interop.Security.AzRoles, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: srmlib, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: Microsoft.Ink,
Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.Interop.Security.AzRoles, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: srmlib, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: Microsoft.Ink.Resources,
Version=6.1.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.ManagementConsole.Resources, Version=3.0.0.0, Culture=en,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Commands.Diagnostics, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Commands.Diagnostics.Resources, Version=1.0.0.0,
Culture=en, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Commands.Management, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Commands.Management.Resources, Version=1.0.0.0,
Culture=en, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Commands.Utility, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Commands.Utility.Resources, Version=1.0.0.0, Culture=en,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.ConsoleHost.Resources, Version=1.0.0.0, Culture=en,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Security, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.PowerShell.Security.Resources, Version=1.0.0.0, Culture=en,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.WSMan.Management, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
Microsoft.WSMan.Management.Resources, Version=1.0.0.0, Culture=en,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: Microsoft.WSMan.Runtime,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: MMCEx, Version=3.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: MMCEx.Resources,
Version=3.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: MMCFxCommon,
Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated: MMCFxCommon.Resources,
Version=3.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
System.Management.Automation, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
asmenum.c:367: Test failed: Assembly not enumerated:
System.Management.Automation.Resources, Version=1.0.0.0, Culture=en,
PublicKeyToken=31bf3856ad364e35
See https://test.winehq.org/data/patterns.html#fusion:asmenum
Notes:
* Only the 32-bit fusion dll is available on Windows 11.
* On Windows 11 the dll was installed by running the dotnetfx-1.1.exe installer
[1] which is only available in 32-bit format.
* The fusion dll is entirely missing on all the Windows 8 and 10 VMs (the
32-bit version could be installed using the same process as on Windows 11).
* The 32-bit and 64-bit versions of this test succeed on the w7u and w7pro64
VMs.
* The 32-bit and 64-bit versions of this test succeed on the deprecated wxppro,
w2003std, wvista and wvistau64 VMs.
* See also bug 54610 for the fusion:asmcache crash.
[1] https://wiki.winehq.org/Wine_TestBot_VMs#fusion.2C_msvcr71
--
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=54610
Bug ID: 54610
Summary: fusion:asmcache - 32-bit calls to InstallAssembly(...,
NULL) crash on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: fusion
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
fusion:asmcache - 32-bit calls to InstallAssembly(..., NULL) crash on Windows:
asmcache.c:846: this is the last test seen before the exception
19e4:asmcache: unhandled exception c0000005 at 0095C478
See https://test.winehq.org/data/patterns.html#fusion:asmcache
The crash only happens in the 32-bit w11pro64 tests which represents 100% of
the cases where the test actually runs:
* The only VM that has the needed fusion dll is w11pro64.
* The dll was installed by running the dotnetfx-1.1.exe installer [1] which is
only available in 32-bit format. Thus only the 32-bit dll is available and the
64-bit test is skipped.
The crash happens in the following call:
hr = IAssemblyCache_InstallAssembly(cache, 0, L"wine.dll", NULL);
But skipping this call just moves the crash to the next InstallAssembly() call.
It's not clear whether the crash is caused by the NULL RefData pointer: the
crash still happens if I pass a non-NULL but pretty empty
FUSION_INSTALL_REFERENCE structure (in particular szNonCannonicalData == NULL).
[1] https://wiki.winehq.org/Wine_TestBot_VMs#fusion.2C_msvcr71
--
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=41013
Bug ID: 41013
Summary: Sourceinsight: the 'Window' menu click no response
Product: Wine
Version: 1.8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robert.hu(a)intel.com
Distribution: ---
Created attachment 55180
--> https://bugs.winehq.org/attachment.cgi?id=55180
'Window' menu list jump to top left
The menu of 'Window' click has no responses.
But other menu can work.
My workaround is to click its adjacent menu item then arrow key to move to
'Window' menu. But even so, it appears to left top of the window. See
attachment.
--
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=23064
Summary: Sourceinsight: no response clicking menu, untill
firstly right-click in main window area
Product: Wine
Version: 1.2-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dwwwww(a)hotmail.com
OS: RHEL 4
Wine, 1.2-rc2
Open sourceinsight, click the menus, no response.
But it works after right click in main window area.
--
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=54632
Bug ID: 54632
Summary: advapi32:registry causes scrobj:scrobj to crash when
run without elevated privileges on Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: scrobj
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:registry causes scrobj:scrobj to crash when run without elevated
privileges on Windows 8:
scrobj.c:767: Test failed: DllInstall failed: 80004005
scrobj.c:771: Test failed: RegQueryValueA failed: 2
scrobj.c:771: Test failed: Unexpected value "F", expected "WineTest object"
scrobj.c:772: Test failed: RegQueryValueA failed: 2
scrobj.c:772: Test failed: Unexpected value "F", expected "*\scrobj.dll"
scrobj.c:773: Test failed: RegQueryValueA failed: 2
scrobj.c:773: Test failed: Unexpected value "F", expected "WineTest.1.23"
scrobj.c:774: Test failed: RegQueryValueA failed: 2
scrobj.c:774: Test failed: Unexpected value "F", expected "WineTest"
scrobj.c:804: Test failed: Could not get class factory: 80040154
scrobj.c:804: this is the last test seen before the exception
0dbc:scrobj: unhandled exception c0000005 at 00403A9A
See https://test.winehq.org/data/patterns.html#scrobj:scrobj
This crash does not happen when running scrobj:scrobj on its own. I determined
that the source of interference is advapi32:registry.
It is the combination of test_reg_open_key() and test_classesroot() in
registry.c that causes the crash. More specifically this call in
test_classesroot():
res = RegCreateKeyExA( HKEY_LOCAL_MACHINE,
"Software\\Classes\\WineTestCls", 0, NULL, REG_OPTION_NON_VOLATILE,
KEY_ALL_ACCESS, NULL, &hklm, NULL );
--
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=50281
Bug ID: 50281
Summary: fsync patch for wine 6.0-rc1 (without staging)
Product: Wine
Version: 6.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: michael.scott(a)quest-arts.co.uk
Distribution: ---
Created attachment 68830
--> https://bugs.winehq.org/attachment.cgi?id=68830
fsync patch that applies to vanilla wine 6.0-rc1
I have created a new fsync patch that can apply directly to wine 6.0-rc1
without needing esync from staging.
I have tested this patch applied to the latest wine sources (6.0-rc1) as of 7th
December 2020 using Star Citizen 3.11.
I have included it here for you to review for your convenience to review
whether to include it in a future wine version.
Current testing from myself and others in the Star Citizen LUG org when using
fsync enabled wine and kernels are resulting in a much smoother experience.
--
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=54631
Bug ID: 54631
Summary: msi:package causes wscript.exe:run to time out when
run without elevated privileges on Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: wscript
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
msi:package causes wscript.exe:run to time out when run without elevated
privileges on Windows 8:
wscript.exe:run start programs/wscript/tests/run.c
run.c:400: running RUN.JS test...
wscript.exe:run:026c done (258) in 120s 35B
See https://test.winehq.org/data/patterns.html#wscript.exe:run
This timeout does not happen when running wscript.exe:run on its own. I
determined that the source of interference is msi:package and that the timeout
is caused by a Windows prompt:
Script: C:\Users\winetest\Documents\tests\test.JS
Line: 19
Error: Automation server can't create object
Code: 800A01AD
Source: Microsoft JScript runtime error
The timeout happens when waiting for the child process in run_script_file() in
run.c. That makes sense: the child process is stuck displaying the Windows
prompt:
WaitForSingleObject(pi.hProcess, INFINITE);
And the timeout is caused by the combination of test_appsearch() and
test_complocator() in package.c: remove either of those two and the timeout
does not happen anymore. More specifically, if leaving test_appsearch()
unmodified, any call to set_component_path() in test_complocator() triggers the
timeout, because of this call:
RegCreateKeyExA(HKEY_LOCAL_MACHINE, prodpath, 0, NULL, 0, access, NULL,
&hkey, NULL);
Note that creating the comppath key does not cause the wscript.exe:run timeout.
--
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=54604
Bug ID: 54604
Summary: improved file browser
Product: Wine-staging
Version: 8.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gizmo_1979(a)yahoo.it
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 74135
--> https://bugs.winehq.org/attachment.cgi?id=74135
file browser
it would be handy if the completion of the names if you type in the file name
field was implemented in the file open window called by the programs as it
happens in any system more modern than windows 95...
--
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=54620
Bug ID: 54620
Summary: advapi32:registry causes mshtml:htmldoc to time out
when run without elevated privileges on Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:registry causes mshtml:htmldoc to time out when run without elevated
privileges on Windows 8:
htmldoc.c:6220: put_href L"about:replace"...
htmldoc.c:6503: open...
htmldoc.c:6503: open...
mshtml:htmldoc:0744 done (258) in 120s 899B
See https://test.winehq.org/data/patterns.html#mshtml:htmldoc
This timeout does not happen when running mshtml:htmldoc on its own. I
determined that the source of interference is advapi32:registry and that the
timeout is caused by a UAC prompt:
A website wants to open web content using this
program on your computer.
This program will open outside of Protected mode. Internet Explorer's
Protected mode helps protect your computer. If you do not trust this
website, do not open this program.
Name: Microsoft Edge
Publisher: Microsoft Corporation
This happens in the IHTMLWindow2_open() call in test_open_window() in
htmldoc.c:
hres = IHTMLWindow2_open(window, url, name, NULL, VARIANT_FALSE,
&new_window);
So this issue is very similar to the ieframe:ie one described in bug 54613.
--
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=15480
Summary: Saving files in Word/Excel creates useless .lnk files
Product: Wine
Version: 1.1.5
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrew(a)etc.gen.nz
Hi,
In Word and Excel 2003 when we save files then a .lnk file is created in the
same directory as the source file. These files are useless for two reasons:
1) They're in the same directory as the original .doc or .xls files which have
Word and Excel associated with them respectively.
2) On a standard Debian Lenny machine running Gnome the .lnk files aren't
recognised by any apps and won't cause Word or Excel to run.
I've searched around the place to see if we can turn this "feature" off, but
haven't found anything. Is this possible? If not, could this please be added.
--
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=54141
Bug ID: 54141
Summary: console: pressing ctrl+4 in any console application
terminates it
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: taviso(a)gmail.com
Distribution: ---
Reproduce:
$ wine cmd.exe
Z:\home\taviso>
[Now press Ctrl+4]
I think all of the Ctrl+Number keys don't work (oddly, except Ctrl+2), but
Ctrl+4 is especially annoying because it immediately terminates the
application.
I was trying to use a Windows console application, but didn't have much luck
because of the missing keybindings.
--
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=53501
Bug ID: 53501
Summary: Test Drive Unlimited not working
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ds000001(a)outlook.de
Distribution: ---
Created attachment 72860
--> https://bugs.winehq.org/attachment.cgi?id=72860
Lutris and Wine
Hello,
I try to run Test Drive Unlimited DVD 1.66 version with Wine.
My system:
CPU: 3700X
GPU: 6700XT
RAM: 32 GB
Wine: 7.15 installed through pacman and using Lutris 0.5.10.1-2 for easier
management of all WINEPREFIX's
WINEPREFIX:
- 32 Bit and complete new
- Through winecfg set as Win XP
- No additional packages installed
- ESync, Fsync and DXVK not enabled
- Virtual window mode enabled with 1080p resolution, that way it is easier for
me to see, if something happens or not
- no additional modules installed with Winetricks
If I try to start the game, the configured Wine desktop appears, the disc drive
starts to spin and after that nothing happens.
Output from "lutris -d" and enabled diagnostics for the WINEPREFIX gave me the
output from
tdudebug1.txt.
Enabled debug with "WINEDEBUG=warn+all" and tried to start the game through the
wine command. Got the log tdudebug2.txt out of this.
Any ideas what I am doing wrong?
--
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=9221
Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |leslie_alistair(a)hotmail.com
--
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=45756
Bug ID: 45756
Summary: Button not clickable when dpi setting changed in
Office 2007 Installer
Product: Wine
Version: 3.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
After upgrading from wine 3.14 to wine 3.15 (self-compiled, 32-bit-only) the
push buttons in the office 2007 installer are no longer "clickable".
When pushing them with the mouse, nothing happens. Using the keyboard to "push"
the buttons works as before. Sometimes the mouse pointer is not even visible
inside the installer window.
This only happens when changing the screen resolution in winecfg (i.e. to 168
dpi). The windows version is set to Windows XP
A bisect shows this commit as the first bad commit:
commit 2068b73db5e19e1ce3b54b2a8ecb5a5b99ea19b5
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Aug 27 14:02:43 2018 +0200
user32: Process hardware messages in physical coordinates.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=39113
Bug ID: 39113
Summary: SimplePC_SC.exe does not work
Product: Wine
Version: unspecified
Hardware: x86
URL: http://downloads.acs.com.hk/utility-tools/en/TOL-PCSC.
zip
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winscard
Assignee: wine-bugs(a)winehq.org
Reporter: vincent.hardy.be(a)gmail.com
Distribution: ---
Created attachment 52115
--> https://bugs.winehq.org/attachment.cgi?id=52115
screenshot
SimplePC_SC is a programme that tests easily the basic functions of winscard
with any smartcard.
I file this bug in the hope that a friendly developer starts a real
implementation of winscard.
--
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=53728
Bug ID: 53728
Summary: "Escape from Tarkov" requires
"DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" in
"DisplayConfigGetDeviceInfo" stub
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: vinni5.2001(a)web.de
Distribution: ---
Created attachment 73161
--> https://bugs.winehq.org/attachment.cgi?id=73161
Attachments for this report.
The video game "Escape from Tarkov" requires the
"DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" type to be implemented in the
"DisplayConfigGetDeviceInfo" function (dlls/user32/sysparams.c).
The game uses that to determine monitor names to list in the ingame settings
menu.
When it first introduced the use of that function, the lack of it in wine made
the whole menu freeze, forcing you to kill the game. That freeze was worked
around by the game developers on their end, since it also affected some Windows
users, but parts of the issue still remain when running the game in wine.
Monitor names in the monitor list in the settings menu are simply blank, making
it hard to figure out which entry in the list corresponds to which monitor. See
"eft_monitors_blank.png" in "attachments.tar.gz" for reference.
Creating a quick and dirty patch to make wine return a string and pretend the
function was executed successfully confirms it is using that function to get
monitor names and the returned string shows up in the list. See
"eft_monitors_names.png" and "dirty-monitor-name-workaround.patch" in
"attachments.tar.gz" for reference.
I should mention that in case other people wanna test the game, it is not free
and makes use of the BattlEye anticheat software, so in order to launch the
game with wine, it requires staging, a patch to load the Proton BattlEye
Runtime (found here, for example:
https://github.com/Frogging-Family/wine-tkg-git/tree/master/wine-tkg-git/wi…),
as well as the Proton BattlEye Runtime itself (can be found and installed via
Steam by Valve) and the necessary environment variable that points to the
Proton BattlEye Runtime ("PROTON_BATTLEYE_RUNTIME"="/path/to/runtime"). It also
needs "corefonts", "vcrun2019" and "dotnet48" installed via winetricks.
I hope those requirements won't prevent this issue from being looked into, but
if they do, I apologize. I was able to put together the quick and dirty patch
to confirm it is indeed just a missing or incomplete function, however I lack
the programming skills and low-level wine/windows knowledge to implement it
properly.
Thank you!
--
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=53176
Bug ID: 53176
Summary: KeePassXC needs
Windows.Security.Credentials.KeyCredentialManager
(UWP)
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: mk939(a)ymail.com
Distribution: ---
Created attachment 72622
--> https://bugs.winehq.org/attachment.cgi?id=72622
stdout and stderr from the terminal while launching the application
KeePassXC 2.7.1 (64-bit, Windows) can no longer be started due to a new Windows
Hello feature. Older versions prior to Feb 2022 will work as expected.
I reproduced this issue on two different machines, each with Wine 7.11
(vanilla).
Source code:
https://github.com/keepassxreboot/keepassxc/blob/develop/src/winhello/Windo…
Specifically, creating a stub for `IsSupportedAsync()` might suffice to disable
the feature for this application, assuming a proper implementation on their
side:
https://github.com/keepassxreboot/keepassxc/blob/develop/src/winhello/Windo…
PS: The error mentions "combase", but is not an available choice in the bug
report selection box. I am sorry if the selected component is wrong.
--
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=54584
Bug ID: 54584
Summary: kernel32:locale - The NtGetNlsSectionPtr() test fails
on Windows 11
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:locale - The NtGetNlsSectionPtr() test fails on Windows 11:
locale.c:4978: Test failed: 14: failed 0
See https://test.winehq.org/data/patterns.html#kernel32:locale
This means Windows 11 supports a new type of NLS section (14). Also
NtGetNlsSectionPtr() returns success so presumably that section type does not
take an id parameter.
--
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=54583
Bug ID: 54583
Summary: kernel32:locale - The non-breaking space
GetNumberFormatEx() test fails on Windows 11
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:locale - The non-breaking space GetNumberFormatEx() test fails on
Windows 11:
locale.c:1820: Test failed: Expected L"-12\00a0345,00", got L"-12\202f345,00"
See https://test.winehq.org/data/patterns.html#kernel32:locale
So Windows 11 returns a narrow non-breaking space instead of a 'plain'
non-breaking space separator when using the French format.
The narrow non-breaking space is probably more correct.
--
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=54534
Bug ID: 54534
Summary: dbghelp:dbghelp - The test_loaded_modules()
enumeration fails on Windows 10 1607
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dbghelp:dbghelp - The test_loaded_modules() enumeration fails on Windows 10
1607:
dbghelp.c:517: Test failed: SymLoadModuleExW failed on
C:\WINDOWS\System32\bcryptPrimitives.dll: 0
See https://test.winehq.org/data/patterns.html#dbghelp:dbghelp
This is the only Windows 10 version which fails.
A bisect confirms that this failure was introduced by the commit below:
8be5c10ff893a22330ad94ae18dfb5fa497b09fd
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Thu Feb 16 10:48:53 2023 +0100
dbghelp/tests: Add tests for 'module' name in EnumLoadedModules() callback.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
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=43224
Bug ID: 43224
Summary: Freelist scan can result in O(n) time when allocating
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: ranma42(a)gmail.com
Distribution: ---
Created attachment 58517
--> https://bugs.winehq.org/attachment.cgi?id=58517
Micro-benchmark that shows the degenerate behaviour
The heap implementation in ntdll can be very inefficient for some allocation
patterns.
Specifically, it is possible that a freelist contains thousands of entries of a
given size and it is scanned while looking for a bigger entry, that will not
fit in any of those.
This is demonstrated by the attached program. It accepts a size as an argument
and will allocate 1000000 elements of that size, deallocate half of them (the
"even" ones), then allocate 1000 elements that are just one bit bigger.
For most sizes the program terminates in milliseconds, but in my environment it
takes several seconds for sizes 16, 32, 48, 64, 80, 88, 96, 112, 120, 128.
A possible workaround (that I had implemented in the past, for short-lived
applications) is to allocate from a freelist whose entries are all at least as
big as the block that is being allocated, but that can cause inefficient memory
usage.
I noticed that wine includes an implementation of a red-black tree.
Would it make sense to organise the free entries as lists in such a tree?
That should ensure O(log N) in the worst case.
If performance is a concern, it might be possible to use "direct" freelists for
small sizes (ensuring that all of the alignment-compatible sizes are covered)
and use a tree for bigger sizes.
I am willing to work on this, but I need some directions on what is the best
path forward (namely, if we should prefer the memory-inefficient but simpler
approach of just allocating from "bigger" freelists or if the tree approach is
the desired one).
The bug https://bugs.winehq.org/show_bug.cgi?id=37773 might be related.
--
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=37146
Bug ID: 37146
Summary: Untis 2015: Crashes while starting
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: schutthuffe(a)web.de
Created attachment 49371
--> https://bugs.winehq.org/attachment.cgi?id=49371
Report generated by wine
Installing Untis 2015 seemed to work. Trying to start the program, the
following message popped up: "Im Programm untis.exe traten schwerwiegende
Fehler auf und es muss beendet werden. Wir entschuldigen uns für die
Unannehmlichkeit." The following report is 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=54582
Bug ID: 54582
Summary: kernel32:locale - test_NLSVersion() fails on Windows
10 22H2
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:locale - test_NLSVersion() fails on Windows 10 22H2:
locale.c:7871: Test failed: IsValidNLSVersion succeeded
See https://test.winehq.org/data/patterns.html#kernel32:locale
Apparently the point of this set of test is to verify that IsValidNLSVersion()
rejects any version different from that returned by GetNLSVersion().
But sometimes that's not the case. Indeed a similar failure happened on Windows
10 2004 back in the day, see bug 51159. In that case IsValidNLSVersion()
accepted versions 0x100 lower than the current one, presumably because that
version of Windows was keeping compatibility with older NLS versions. That one
was fixed by making bigger changes to the version.
In this case Windows 10 22H2 accepts NLS versions that are 0x100 greater than
the current one. So presumably we can just use a larger increment to get the
expected failure.
--
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=54338
Bug ID: 54338
Summary: Swift crashes due unimplemented
QueryUnbiasedInterruptTimePrecise function
Product: Wine
Version: 8.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal(a)protonmail.com
Distribution: ---
Swift language after installing, crashes with this message
```
wine: Call from 000000017002FA08 to unimplemented function
api-ms-win-core-realtime-l1-1-1.dll.QueryUnbiasedInterruptTimePrecise, aborting
wine: Unimplemented function
api-ms-win-core-realtime-l1-1-1.dll.QueryUnbiasedInterruptTimePrecise called at
address 000000017002FA08 (thread 0110), starting debugger...
```
Steps to reproduce
- install Swift 5.7.2 -
https://download.swift.org/swift-5.7.2-release/windows10/swift-5.7.2-RELEAS…
- execute `wine swift`
--
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=53504
Bug ID: 53504
Summary: Sacred:unhandled exception in Wine 7.14
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chebanenkoigor93(a)gmail.com
Distribution: ---
Created attachment 72868
--> https://bugs.winehq.org/attachment.cgi?id=72868
screenshot
Wine 7.14 gives me exception after launching Sacred.
--
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=24256
Summary: 3D Sexvilla 2: extremely long loading times
Product: Wine
Version: 1.2
Platform: x86
URL: http://www.3d-sexgames.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mailme667(a)yahoo.co.uk
Loading time makes the game unusable (version 2.093). I just watched the
loading screen for half an hour. But I know it works, because I tried starting
the game, turning the monitor off, having dinner and see the game running when
I came back a long time later.
Clean .wine tested. Other users in appdb have reported the same problem, it's
not just me.
Bug is tested to be present on wine 1.2 and 1.3.1. sysprof makes it clear ntdll
is consuming nearly all the time.
Using wine 1.2 the following is seen repeating over and over with winedebug
during loading:
002e:Call KERNEL32.GetTickCount() ret=7da7655d
002e:Ret KERNEL32.GetTickCount() retval=00032601 ret=7da7655d
002e:Call KERNEL32.GetTickCount() ret=7e7997bb
002e:Ret KERNEL32.GetTickCount() retval=00032601 ret=7e7997bb
002e:Call KERNEL32.GetTickCount() ret=7e7997bb
002e:Ret KERNEL32.GetTickCount() retval=00032607 ret=7e7997bb
002e:Call KERNEL32.GetTickCount() ret=7da76415
002e:Ret KERNEL32.GetTickCount() retval=00032607 ret=7da76415
002e:Call ntdll.RtlAcquireResourceShared(00187fa4,00000001) ret=7da76541
002e:Ret ntdll.RtlAcquireResourceShared() retval=00000001 ret=7da76541
002e:Call ntdll.RtlReleaseResource(00187fa4) ret=7da76555
002e:Ret ntdll.RtlReleaseResource() retval=00000000 ret=7da76555
I got the following from wine-dbg also using 1.2:
Wine-dbg>bt 0x0000002e
Backtrace:
=>0 0xb7705430 (0x04e0e9d8)
1 0x7e78ea4a TIME_MMSysTimeThread+0x329(arg=0x4e0ea34)
[/build/buildd/wine1.2-1.2/dlls/winmm/time.c:218] in winmm (0x04e0ea68)
2 0x7e78ea4a TIME_MMSysTimeThread+0x329(arg=0x7e770000)
[/build/buildd/wine1.2-1.2/dlls/winmm/time.c:218] in winmm (0x04e0ea78)
3 0x7bc6f8f0 call_thread_func+0xb() in ntdll (0x04e0eb48)
4 0x7bc6fac0 call_thread_entry_point+0x6f(entry=0x7e78e720, arg=0x7e770000)
[/build/buildd/wine1.2-1.2/dlls/ntdll/signal_i386.c:2473] in ntdll (0x04e0f398)
5 0x7bc780b5 start_thread+0xf4(info=0x7ff9cfb8)
[/build/buildd/wine1.2-1.2/dlls/ntdll/thread.c:399] in ntdll (0x04e0f498)
6 0xb757780e start_thread+0xbd() in libpthread.so.0 (0x00000000)
I hope I've provided enough information.
--
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=53094
Bug ID: 53094
Summary: ntdll:rtlstr test crashes on win32 arch with hi-IN
locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: rbernon(a)codeweavers.com
Regression SHA1: d8c973ad95ba5e8a9a51df0dd9be587950179ec3
Distribution: ---
As seen on the testbot nightly runs there for instance:
https://test.winehq.org/data/c1e793f1119de0c0ef7d4bd6d9fefbafdb5dbbe5/linux…
Locally reproducible with:
LC_ALL=hi-IN.UTF-8 LC_LANG=hi-IN.UTF-8 WINEARCH=win32 WINEPREFIX=$PWD/pfx
wine32/wine wine32/dlls/ntdll/tests/ntdll_test.exe rtlstr
Bisected to:
commit d8c973ad95ba5e8a9a51df0dd9be587950179ec3
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon May 30 22:38:28 2022 +0200
kernelbase: Reimplement CompareStringEx using the sortkey generation code.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/kernel32/tests/locale.c | 117 +++++++++-----------
dlls/kernelbase/locale.c | 247 +++++++++++++++++--------------------------
2 files changed, 147 insertions(+), 217 deletions(-)
--
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=51259
Bug ID: 51259
Summary: 6.0.1 Introduces error causing Wavelab to close when
loading presets
Product: Wine
Version: 6.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shagooserver(a)gmail.com
Distribution: ---
Update 6.0.1 (7/6/21) introduces an error whereby Wavelab 6 closes/crashes when
a preset is loaded (into the master section).
The terminal outputs:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 151 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 6199
Current serial number in output stream: 6200
--
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.