https://bugs.winehq.org/show_bug.cgi?id=2155
Christian Costa <titan.costa(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |titan.costa(a)gmail.com
--- Comment #31 from Christian Costa <titan.costa(a)gmail.com> ---
It seems the staging patchset has been upstreamed with
f20c72d83c8a8de638b95e1ebc9e54fce1e4b162.
--
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=57940
Bug ID: 57940
Summary: ntoskrnl.exe tests can trigger BSOD
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: amorozov(a)etersoft.ru
Created attachment 78188
--> https://bugs.winehq.org/attachment.cgi?id=78188
MEMORY.DMP analysis with WinDbg
I have seen BSOD on Windows 10 Pro 1709 x64, Windows 10 Pro 22H2, Windows 11
Home 21H2 x64.
On Windows 10 testsigning was enabled with
bcdedit -set testsigning on
Windows 11 was loaded without driver signature check.
--
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=58040
Bug ID: 58040
Summary: Compiling with clang 20.1.1 results in a lot of
mp67e96999/shell32-00000000.spec-00000000.s:32085:10:
error: Could not find incbin file
'dlls/shell32/shell32.res' errors when shell32.dll is
built.
Product: Wine
Version: 10.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)ivanchev.net
Distribution: ---
Created attachment 78296
--> https://bugs.winehq.org/attachment.cgi?id=78296
Excerpt from the build log
Using latest clang (20.1.1) to compile Wine results in weird error about
missing incbin file dlls/shell32/shell32.res when shell32.dll is being built
although shell32.res is successfully compiled before hand (see log excerpt).
--
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=58044
Bug ID: 58044
Summary: Realm Grinder freezes/crashes after a very long run
Product: Wine
Version: 10.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
Created attachment 78299
--> https://bugs.winehq.org/attachment.cgi?id=78299
output of two failed runs
This I strongly suspect is a regression, yet I can't really pin down the time
when this started happening. The problem happens with little to no human
interaction, yet the timeframes make it unreasonable to actively reproduce.
I suspect it started around 10.0 release, but with a -/+ 2 months margin (so
close to useless).
Anyway, what's the problem ?
If Realm Grinder is run for long enough (but 'long enough' here is measured in
*days*), it tends to eventually either freeze with a completely black window or
crash with an X server error.
The attachment has output of two such runs, second chunk is when it just froze,
the first when it crashed.
'fixme:d3d:swapchain_blit_gdi Using GDI present.' at the end of both seems to
be the moment the problem triggers.
It seems to be some kind of a resource leak, but it doesn't affect any other
apps running besides it, not even those run by wine.
No user action is really required to trigger this - I've seen it freeze after a
desktop switch, I've seen it crash when the window was just displayed, but not
really interacted with.
(Realm Grinder here is still at v4.2.27.0, though I'll likely update it shortly
for Easter event)
--
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=58034
Bug ID: 58034
Summary: TUBERANK JEET AI SOFTWARE NOT OPENING NEW BUG
Product: Wine
Version: 10.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: pocomal112(a)codverts.com
Distribution: ---
Created attachment 78292
--> https://bugs.winehq.org/attachment.cgi?id=78292
TUBERANK JEET AI SOFTWARE NOT OPENING NEW BUG
TUBERANK JEET AI SOFTWARE NOT OPENING NEW BUG
HERE IS THE LINK FOR THE SOFTWARE
https://tuberankjeet.com/freeversion
--
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=58043
Bug ID: 58043
Summary: DVDFab won't run on Wine 10.3 because it thinks that
there is a debugger running when there isn't
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 78297
--> https://bugs.winehq.org/attachment.cgi?id=78297
Screenshot
To reproduce, run `wine dvdfab13_online_13037.exe`. When installation is
complete, an error dialog appears that says "A debugger has been found running
in your system. Please, unload it from memory and restart your program."
This error did not happen before Wine 10.3. `git bisect` says:
dc718fd33b23a6104a0fa2e971a358662bf766af is the first bad commit
commit dc718fd33b23a6104a0fa2e971a358662bf766af (HEAD)
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Tue Feb 25 13:45:33 2025 +0100
Commit: Alexandre Julliard <julliard(a)winehq.org>
CommitDate: Tue Feb 25 23:01:11 2025 +0100
ntdll: Add some missing Zw exports.
dlls/ntdll/ntdll.spec | 23 ++++++++++++++++-------
1 file changed, 16 insertions(+), 7 deletions(-)
$ sha256sum dvdfab13_online_13037.exe
9260ecbad0ddeeca876ff7adb35d26cffc7fb40399c814ae6fd369d2d7708791
--
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=57545
Bug ID: 57545
Summary: EdbMails crashes on start with assertion failure on
"index < meta->heap_strings.size"
Product: Wine
Version: 10.0-rc2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Run `wine EdbMailsSetup.exe`
2. Run `wine 'C:\Program Files (x86)\EdbMails\edbmails.exe'`
The program does not start. The following errors are printed to the terminal:
02e8:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
Unknown heap type: #Schema
* Assertion at /var/hostdir/mono/mono/metadata/metadata.c:1154, condition
`index < meta->heap_strings.size' not met, function:mono_metadata_string_heap,
index = 0x4a990000 size = 0x00000001 meta=C:\Program Files
(x86)\EdbMails\edbmails.exe
$ sha256sum EdbMailsSetup.exe
78a42bf203d626080b7033dce2375cf7871259720528b7260f5dac52eab606d7
--
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=52002
Bug ID: 52002
Summary: comctl32:datetime fails in the Arabic (Egypt) locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:datetime fails in the Arabic (Egypt) locale:
datetime.c:212: Test failed: String mismatch ("12 hh" vs "hh 12")
datetime.c:798: Test failed: Expected 08/11/2021, got 2021/11/08
https://test.winehq.org/data/patterns.html#comctl32:datetime
This failure happens as soon as one sets UserDefaultLCID to 0xc01 (Settings ->
Time & Language -> Regional format -> Arabic (Egypt)).
Note: the reason it worked up to 2021-10-21 is because before then
UserDefaultLCID was incorrectly set to English in the w10pro64-ar VM. Then I
upgraded the VM to Windows 21H1 and in the process I recreated the Arabic
snapshot which got the intended locale this time. The current settings are:
SystemDefaultLCID 0c01
UserDefaultLCID 0c01
ThreadLocale 0c01
SystemPreferredUILanguages 0409
UserDefaultUILanguage 0401
ThreadUILanguage 0401
--
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=58042
Bug ID: 58042
Summary: PlayOnline Viewer: Window content only updates in the
primary screen.
Product: Wine
Version: 10.4
Hardware: x86-64
URL: https://web.archive.org/web/20210810150839/http://www.
playonline.com/ff11eu/download/media/install_win.html
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chiitoo(a)gentoo.org
Distribution: Gentoo
PlayOnline Viewer window content does not get updated unless it is running in
the primary X11 screen.
If the window is moved to a secondary screen, the application keeps running and
accepting input, but the image will be frozen to what it was when moved there,
or it will remain black if minimised and restored.
As a sidey-note, when running via winewayland, the window content is black
regardless of the screen it is running in [1].
Thank you!
1. https://bugs.winehq.org/show_bug.cgi?id=58041
--
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=58041
Bug ID: 58041
Summary: PlayOnline Viewer: Black screen when running via
winewayland.
Product: Wine
Version: 10.4
Hardware: x86-64
URL: https://web.archive.org/web/20210810150839/http://www.
playonline.com/ff11eu/download/media/install_win.html
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: chiitoo(a)gentoo.org
Distribution: Gentoo
Running PlayOnline Viewer via Wayland by setting DISPLAY="" in an LXQt/Wayfire
session results into a completely black window.
The application still works, just no content can be seen.
Final Fantasy XI Online, which PlayOnline Viewer is used to launch, seems to
work OK so far, when navigated to blindly.
Did not spot anything different in the default terminal output yet.
Running via XWayland works as expected, though that also means a black screen
in displays other than the primary screen, or rather the content just isn't
updated in the other screens.
Without XWayland, the result is the same regardless of the display.
Thank you!
--
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.