https://bugs.winehq.org/show_bug.cgi?id=52117
Bug ID: 52117
Summary: All windows are blacked out when running 16 bit
cardfile.exe
Product: Wine-staging
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 71147
--> https://bugs.winehq.org/attachment.cgi?id=71147
top window is unreadable due to being filled with black.
All windows are blacked out when running 16 bit cardfile.exe. The program runs
but text in any visible window is blacked out.
The cardfile.exe and its help can be downloaded from this link
https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=…
--
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=55280
Bug ID: 55280
Summary: Wine should come with MSVBVM60.DLL
Product: Wine
Version: 8.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ry1tg3+RY1TN1(a)rokejulianlockhart.anonaddy.com
Distribution: ---
When I run VB6-based software with Wine, it states that the DLL is unavailable.
--
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=52576
Bug ID: 52576
Summary: Cardfile windows are grayed out
Product: Wine-staging
Version: 7.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 71902
--> https://bugs.winehq.org/attachment.cgi?id=71902
selected window grayed out
Program: cardfile.exe (16bit originally released in windows 3.1)
Symptom: selected windows are grayed out making any text unreadable.
History: this bug has been present in wine & wine-staging since release 6.6
The bug was not present in wine/wine-staging 6.5
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44823
Bug ID: 44823
Summary: Steam doesn't close on exit. Will continue running in
background.
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vblanton(a)gmail.com
Distribution: ---
Created attachment 60857
--> https://bugs.winehq.org/attachment.cgi?id=60857
Steam system information and version
Running the latest Steam client, I find that Steam doesn't actually close
entirely after I exit normally with Steam>Exit. I have to open System Monitor
and kill all steam and wine related processes. I can't open steam again until I
do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in
the background until I do so.
--
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=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.