https://bugs.winehq.org/show_bug.cgi?id=50751
Bug ID: 50751
Summary: notepad++ Find in files progressbar window doesn't
stay on top
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: forinih564(a)nic58.com
Distribution: ---
Created attachment 69535
--> https://bugs.winehq.org/attachment.cgi?id=69535
Log
Tested with wine 6.3 & notepad++ version 7.9.3 (32-bit)
When using the Find in files feature in notepadd++ & starting the search ,
notepad++ locks the interaction with all windows except for the find in files
progressbar window that contains a cancel button , if you switch to other app
then return back to notepad++ using its taskbar icon , only the locked windows
appear which you can't interact with unless the search finishes or accessing
the progressbar window by alt+tab
it could be related to bug #26087 , but that bug is closed
--
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=54757
Bug ID: 54757
Summary: d3d11:d3d11 - test_resource_access() sometimes
triggers a wined3d assertion
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 - test_resource_access() sometimes triggers a wined3d assertion:
d3d11.c:15552: Test marked todo: Feature level 0xb100: Got hr 0 for WRITE.
Assertion failed: bo->b.map_ptr, file ../wine/dlls/wined3d/context_gl.c, line
3049
d3d11:d3d11:06e8 done (3) in 9s 15479B
See https://test.winehq.org/data/patterns.html#d3d11:d3d11
The assertion always happens after the same trace so it is likely caused by
this test_resource_access() line:
15552 check_resource_cpu_access(context, resource,
15553 texture_desc.Usage, texture_desc.BindFlags,
texture_desc.CPUAccessFlags);
15554 ID3D11Resource_Release(resource);
And the assertion happens in wined3d_context_gl_unmap_bo_address():
3049 assert(bo->b.map_ptr);
The oldest known instance happened on 2023-02-23 and there has been about one
further failure per week since, all in the pure 32-bit tests on the debian11
TestBot VM.
--
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=54754
Bug ID: 54754
Summary: zoom history meeting window 90% chance of not popping
up properly
Product: Wine
Version: 8.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: 399989567(a)qq.com
Distribution: ---
Created attachment 74250
--> https://bugs.winehq.org/attachment.cgi?id=74250
Image 1
The window circled by the red box in "Image 1" does not pop up properly.
Steps to reproduce:
1. Because this is a historical meeting window, you need to have joined a zoom
meeting in advance. zoom meetings can be applied for free on their website.
2. After joining the meeting and leaving the meeting, an arrow will appear
where you enter the meeting number, click the arrow to bring up the window and
trigger the bug.
Download zoom at: https://zoom.us/DOWNLOAD
Some of my research, when the problem pop-up window received the message
clientmessage, but the window style is 86000000, not the problem is 96000000, I
think this can be used as an entry point to fix the bug.
You can look at this function: handle_wm_protocols
--
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=50449
Bug ID: 50449
Summary: Program freezes if both keyboard and mouse is used at
the same time
Product: Wine
Version: 6.0-rc5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: g0re(a)null.net
Distribution: ---
Created attachment 69063
--> https://bugs.winehq.org/attachment.cgi?id=69063
console output from version 5.22
Zdaemon 1.10.15 - a DOOM source port
http://downloads.zdaemon.org/zdaemon11015_win32_bin.7z
If only keyboard is used, works ok
If only mouse is used, works ok
Program freezes if both keyboard and mouse is used at the same time.
Issue both in windowed and fullscreen mode.
Until version 5.14, works fine.
Occurs from wine version 5.15 to version 6.0-rc5 (tested every version between)
Can do a simple test with (need an IWAD):
$ wine zdaemon.exe -iwad DOOM2.WAD -skill 4 +map map01
--
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=50130
Bug ID: 50130
Summary: Outrun 2006 cannot choose anti aliasing levels more
than 2
Product: Wine
Version: 5.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jogamer1(a)protonmail.com
Distribution: ---
Created attachment 68622
--> https://bugs.winehq.org/attachment.cgi?id=68622
output log of config.exe
Install Outrun 2006 and run the Config.exe, under Video settings you can choose
anti aliasing settings up to 6 but in Wine only up to 2 is shown. If the anti
aliasing level is changed in outrun2006.ini the value will be blank in the anti
aliasing drop-down menu. Happens both on development and staging 5.21 and back
to Wine 5.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=45601
Bug ID: 45601
Summary: Wargaming Game Center doesn't start after installation
Product: Wine
Version: 3.13
Hardware: x86
URL: http://redirect.wargaming.net/WGC/Wargaming_Game_Cente
r_Install_TWA_EU.exe
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 62032
--> https://bugs.winehq.org/attachment.cgi?id=62032
wine log
When the program installed, it should start the program - but it does not.
"winetricks -q ie8" works around 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=54749
Bug ID: 54749
Summary: ddraw:dsurface sometimes times out on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:dsurface sometimes times out on Windows:
ddraw:dsurface start dlls/ddraw/tests/dsurface.c
ddraw:dsurface:1260 done (258) in 120s 0B
See https://test.winehq.org/data/patterns.html#ddraw:dsurface
There are 5 known instances in the past 8 months:
* 2022-09-01 on w1064-tsign-64
* 2022-12-09 on fgtb-w10pro64-rx550-64
* 2022-12-09 on w1064v21h2-64
* 2023-03-27 on w10pro64-ar-64
* 2023-03-27 on w10pro64-mx-MX-64
Again the dates look similar to the other ddrawmodes and dsurface issues (bug
54746 and bug 54747) but not identical. So while there is probably some common
factor making these failures more likely, it's not a simple trigger.
--
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=54747
Bug ID: 54747
Summary: ddraw:dsurface sometimes gets E_OUTOFMEMORY on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:dsurface sometimes gets E_OUTOFMEMORY on Windows. However this does not
always happen in the same place:
* 2022-08-31 in test_ddsd() on w1064-tsign-64:
dsurface.c:2232: Test failed: Got hr 0x8007000e.
* 2022-10-14 in BackBufferAttachmentFlipTest() on w1064-tsign-32:
dsurface.c:1710: Test failed: Got hr 0x8007000e.
dsurface.c:1758: Test failed: Attaching a back buffer to another back buffer
returned 0x80070057
dsurface.c:1776: this is the last test seen before the exception
14a8:dsurface: unhandled exception c0000005 at 00553E4A
* 2022-12-09 in PaletteTest(), BackBufferAttachmentFlipTest() and test_ddsd()
on w1064-tsign-64:
dsurface.c:1372: Test failed: Got hr 0x8007000e.
dsurface.c:1375: Tests skipped: failed to create surface
dsurface.c:1691: Test failed: Got hr 0x8007000e.
dsurface.c:2232: Test failed: Got hr 0x8007000e.
* 2023-01-24 in BackBufferAttachmentFlipTest() and zbufferbitdepth_test() on
w10pro64-fr-64:
dsurface.c:1691: Test failed: Got hr 0x8007000e.
dsurface.c:2130: Test failed: Got hr 0x8007000e.
dsurface.c:2130: this is the last test seen before the exception
1f40:dsurface: unhandled exception c0000005 at 0000000000522CD1
* 2023-03-27 in test_ddsd() on w10pro64-ru-64
dsurface.c:2232: Test failed: Got hr 0x8007000e.
See https://test.winehq.org/data/patterns.html#ddraw:dsurface
Where 0x8007000e == E_OUTOFMEMORY
Notes:
* There are really 5 places where this happens.
* It always happens after a IDirectDraw_CreateSurface() call, except for the
test_ddsd() (line 2232) cases where it follows a IDirectDrawSurface7_Lock()
call.
* The failure dates look somewhat similar to the ddraw:ddrawmodes E_OUTOFMEMORY
failures but not exactly and the VMs mostly don't match. So the ddrawmodes
failures are not the cause of the dsurface ones. But there may be some common
factor making these failures more likely.
--
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=54746
Bug ID: 54746
Summary: ddraw:ddrawmodes - testcooperativelevels_normal()
sometimes gets E_OUTOFMEMORY on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:ddrawmodes - testcooperativelevels_normal() sometimes gets E_OUTOFMEMORY
on Windows:
ddrawmodes.c:723: Test failed: Got hr 0x8007000e.
ddrawmodes.c:724: Test failed: Returned NULL surface pointer
See https://test.winehq.org/data/patterns.html#ddraw:ddrawmodes
Where 0x8007000e == E_OUTOFMEMORY
This failure always happens in this call:
716 /* Try creating a double buffered primary in fullscreen + exclusive +
normal mode */
717 rc = IDirectDraw_CreateSurface(lpDD, &surfacedesc, &surface, NULL);
...
723 ok(rc == DD_OK, "Got hr %#lx.\n", rc);
There is one instance on 2022-09-01 but this started happening about twice per
month on 2022-12-09.
--
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.