http://bugs.winehq.org/show_bug.cgi?id=24514
Summary: LVM_SUBITEMHITTEST fails on Chinese and Japanese
Versions of XP
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austin.lund(a)gmail.com
In the test_hittest function for the listview test the following test fails for
the Chinese and Japanese versions on the test bot:
/* subitem returned with -1 item too */
x = pos.x + 150;
y = -10;
test_lvm_subitemhittest(hwnd, x, y, -1, 1, LVHT_NOWHERE, FALSE, FALSE, FALSE);
The failures read:
listview.c:3056: Test failed: Expected -1 retval, got -2
listview.c:3056: Test failed: Expected -1 item, got -2
listview.c:3056: Test failed: Expected flags 0x1, got 0x4
This basically says that the message returned -2 (undocumented ?) and set the
flags to LVHT_ONITEMLABEL.
Is y = -10 relative to the control client area or the parent window? How can
you be on the item label in either case? Should the above values be added as
successes to this test?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=27117
Summary: Quake III Arena demo installer spawns Wine File when
setting up Start menu items
Product: Wine
Version: 1.3.19
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tjwt(a)hush.ai
The demo is downloadable from
ftp://ftp.idsoftware.com/idstuff/quake3/win32/Q3ADemo.exe . During a default
installation in Wine, it creates ten files in C:\users\Public\Start Menu\ and
ten Wine File windows appear. No Windows Explorer windows open when installing
under Windows XP. I see the problem with Wine 1.3.18 and 1.3.19 (I did not try
earlier versions).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=33092
Bug #: 33092
Summary: Melodyne Studio demo crashes on startup
Product: Wine
Version: 1.4.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jules.bernable(a)laposte.net
Classification: Unclassified
Created attachment 43757
--> http://bugs.winehq.org/attachment.cgi?id=43757
wine backtrace
Could the same issue as #16650, however this is happening with wine 1.4.1 on
debian wheezy.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=50375
Bug ID: 50375
Summary: Celemony Melodyne 3 demo: application starts, but
suddenly stops responding to user actions, without any
errors
Product: Wine
Version: 6.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: suenish.salkimbaev(a)gmail.com
Distribution: ---
The application starts at the beginning without any errors, but does not
respond to any user actions.
--
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=58167
Bug ID: 58167
Summary: Pegasus Mail immediately restores window
Product: Wine
Version: 10.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)jonass.user.lysator.liu.se
Distribution: ---
After upgrading from 10.5 to 10.6 I can't minimize Pegasus Mail. When I click
minimize the window only flashes, seems like it minimizes but immediately
restores to open window with the same size as before.
No error messages in console.
git bisect suggests it may be related to commit
6b04bdf25796c9c76815588bf7bdc36ff44b9e13
OS: XUbuntu 24.04.2 LTS
NVIDIA Driver Version: 535.183.01
Using X11 (not Wayland)
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58193
Bug ID: 58193
Summary: Dragon Quest X Online fails to play livestream video
Product: Wine
Version: 10.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: achurch+wine(a)achurch.org
Distribution: ---
Created attachment 78496
--> http://bugs.winehq.org/attachment.cgi?id=78496
+mfplat,+dmo debug log
Dragon Quest X Online has a feature in which official livestreams can be viewed
in-game, but this fails under Wine when using the FFmpeg backend for Media
Foundation:
0530:trace:mfplat:source_resolver_CreateObjectFromByteStream 43D86A20,
43E8B754, L"C:/users/dqx/Documents/My Games/DRAGON QUEST
X/work/Bin/hls00000470010000058d.aac", 0x1, 00000000, 4573FDE4, 4573FDE8.
[...]
0530:trace:mfplat:async_result_SetStatus 43DCBC58, 0xc00d36c4.
(This file is an AAC audio chunk downloaded from the livestream. An MPEG-TS
video chunk with a similar filename and .ts extension is also stored but never
referenced, presumably because this initialization fails.)
The MF_E_UNSUPPORTED_BYTESTREAM_TYPE error appears to be returned by
mfplat/main.c:resolver_get_bytestream_handler(); this iterates through registry
keys for specific supported MIME types and extensions and then falls back to
resolver_create_gstreamer_handler(), which naturally fails because Wine is
built without GStreamer support. I can get past that error by adding a
registry key for .aac (HKCU/Software/Microsoft/Windows Media
Foundation/ByteStreamHandlers/.aac) with values copied from an existing
bytestream handler (I arbitrarily chose the .mp3 handler), and FFmpeg (via
winedmo) appears to correctly recognize the bytestream as AAC audio, but the
game's livestream playback thread immediately crashes with a divide-by-zero
exception (the game itself is still playable, but an error dialog pops up and
no stream is played).
Unfortunately, this issue may be difficult to track down because the relevant
code is only executed when an official livestream is actually running, and the
game does not have any "test" functionality for the livestream viewer.
--
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=58190
Bug ID: 58190
Summary: secur32:ntlm tests fail on Windows 11 24H2
Product: Wine
Version: 10.6
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: secur32
Assignee: wine-bugs(a)winehq.org
Reporter: bshanks(a)codeweavers.com
secur32:ntlm has one failure on Windows 11 24H2:
ntlm.c:348: Running the client the second time.
ntlm.c:956: Test failed: Running the client returned SEC_E_NO_CREDENTIALS, more
tests will fail.
ntlm.c:973: Tests skipped: Authentication failed, skipping test.
This is likely because of the removal of NTLMv1 from Windows 11 24H2 and Server
2025: https://learn.microsoft.com/en-us/windows/whats-new/removed-features
--
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=58192
Bug ID: 58192
Summary: dozen Vulkan driver fails due to missing/minimal
dxcore implementation (both MacOS and Linux)..
Product: Wine
Version: 10.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rtfss1(a)gmail.com
Distribution: ---
Hi,
in brief my request expand dxcore.dll support in Wine to a minimal dxcore
implementation that allows to run Dozen via Wine.. on both Macos and Linux..
on MacOS for Dozen+D3DMetal testing on Linux for Dozen+VKD3D testing..
details:
just wanting to test Dozen (Mesa Vulkan over D3D12 library) in Macos with
Crossover 25.0 (bottle setup to using D3DMetal 2.1 as D3D12 driver)..
for that I just download:
mesa3d-25.0.4-release-msvc.7z
from:
https://github.com/pal1000/mesa-dist-win/releases/tag/25.0.4
and then adjust ICD loader to find the vulkan_dzn.dll driver and run
vulkaninfo.exe..
I check I have all enviroment correctly as also extract lavapipe Vulkan driver
from that package and it works correctly with vulkaninfo.exe
using dozen on Crossover 25.0 (setup to use D3DMetal 2.1) I see bug that is not
related to D3DMetal D3D12 driver:
MESA: error: Failed to retrieve D3D12GetInterface
MESA: error: Failed to create DXCore adapter factory
so would fail also on Linux..
seeing Dozen source code I find in:
https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/microsoft/vulkan/d…
fails in dzn_enumerate_physical_devices_dxcore function.. code below..
that is using dxcore and fails with DXCoreCreateAdapterFactory being a stub
currently:
https://github.com/wine-mirror/wine/blob/master/dlls/dxcore/main.c
perhaps it's better to use as reference if wanting to implement dxcore Wine
support checking it works with a minimal sample provided "Minimal DXCore
application":
https://github.com/MicrosoftDocs/win32/blob/docs/desktop-src/dxcore/dxcore-…
dxcore microsoft docs:
https://learn.microsoft.com/en-us/windows/win32/dxcore/dxcore-enum-adapters
dxcore seems the "future" to enumerate adapters on Windows due to enumeration
possibly NPU devices also..
dozen source code where it fails:
util_dl_library *dxcore = util_dl_open(UTIL_DL_PREFIX "dxcore" UTIL_DL_EXT);
if (!dxcore) {
mesa_loge("Failed to load DXCore\n");
return VK_ERROR_INITIALIZATION_FAILED;
}
using PFNDXCoreCreateAdapterFactory = HRESULT (APIENTRY*)(REFIID, void **);
PFNDXCoreCreateAdapterFactory create_func =
(PFNDXCoreCreateAdapterFactory)util_dl_get_proc_address(dxcore,
"DXCoreCreateAdapterFactory");
if (!create_func) {
mesa_loge("Failed to load DXCoreCreateAdapterFactory\n");
return VK_ERROR_INITIALIZATION_FAILED;
}
IDXCoreAdapterFactory *factory;
if (FAILED(create_func(IID_PPV_ARGS(&factory)))) {
mesa_loge("Failed to create DXCore adapter factory\n");
return VK_ERROR_INITIALIZATION_FAILED;
}
--
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=42898
Bug ID: 42898
Summary: Listbox keyboard input
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: janwinehq(a)gmail.com
Distribution: ---
A listbox widget in Wine does not react the same way to keyboard input as in
Windows.
In Windows, you can type the first characters of a word and the cursor will
jump to the first item matching *all* the characters you typed. This allows you
to drill down quickly to the item you want.
In Wine, when you start typing it only considers the *last* character you typed
when looking for a match. On listboxes where you have lots of items starting
with the same character, this can make it problematic to drill down to the
correct item.
This may be better explained with a simple example. Suppose you have a listbox
with the following items, sorted alphabetically:
* AMBER
* BLUE
* BROWN
* GREEN
* ORANGE
* RED
* YELLOW
Windows behavior:
* if you type "B", it will drill down to "BLUE"
* if you type "BR", it will drill down to "BROWN"
* if you type "BRO", it will drill down to "BROWN"
Wine behavior:
* if you type "B", it will drill down to "BLUE"
* if you type "BR", it will drill down to "RED"
* if you type "BRO", it will drill down to "ORANGE"
--
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.