https://bugs.winehq.org/show_bug.cgi?id=46017
Bug ID: 46017
Summary: Layers of Fear areas are almost entirely black
rendered
Product: Wine
Version: 3.18
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 62591
--> https://bugs.winehq.org/attachment.cgi?id=62591
screenshot
Main hall.
err:d3d:wined3d_debug_callback 0x937c010: "GL_INVALID_FRAMEBUFFER_OPERATION
error generated. Operation is not valid because a bound framebuffer is not
framebuffer complete.".
fixme:d3d:context_check_fbo_status FBO status
GL_FRAMEBUFFER_INCOMPLETE_LAYER_TARGETS (0x8da8).
fixme:d3d:context_dump_fbo_attachment GL_DEPTH_ATTACHMENT: 2d texture 1116,
128x128, 0 samples, format 0x81a5.
fixme:d3d:context_dump_fbo_attachment GL_STENCIL_ATTACHMENT: NONE.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT0: 2d-array
texture 1112, 128x128, 0 samples, format 0x822e.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT1: NONE.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT2: NONE.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT3: NONE.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT4: NONE.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT5: NONE.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT6: NONE.
fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT7: NONE.
wine-3.18-114-g417e94f199
--
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=51624
Bug ID: 51624
Summary: TETRIS (16bit) shows wrong background for scoreboard
Product: Wine
Version: 6.14
Hardware: x86-64
OS: Linux
Status: NEW
Severity: trivial
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 70480
--> https://bugs.winehq.org/attachment.cgi?id=70480
Screenshot showing the issue
Follow up to bug 51570.
The graphics of the game almost work now, but the scoreboard to the left has
the wrong background.
--
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=32991
Bug #: 32991
Summary: ARM port of "WabbitEMU" crashes due to unimplemented
function KERNEL32.dll.RtlUnwindEx (no ntdll forward on
arch=arm)
Product: Wine
Version: 1.5.24
Platform: arm
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello folks,
the ARM port of "WabbitEMU", a Texas Instruments graphing calculator emulator
and dev tools crashes after clicking "Browse for a ROM image" radio button in
image selection dialog.
Download: http://forum.xda-developers.com/showpost.php?p=37928562
(main thread: http://forum.xda-developers.com/showthread.php?t=2092348)
--- snip ---
$ WINEDEBUG=+tid,+seh,+relay wine ./Wabbitemu.exe
...
0024:Call user32.GetWindowTextA(00010096,40a0ebf0,00000104) ret=00439fa5
0024:Call window proc 0x40bc5f30
(hwnd=0x10096,msg=WM_GETTEXT,wp=00000104,lp=40a0ebf0)
0024:Ret window proc 0x40bc5f30
(hwnd=0x10096,msg=WM_GETTEXT,wp=00000104,lp=40a0ebf0) retval=00000000
0024:Ret user32.GetWindowTextA() retval=00000000 ret=00439fa5
0024:Call KERNEL32.GetLastError() ret=004141cf
0024:Ret KERNEL32.GetLastError() retval=00000000 ret=004141cf
0024:trace:seh:raise_exception info[0]=0047be54
0024:trace:seh:raise_exception info[1]=0047cc8e
wine: Call from 0x7bc9a630 to unimplemented function KERNEL32.dll.RtlUnwindEx,
aborting
0024:trace:seh:call_stack_handlers calling handler at 0x7bcb8d88 code=80000100
flags=1
0024:Call KERNEL32.UnhandledExceptionFilter(40a0e81c) ret=7bcb8df0
--- snip ---
The app is importing all win32 API by name so it's the real thing :-)
+module,+imports
--- snip ---
...
0009:trace:module:load_dll looking for L"KERNEL32.dll" in
L"Z:\\home\\linaro\\wine-apps\\wabbitemu;.;C:\\windows\\system32;C:\\windows\\system;C:\\windows;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem"
0009:trace:module:load_dll Found L"C:\\windows\\system32\\KERNEL32.dll" for
L"KERNEL32.dll" at 0x7b820000, count=19
0009:warn:module:import_dll No implementation for KERNEL32.dll.RtlUnwindEx
imported from L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting
to 0x41820000
0009:trace:imports:import_dll --- RtlUnwindEx KERNEL32.dll.1209 = 0x41820000
0009:trace:imports:import_dll --- GetCommandLineA KERNEL32.dll.481 = 0x7b846be0
0009:trace:imports:import_dll --- RtlPcToFileHeader KERNEL32.dll.1205 =
0x7bc69188
0009:warn:module:import_dll No implementation for
KERNEL32.dll.RtlLookupFunctionEntry imported from
L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting to 0x41820024
0009:trace:imports:import_dll --- RtlLookupFunctionEntry KERNEL32.dll.1203 =
0x41820024
0009:trace:imports:import_dll --- GetModuleFileNameW KERNEL32.dll.634 =
0x7b86b864
...
--- snip ---
It also needs KERNEL32.dll.RtlLookupFunctionEntry later.
Wine forwards both to ntdll but only on arch=x86_64.
It seems Windows RT exposes both API.
Interestingly only the MSDN page for KERNEL32.dll.RtlLookupFunctionEntry gives
a hint about this:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms680597%28v=vs.85%…
("ARM Definition").
Regards
--
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=51557
Bug ID: 51557
Summary: GetSystemFirmwareTable fails to return SMBIOS on Apple
Silicon Macs
Product: Wine
Version: 6.14
Hardware: aarch64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bshanks(a)codeweavers.com
The macOS implementation of GetSystemFirmwareTable() retrieves the system's
actual SMBIOS table using IOKit. This fails on Apple Silicon/ARM64 Macs, since
they don't have an SMBIOS table.
This breaks any applications that depend on getting an SMBIOS table (like the
Rockstar Games Launcher) or that look for the
HKLM/Hardware/Description/System/BIOS registry keys.
I think the fix will be to use the SMBIOS table creation functions used by
Linux currently, with strings and data (serial number, UUID, etc) coming from
IOKit if possible.
--
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=51490
Bug ID: 51490
Summary: dinput:device has a random failure in
overlapped_format_tests() on Windows 8.1
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dinput:device has a random failure on the w8 VM:
https://test.winehq.org/data/patterns.html#dinput:device
device.c:374: Test failed: keydown for D did not register
It sort of looks like a race condition though the pump_messages() call should
take care of that.
The failing test (and all of overlapped_format_tests()) was added by the
following commit.
commit d10887b8f56792ebcca717ccc28a289f7bcaf107
Author: Arkadiusz Hiler <ahiler(a)codeweavers.com>
AuthorDate: Thu Jul 8 13:03:21 2021 +0300
dinput: Don't add 'default value 0' entries to the data transform.
This helps when dealing with the quirky c_dfDIJoystick2 format,
which defines all the sliders as overlapping, i.e. rglSlider[2],
rglVSlider[2], rglASlider[2] and rglFSlider[2] all share the same
offset.
With the Linux backends, if the device exposes enough axes (e.g. some
HOTAS) we end up using rglSlider.
Let's make sure we don't unnecessarily override the values there.
Signed-off-by: Arkadiusz Hiler <ahiler(a)codeweavers.com>
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=48119
Bug ID: 48119
Summary: The tests sometimes trigger "critical section is not
acquired" errors
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The logs of most test runs, WineTest and others, contain critical section
errors complaining that the critical section was not acquired before being
released.
Most are caused by the following two tests:
msvcp120:msvcp120 intentionally triggers one such error in test_threads__Mtx().
It's easy to identify because it follows a bunch of CreateSymbolicLinkA()
fixmes:
0044:fixme:file:CreateSymbolicLinkA ("tr2_test_dir/f1_symlink"
"tr2_test_dir/f1" 0): stub
0044:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: beef
0044:err:ntdll:RtlLeaveCriticalSection section 0x622088 is not acquired
ntdll:rtl intentionally triggers two such errors in
test_RtlLeaveCriticalSection(). They stand alone but would typically follow a
bunch of RtlGetCompressionWorkSpaceSize fixmes from previous tests:
https://testbot.winehq.org/JobDetails.pl?Key=60096
0009:err:ntdll:RtlLeaveCriticalSection section 0x7bfd88 is not acquired
0009:err:ntdll:RtlLeaveCriticalSection section 0x7bfd88 is not acquired
But there are other logs that contain this error with no identified source. For
instance in task 60103/4/2 (wow64) which is for an unrelated patch and only
runs kernel32 tests which do not normally trigger this error:
https://testbot.winehq.org/JobDetails.pl?Key=60103#k402
[...]
Extracting: Done (1 of 1)
Running tests
003e:err:ntdll:RtlLeaveCriticalSection section 0x14c80 is not acquired
002e:fixme:console:GetConsoleProcessList ((nil),0): stub
[...]
Or task 59774/4/1 (win32) which only ran comctl32 tests:
https://testbot.winehq.org/JobDetails.pl?Key=59774#k401
Or task 59426/1/1 (wow32) which only ran user32 tests:
https://testbot.winehq.org/JobDetails.pl?Key=59426
Or task 59176/3/1 (wow32/wow64?) which, again, only ran user32 tests:
https://testbot.winehq.org/JobDetails.pl?Key=59176#k301
Or task 59042/1/1 (wow32/wow64?) which, again, only ran user32 tests:
https://testbot.winehq.org/JobDetails.pl?Key=59042#k101
--
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=25193
Summary: Dasher does not operate correctly
Product: Wine
Version: 1.3.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: physicspirate(a)yahoo.ca
Greetings,
I've attempted to run
Dasher(http://appdb.winehq.org/objectManager.php?sClass=version&iId=21982&i…
and it does not appear to be loading or functioning correctly.
I've attached a screenshot of what happens after loading. There is a gray box
up top, and it appears to be non responsive. There also seems to be some
problems with the networking as I have a high speed connection, and their
servers tell me my latency is too high. If I run the same program on windows
it runs like a dream.
--
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=51733
Bug ID: 51733
Summary: CreateProcess does not properly set the current
directory of the new process.
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: johnfound(a)asm32.info
Distribution: ---
Regression.
The current directory of the new process, created with CreateProcessW is always
set to "/" (z:\) instead of the current directory of the parent process.
I am testing with the following call:
The last version that works properly is WINE 6.12
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51415
Bug ID: 51415
Summary: Windows PC Health Check requires msvcp_win.dll
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Run `winecfg` and set the Windows version to Windows 10.
2. Run `wine msiexec /i WindowsPCHealthCheckSetup.msi` and click through the
installer.
3. When the installer finishes and the app tries to start, you will see:
0164:err:module:import_dll Library msvcp_win.dll (which is needed by
L"C:\\users\\alex\\AppData\\Local\\PCHealthCheck\\PCHealthClient.dll") not
found
This DLL appears to be yet another copy of the Microsoft C++ runtime.
$ sha256sum WindowsPCHealthCheckSetup.msi
45c82e40ed0e27db7c55e0554512631b8f175b06d9b2d2cf58db52b18f0913fa
--
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=51307
Bug ID: 51307
Summary: msvcp140:msvcp140 fails on msvcp140 >= 14.25
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
On cw-rx460 machines that have either Radeon 21.3.2 or 21.4.1 the 64-bit
msvcp140:msvcp140 test fails:
https://test.winehq.org/data/patterns.html#msvcp140:msvcp140
msvcp140.c:1257: Test failed: ret = 37, expected 39
msvcp140.c:1258: Test failed: buf = The operation completed
successfully.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaThe
operation completed successfully.
, expected The operation completed successfully.
This is probably because the Radeon driver upgrades the 64-bit msvcp140.dll.
Currently we have:
Radeon msvcp140
cw-rx460-1507 19.11.3 14.14.26429.4
cw-rx460-1709 19.11.3 14.14.26429.4
cw-rx460-1809 19.11.3 14.14.26429.4
cw-rx460-1909 21.4.1 14.25.28508.3
cw-rx460-2009 21.4.1 14.25.28508.3
Also:
w1064v1507 - -
w1064v1607 - 14.0.23026.0
w1064v1709 - 14.0.23026.0
w1064v1809 - 14.0.23026.0
w1064v1909 - 14.0.23026.0
w10pro64 (2004) - 14.0.23026.0
w1064 (2009) - 14.0.23026.0
Note that the 14.0.23026.0 version comes from the "Visual C++ 2015
redistributables" package [1]. So all Radeon drivers actually install a newer
version.
But according to Chocolatey there are quite a few even newer versions, the
current latest being 14.29.30037. But there does not seem to be any
microsoft.com download URLs for it :-(
https://community.chocolatey.org/packages/vcredist140#versionhistory
[1] https://wiki.winehq.org/Wine_TestBot_VMs#msvcp140.2C_msvcr140.2C_ucrtbase
--
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.