https://bugs.winehq.org/show_bug.cgi?id=55295
Bug ID: 55295
Summary: d3dcompiler_43:hlsl_d3d11 - test_sampling() triggers
GLSL errors 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: ---
d3dcompiler_43:hlsl_d3d11 - test_sampling() triggers GLSL errors in Wine:
0668:err:d3d:wined3d_debug_callback 0166D4E8: "0:39(1): error: error index must
be >= 0".
0668:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#2:
0668:fixme:d3d_shader:print_glsl_info_log 0:39(8): warning: signed literal
value `4294967295' is interpreted as -1
0668:fixme:d3d_shader:print_glsl_info_log 0:39(1): error: error index must
be >= 0
These happen at least with the QEmu and Intel GPUs (HD Graphics 4600). Because
these warnings appear in the Wine log they cannot be seen in the nightly
WineTest reports. However one can see these warnings in the TestBot's Debina
WineTest jobs, both in the summary and in the "task.log" files.
Also, to see these warnings one has to delete the shader cache since they
happen during compilation:
rm -rf ~/.cache/mesa_shader_cache/
--
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=55294
Bug ID: 55294
Summary: d3d11:d3d11 generates some GLSL uninitialized register
warnings 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: ---
d3d11:d3d11 generates some GLSL uninitialized register warnings in Wine:
010c:fixme:d3d_shader:print_glsl_info_log 0:38(9): warning: `R0' used
uninitialized
010c:fixme:d3d_shader:print_glsl_info_log 0:38(16): warning: `R0' used
uninitialized
010c:fixme:d3d_shader:print_glsl_info_log 0:72(9): warning: `R0' used
uninitialized
010c:fixme:d3d_shader:print_glsl_info_log 0:72(16): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:37(56): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:38(56): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:39(56): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:40(56): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:41(59): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:42(59): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:43(59): warning: `R0' used
uninitialized
0110:fixme:d3d_shader:print_glsl_info_log 0:44(59): warning: `R0' used
uninitialized
These happen at least with the QEmu and Intel GPUs (HD Graphics 4600). Because
these warnings appear in the Wine log they cannot be seen in the nightly
WineTest reports. However one can see these warnings in the TestBot's Debina
WineTest jobs, both in the summary and in the "task.log" files.
Also, to see these warnings one has to delete the shader cache since they
happen during compilation:
rm -rf ~/.cache/mesa_shader_cache/
Commenting out the tests shows that these warnings are caused by the following
d3d11 tests:
test_sample_shading()
test_standard_pattern()
--
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=7767
Michael Stefaniuc <mstefani(a)winehq.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.0.x
--
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=55091
Bug ID: 55091
Summary: Wine fails compiling
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: eric.pouech(a)gmail.com
Distribution: ---
wine (c47c4d54bdf9a0f2100045fb6bc163291960fa05) fails to compile:
```
CCLD loader/wine64-preloader
loader/preloader.o: in function `wld_start':
/home/eric/wine/wine/loader/preloader.c:1402:(.text+0xc33): failed to convert
GOTPCREL relocation against '_start'; relink with --no-relax
collect2: error: ld returned 1 exit status
```
adding -Wl,--no-relax to preloader link operation fixes the issue
(at least allows linking, and notepad starts)
$ uname -a
Linux fedora.home 6.3.8-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 15
02:15:40 UTC 2023 x86_64 GNU/Linux
(split from https://bugs.winehq.org/show_bug.cgi?id=55050)
--
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=55203
Bug ID: 55203
Summary: ws2_32:sock - test_AcceptEx() sometimes gets
WSAEWOULDBLOCK and times out on Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ws2_32:sock - test_AcceptEx() sometimes gets WSAEWOULDBLOCK and times out on
Windows 10:
sock.c:8704: Test failed: failed to accept, error 10035
sock.c:8716: Test failed: got 0xc0000023
sock.c:8751: Test failed: got 00000000
sock.c:8765: Test failed: AcceptEx on too small remote address size returned 0
+ errno 10022
sock.c:8785: Test failed: AcceptEx returned 0 + errno 10022
sock.c:8805: Test failed: got error 10056
ws2_32:sock:13d4 done (258) in 120s 488B
See https://test.winehq.org/data/patterns.html#ws2_32:sock
Where:
10022 == WSAEINVAL
10035 == WSAEWOULDBLOCK
10056 == WSAEISCONN
0xC0000023 == STATUS_BUFFER_TOO_SMALL
This happened 6 times in the past 8 months, all on Windows 10:
* 2023-02-07 win22H2_fgtb-w10pro64-64
* 2023-03-23 win21H1_newtb-w10pro64-zh-CN-64
* 2023-03-31 win2004_newtb-w10pro64v2004-64
* 2023-05-30 win1909_newtb-w1064v1909-64
* 2023-06-23 win21H1_newtb-w10pro64-ja-64
* 2023-07-06 win21H1_newtb-w10pro64-de-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=55247
Bug ID: 55247
Summary: Assertion in riched20 while installing Office 2007
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
Created attachment 74844
--> https://bugs.winehq.org/attachment.cgi?id=74844
Log file with WINEDEBUG=riched20
The installer of Office 2007 fails with an assertion in riched20.
A bisect shows the following commit
commit b70eb32c5f3e506181d9e1e9fbef62e9baf3674d
Author: Jinoh Kang <jinoh.kang.kr(a)gmail.com>
Date: Sat Jul 1 13:22:46 2023 +0900
riched20: Wrap marked paragraphs at Text Services initialization.
Today, CreateTextServices() returns an Rich Edit object without row
start and end marks, which are expected to exist by many Rich Edit
operations as well as EM_* message handlers.
This leads to a crash when certain messages (e.g., EM_SCROLLCARET) are
sent to the Rich Edit object via ITextServices::TxSendMessage(), unless
ME_WrapMarkedParagraphs() has been called beforehand.
Fix this by calling wrap_marked_paras_dc() early in the initialization
process.
This is not a problem for windowed Rich Edit controls, which already
calls ME_WrapMarkedParagraphs() before the user or application starts
interacting with it.
dlls/riched20/para.c | 1 +
dlls/riched20/tests/txtsrv.c | 18 ++++++++++++++++++
2 files changed, 19 insertions(+)
A log file with WINEDEBUG=riched20 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=54688
Bug ID: 54688
Summary: ntdll:info - test_query_cpu() fails on Windows 7
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_cpu() fails on Windows 7:
32-bit case:
info.c:382: Test failed: SystemProcessorFeaturesInformation failed c0000003
info.c:383: Test failed: wrong len 3735928559
info.c:384: Test failed: wrong bits 5 / a0cd3fff
64-bit case:
info.c:382: Test failed: SystemProcessorFeaturesInformation failed c0000003
info.c:383: Test failed: wrong len 3735928559
info.c:384: Test failed: wrong bits c0000003 / b1993dfe
See https://test.winehq.org/data/patterns.html#ntdll:info
Where:
0xc0000003 == STATUS_INVALID_INFO_CLASS
These are new tests introduced in the commit below:
commit c44e58c88bd1a67ecb2f58472b1c67ab5f3ccb80
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Tue Mar 14 17:37:33 2023 +0100
ntdll: Implement the SystemProcessorFeaturesInformation query.
--
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=54503
Bug ID: 54503
Summary: d3dx9_36:math - test_D3DXSHMultiply3() fails on Debian
Testing
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3dx9_36:math - test_D3DXSHMultiply3() fails on Debian Testing:
math.c:4099: Test failed: Expected[6] = 4.27384138e+000, received =
4.27386904e+000.
See https://test.winehq.org/data/patterns.html#d3dx9_36:math
This looks like another imprecision problem.
What's notable is that this failure:
* Does not happen on Windows.
* Does not happen on Debian 11.
* Started happening on Debian Testing after the 2023-01-15 upgrade.
So it may be that some Debian library is in the 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=50868
Bug ID: 50868
Summary: League of Legends: infinite loading after login
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ickoeboki(a)gmail.com
Distribution: ---
Created attachment 69678
--> https://bugs.winehq.org/attachment.cgi?id=69678
A log from lutris when the error happens
After logging into League of Legends, the client is stuck in a state of
infinite loading.
--
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.