https://bugs.winehq.org/show_bug.cgi?id=52071
Bug ID: 52071
Summary: mshtml:script fails in externalDisp_InvokeEx() on
Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mshtml:script fails in externalDisp_InvokeEx() on all Windows versions from 7
to 10/21H1.
script.c:640: L"/index.html?11:doc_mode: Testing compatibility mode 11"
script.c:624: Test failed: L"/index.html?11:elem_attr: removed ondblclick
string = function ondblclick(event)\n{\nstring\n}"
script.c:3417: Running documentmode.js script in edge;123 mode...
script.c:640: L"/index.html?11:doc_mode: Testing compatibility mode 11"
script.c:624: Test failed: L"/index.html?11:elem_attr: removed ondblclick
string = function ondblclick(event)\n{\nstring\n}"
https://test.winehq.org/data/patterns.html#mshtml:script
A bisect shows that this failure appeared with the commit below:
commit 6b2c20c6a1aa046c5f0317221b52609bcaa11295
Author: Gabriel Ivăncescu <gabrielopcode(a)gmail.com>
Date: Tue Nov 16 19:58:16 2021 +0200
mshtml: Clear the string dprop associated with the builtin attribute when
removing it.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com>
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Note that this failure was reported by the TestBot:
https://www.winehq.org/pipermail/wine-devel/2021-November/200830.htmlhttps://source.winehq.org/patches/data/219693.testbot
--
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=49174
Bug ID: 49174
Summary: Duplicate checking iter->parent in mshtml/htmlwindow.c
Product: Wine
Version: 5.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal54(a)gmail.com
Distribution: ---
Should be probably `iter && iter->parent`
https://github.com/wine-mirror/wine/blob/59987bc9ecdd0dbafd768a95c21a14884b…
--
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=49099
Bug ID: 49099
Summary: MIDI events sent to all devices at once
Product: Wine
Version: 5.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
Assignee: wine-bugs(a)winehq.org
Reporter: jpm(a)it-he.org
Distribution: ---
I am using an old version of Cakewalk SONAR to control a large number of
synthesizers. These are connected via an ESI M8Uex MIDI interface, which
appears to ALSA as 16 MIDI outputs and outputs over a single USB connection
("ESI M8U eX - ESI M8U eX MIDI 1", "ESI M8U eX - ESI M8U eX MIDI 2").
In WINE 4.x this has been working fine, but a recent Ubuntu upgrade has bumped
WINE to 5.5, and now SONAR is sending the same MIDI commands to all 16 ports on
the ESI device instead of just e.g. port 2.
For example, if you play the organ part in isolation, it should be sending
these notes to the Hammond XM-1 module on port 4 of the ESI device. But it is
also sending these to the drum machine on port 6, the Triton on port 1 and so
on.
It does not appear to be sending the MIDI data to the Roland UM-ONE interface
also attached the system, however.
As a workaround I have reverted to an old version of winealsa.drv.so from 2017
which I happened to have lying around from some earlier experiment. This has
made the problem go away.
I can try building WINE myself to find the point at which the bug was
introduced, but looking at the recent changes in git I'd be inclined to suspect
this commit:
https://github.com/wine-mirror/wine/commit/3d57cc2863f2f9a5ace40d29317b3ff4…
...since it appears to be using a much less fine-grained approach to sending
MIDI data to the devices.
It is quite likely that it works fine for the case of a USB synthesizer where
one instrument is on one port, but for something like a 4x4 MIDI interface
there appears to be a regression.
Thanks,
Joseph P Morris
--
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=46841
Bug ID: 46841
Summary: JASC Paint Shop Pro 8 Crash
Product: Wine
Version: 4.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: robcashwalker(a)gmail.com
Distribution: ---
Created attachment 63879
--> https://bugs.winehq.org/attachment.cgi?id=63879
back trace of fault for Paint Shop Pro 8
Used to work great with earlier version of Wine on Linux Mint 17. I don't
recall which version of Wine, but I remember installing it from the ubuntu
repository, not from WineHQ.
Never really gets into the program. Crashes after splash screen, but has built
the main window. Guessing right about the time it would destroy the splash
screen.
Happens in both stable release and development.
Had the same issue with PSP v9, gave up, and then I just came across the
install media for v8 and decided to try it, as I had been using v8 previously.
--
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=52042
Bug ID: 52042
Summary: Ketarin crash in WINE 6.21 THREAD transition from
RUNNING to DONE_BLOCKING
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jim_henderson(a)sil.org
Distribution: ---
Created attachment 71052
--> https://bugs.winehq.org/attachment.cgi?id=71052
log of output from the shell that ran Ketarin over WINE.
Ketarin app (latest vn, 1.8.11) over WINE crashed with logging output as in the
attachment.
Running on Lubuntu 20.04.3, 64-bit.
This windows program runs on Windows without crashing, but I'm having trouble
getting it to work properly on WINE 6.21.
Hoping some generous person has time to look at this and make a suggestion.
Jim
--
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=51872
Bug ID: 51872
Summary: Logos Bible Software 9 (.Net 4.8 app)
System.AccessViolationException regression
Product: Wine
Version: 6.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johnpgoodman(a)gmail.com
Distribution: ---
Created attachment 70791
--> https://bugs.winehq.org/attachment.cgi?id=70791
terminal output from crash after long execution period
>From 6.18 onwards I noticed that at seemingly random moments Logos will crash.
It has occasionally happened within a few moments of starting but also when
idle for a day or 2. In the past I had the app running for a month with no
crashes.
--
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=51805
Bug ID: 51805
Summary: Tropico 2: mouse cursor is black
Product: Wine
Version: 6.11
Hardware: x86-64
URL: https://archive.org/details/tropico2betademo
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: zzhang(a)codeweavers.com
Regression SHA1: d171d1116764260f4ae272c69b54e5dfd13c6835
Distribution: ---
The mouse pointer is showing up black instead of the animated cursor used by
the game. Can be observed right off the main menu in the demo.
Regression testing resulted
d171d1116764260f4ae272c69b54e5dfd13c6835 is the first bad commit
commit d171d1116764260f4ae272c69b54e5dfd13c6835
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Mon May 31 16:12:44 2021 +0800
gdi32: Return correct color depth for display DCs in GetDeviceCaps().
I could revert the patch on 6.17 and that fixed the issue.
Wine-6.18
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.74
--
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=48084
Bug ID: 48084
Summary: Crouzet soft & Virtual Display - Application crash
when 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: dokmad(a)yahoo.it
Distribution: ---
Created attachment 65634
--> https://bugs.winehq.org/attachment.cgi?id=65634
not able to describe
Crouzet soft & Virtual Display - Application crash when start.
https://www.crouzet.com/download-crouzet-soft --> Crouzet soft
--
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=51829
Bug ID: 51829
Summary: Roblox Player: Long freeze during loading
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: a0939712328(a)gmail.com
Regression SHA1: 7ef35b33936682c01f1c825b7d1b07567a691c12
Distribution: ---
Since a update, Roblox Player has been constantly freezing for more than 10
seconds before loading the game.
With help from git bisect, the faulty commit should be 7ef35b3 (ntdll:
Reimplement file system redirection using NT pathname comparisons.)
Steps to reproduce:
1. Install and set up Roblox using Grapejuice
(https://gitlab.com/brinkervii/grapejuice/-/wikis/home)
2. Open any experience through Roblox website
3. Look for long graphical freeze during game loading
Expected behavior:
The game freezes briefly and loads the game.
Actual behavior:
The game freezes for more than 10 seconds before loading the game, the graphics
are not updated in the process.
--
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=41239
Bug ID: 41239
Summary: FUEL Aborts on Start Due to Shader Validation Failing
Product: Wine
Version: 1.9.17
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: ben(a)xnode.org
Distribution: ---
Created attachment 55531
--> https://bugs.winehq.org/attachment.cgi?id=55531
Basic Terminal Output
FUEL seems to start fine and then spends a while (the first time it's opened)
generating shaders, but then just before it completes, it errors out claiming
that it couldn't validate the shaders and quits. Any time you open the game, it
jumps straight to the validation (and failure point) as it's already generated
the shaders.
--
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.