https://bugs.winehq.org/show_bug.cgi?id=55252
Bug ID: 55252
Summary: tightvnc viewer crashes on connection
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mylazid(a)gmail.com
Distribution: ---
Created attachment 74859
--> https://bugs.winehq.org/attachment.cgi?id=74859
error occurs when connections
tightvnc viewer crashes on connection
--
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=42360
Bug ID: 42360
Summary: Terragen 4 fails to start
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: eneeen(a)gmail.com
Distribution: ---
Created attachment 57137
--> https://bugs.winehq.org/attachment.cgi?id=57137
tgd4_backlog
Using Kubuntu 16.10
I've attached backlog.
--
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=51406
Bug ID: 51406
Summary: riched32:editor fails in Wine on right-to-left locales
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
riched32:editor fails in Wine when run in the Arabic (EG and MA) and Hebrew
(IL) locales:
https://test.winehq.org/data/patterns.html#riched32:editor
editor.c:122: Test failed: [2] EM_GETLINECOUNT returned 2, expected 2
editor.c:122: Test failed: [5] EM_GETLINECOUNT returned 3, expected 3
editor.c:122: Test failed: [6] EM_GETLINECOUNT returned 4, expected 4
editor.c:122: Test failed: [14] EM_GETLINECOUNT returned 3, expected 3
editor.c:122: Test failed: [15] EM_GETLINECOUNT returned 4, expected 4
editor.c:455: Test failed: 1: expected_bytes_written=2
editor.c:455: Test failed: 2: expected_bytes_written=4
editor.c:455: Test failed: 3: expected_bytes_written=5
editor.c:455: Test failed: 4: expected_bytes_written=3
editor.c:876: Test failed: EM_POSFROMCHAR reports x=1, expected 8
editor.c:902: Test failed: EM_POSFROMCHAR reports x=1, expected 8
In both cases the failure are the same. Also the test succeeds in the
corresponding locales on Windows 2004.
The test on line 122 fails because Wine returns the same values in RTL locales
as in LTR ones.
--
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=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=55160
Bug ID: 55160
Summary: Loading Bay / Harry Potter Magic Awakened: Unable to
install
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: worble+winehq(a)worble.xyz
Distribution: ---
Created attachment 74728
--> https://bugs.winehq.org/attachment.cgi?id=74728
Wine Logs
After clicking "Install", a generic "Installation Failed" page appears.
Attached logs suggest '01b0:fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm
L"RC4" not supported' could be the culprit?
The installer can be downloaded from this page:
https://www.harrypottermagicawakened.com/global/
Direct link:
https://api.loadingbay.com/app/v1/download_client/windows/mkt-hpma-official…
SHASUM: 3f3ff1a8d118975dfb03ce7cceab99ba499b13c0
Using wine-8.11 (Staging)
--
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=55124
Bug ID: 55124
Summary: Can't run Flutter SDK (cmd.exe doesn't support
redirecting stderr for a block)
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
`wine flutter.bat` goes into an infinite loop that prints this message over and
over:
Can't recognize '2 (' as an internal or external command, or batch script.
It's coming from these lines in internal/shared.bat:
2>NUL (
REM "3" is now stderr because of "2>NUL".
CALL :subroutine %* 2>&3 9> "%cache_dir%\flutter.bat.lock" || GOTO
acquire_lock
)
Wine's cmd.exe does support redirecting stdout for a block of code, for
example:
>NUL (
COPY flutter.bat flutter2.bat
)
But it does not support redirecting stderr in the same way.
--
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=55097
Bug ID: 55097
Summary: cmd.exe does not handle PATH with leading or
sequential semicolons
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: loothelion(a)nvidia.com
Distribution: ---
Created attachment 74657
--> https://bugs.winehq.org/attachment.cgi?id=74657
Repro program for PATH separator bug
Wine's cmd.exe doesn't properly handle PATH values with:
- A leading semicolon
- Two sequential semicolons
Windows handles this fine, as shown in the attached test program. Simply
extract and then run test.bat from cmd.exe
Output looks like such in wine:
```
Z:\home\loothelion\repos\wine-path-bug>test.bat
"Expecting failure (no print)"
Can't recognize 'test.bat' as an internal or external command, or batch script.
"Expecting SUCCESS"
"PATH=Z:\home\loothelion\repos\wine-path-bug/a"
SUCCESS
"Expecting SUCCESS (exposes WINE bug)"
"PATH=;Z:\home\loothelion\repos\wine-path-bug/a"
"Expecting SUCCESS"
"PATH=D:/;Z:\home\loothelion\repos\wine-path-bug/a"
SUCCESS
"Expecting SUCCESS (exposes WINE bug)"
"PATH=D:/;;Z:\home\loothelion\repos\wine-path-bug/a"
```
I have a fix for this that I plan to send for review shortly, as well as a new
test case to protect against regressions.
--
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=54978
Bug ID: 54978
Summary: vbscript fails to compile Sub when End Sub on same
line
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: francisdb(a)gmail.com
Distribution: ---
Sub Sw35_UnHit()Controller.Switch(35)=0: End Sub
has to be changed to
Sub Sw35_UnHit()
Controller.Switch(35)=0
End Sub
to work
see also Bug 53873
--
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.