https://bugs.winehq.org/show_bug.cgi?id=55222
Bug ID: 55222
Summary: Virtual Desktop does not work correctly under Wine
8.11
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tst1(a)mixbox.pl
Distribution: ---
I use dual monitor (2 monitors).
Under Wine, I use Virtual Desktop, which covers up almost all of these two
monitors.
After updating Wine to 8.11 (under Manjaro Linux), regardless of the running
application, Wine desktop runs on only one monitor (in full screen mode).
You can then neither resize nor move the Wine desktop to the second monitor.
Downgrading Wine to my previous version: 8.8 is a workaround solution solving
the issue.
--
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=52826
Bug ID: 52826
Summary: All windows are grayed out. text is unreadable
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
Distribution: ---
Created attachment 72213
--> https://bugs.winehq.org/attachment.cgi?id=72213
grayed out windows sample
cardfile.exe windows are grayed out. No text is readable. Bug has been present
since wine-6.6.
link to cardfile.exe and its help file on my google drive
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=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.
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.
https://bugs.winehq.org/show_bug.cgi?id=49772
Bug ID: 49772
Summary: Memory safety issues in widl
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: kolan_n(a)mail.ru
Distribution: ---
I have tried to compile some type libraries missing in MinGW-w64 and Wine and
ReactOS SDKs too (more precisely, sapiddk.idl) into headers from the files in
Windows SDK (used Windows 10 SDK).
MinGW-w64 widl has crashed without producing any output, just left some files
with garbled filenames (looks like a zero terminator got missing in a C
string).
So I have built wine widl. It has also crashed, but at least produced some
meaningful 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=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=55101
Bug ID: 55101
Summary: DesignDoll Declaring An Error After Loading All
Component In Splash Screen
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zeroredgrave(a)gmail.com
Distribution: ---
Created attachment 74668
--> https://bugs.winehq.org/attachment.cgi?id=74668
After Loading Screen
DesignDoll Doesn't Load in Weird Way and I dunno what kind of Error is this.
--
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=55053
Bug ID: 55053
Summary: Prometheus exporter for Windows needs
DISPATCH_PROPERTYGET support in object_Invoke
Product: Wine
Version: 8.10
Hardware: x86-64
URL: https://github.com/prometheus-community/windows_export
er/releases/download/v0.22.0/windows_exporter-0.22.0-a
md64.exe
OS: Linux
Status: NEW
Keywords: download, patch, source
Severity: normal
Priority: P2
Component: wmi&wbemprox
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
Distribution: ---
Created attachment 74615
--> https://bugs.winehq.org/attachment.cgi?id=74615
hack
To test this:
1) Run windows_exporter-0.22.0-amd64.exe
2) Go to http://localhost:9182/ in your browser
3) Press the 'Metrics' button
4) An error page is shown
When pressing the 'Metrics' button, this fixme is spammed:
0188:fixme:wbemdisp:object_Invoke flags 0x2 not supported
This stems from the fact that wbemdisp:object_Invoke doesn't support
DISPATCH_PROPERTYGET on its own. The attached hack "fixes" the issue and
instead of the error page, you get a page with metrics.
Source of the program can be found here:
https://github.com/prometheus-community/windows_exporter
--
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=9378
Summary: CM: Shock Force 'Could not initialize graphics display'
Product: Wine
Version: 0.9.43.
Platform: PC
URL: http://www.battlefront.com/products/cmsf/downloads.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mailing_list(a)orange.nl
After starting Combat Mission: Shock Force Demo it stops with the message:
'Could not initialize graphics display. REQUIRED 1024x768, 32-bit
color'.
The terminal output doesn't provide any clues:
wine 'CM Shock Force DEMO.exe'
ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0
ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file
or directory
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55042
Bug ID: 55042
Summary: scrrun: dictionary get_num_hash generating the same
hash for 2175 and 6259
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: scrrun
Assignee: wine-bugs(a)winehq.org
Reporter: jsm174(a)gmail.com
Distribution: ---
In vbscript, I had some code like this:
Set FlexDMDDict = CreateObject("Scripting.Dictionary")
FlexDMDDict.Add 0, "VPX.DMD_Space"
FlexDMDDict.Add 63, "VPX.DMD_O"
FlexDMDDict.Add 2175,"VPX.DMD_8"
.
.
FlexDMDDict.Add 6259, "VPX.DMD_R"
I was getting VBSE_ACTION_NOT_SUPPORTED on the last line, so I put a printf in
the `get_num_hash`:
static DWORD get_num_hash(FLOAT num)
{
DWORD x = (*((DWORD*)&num)) % DICT_HASH_MOD;
printf("get_num_hash: num=%f, hash=%u\n", num, x);
return (*((DWORD*)&num)) % DICT_HASH_MOD;
}
I'm getting:
get_num_hash: num=2175.000000, hash=977
get_num_hash: num=6259.000000, hash=977
FWIW, I'm using this on macos, so DWORD is set to:
typedef unsigned int DWORD, *PDWORD, *LPDWORD;
--
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=54380
Bug ID: 54380
Summary: WINE debugger shows up at the start of every program.
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: tch(a)protonmail.com
Distribution: ---
When i run a program with WINE, the debugger window shows up and says
"Unhandled exception: unimplemented function ntoskrnl.exe.Ke386QueryIoAccessMap
called in 32-bit code (0x[address]).", then displays some other messages, then
disappears.
Then the program runs normally, but this did not happen before i upgraded to
WINE 8.0.
--
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=53092
Bug ID: 53092
Summary: Animated Puzzles crashes on start
Product: Wine
Version: 7.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user16
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
16bit application Animated Puzzles crashes on start. This bug report tracks
commit
https://github.com/otya128/winevdm/commit/9868db40f249595fcffc57050ce4a29ae…
in otvdm. The same fix in Wine makes the application start and run correctly.
--
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.