https://bugs.winehq.org/show_bug.cgi?id=55461
Bug ID: 55461
Summary: directmanipulation:manipulation sometimes times out on
Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
directmanipulation:manipulation sometimes times out on Windows 10:
directmanipulation:manipulation:2190 done (258) in 120s 0B
See https://test.winehq.org/data/patterns.html#directmanipulation:manipulation
The test normally runs in under 1 second which means the time out is caused by
a deadlock. However this is pretty rare and has only happened twice in the past
8 months:
* 2023-04-06 win21H1_newtb-w10pro64-hi-u8-64 (followed out-of-memory failures
in previous tests)
* 2023-08-18 win21H1_newtb-w10pro64-de-64 (followed dinput:joystick8 failures)
--
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=55477
Bug ID: 55477
Summary: shell32:autocomplete - test_prefix_filtering()
sometimes fails on Windows because the AutoComplete
DropDown is visible
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:autocomplete - test_prefix_filtering() sometimes fails on Windows
because the AutoComplete DropDown is visible:
autocomplete.c:671: Test failed: AutoComplete DropDown visible
See https://test.winehq.org/data/patterns.html#shell32:autocomplete
This is pretty rare and did not happen for 4 months but has started happening
again:
* 2023-01-16 win21H1_newtb-w10pro64-ar-64
* 2023-01-19 win22H2_newtb-w1064-tsign-64
* 2023-02-14 win1507_newtb-w1064v1507-64
* 2023-07-03 win21H1_newtb-w10pro64-he-64
* 2023-08-22 win7_newtb-w7u-2qxl
--
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=55492
Bug ID: 55492
Summary: ntdll:threadpool - test_RtlRegisterWait() sometimes
fails in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:threadpool - test_RtlRegisterWait() sometimes fails in Wine. There are
three variants which look like they are probably related:
(1)
threadpool.c:354: Test failed: expected info.userdata = 1, got 0
threadpool.c:370: Test failed: expected info.userdata = 1, got 0
threadpool.c:371: Test failed: expected info.threadid != 0, got 0
threadpool.c:373: Test failed: OpenThread failed with 87
threadpool.c:376: Test failed: QueueUserAPC failed with 6
(2)
threadpool.c:290: Test failed: expected info.userdata = 0, got 65536
threadpool.c:294: Test failed: expected info.userdata = 1, got 65536
threadpool.c:296: Test failed: WaitForSingleObject returned 0
(3)
threadpool.c:292: Test failed: expected info.userdata = 1, got 65536
threadpool.c:294: Test failed: WaitForSingleObject returned 0
See https://test.winehq.org/data/patterns.html#ntdll:threadpool
(1) This is the most common variant and it happens in both the GitLab and other
non-TestBot VMs:
* 2023-06-30 linux_fgtb-debian11-x86-64
* 2023-06-18 MR!3094
* 2023-06-06 linux_rbernon-vulkan-win64
* 2023-05-29 linux_fg-deb64-wow32
* 2023-05-24 MR!2628
* 2023-01-31 linux_fg-deb64-wow64
* 2023-01-11 MR!1940
(2) Only happened once and on the GitLab CI.
* 2023-04-28 MR!2682
(3) Only happened on the GitLab CI.
* 2023-08-25 linux_gitlab-debian-32
* 2023-06-02 MR!2954
--
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=55579
Bug ID: 55579
Summary: kernel32:loader - test_ExitProcess() sometimes fails
on the 32-bit w8 VM
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:loader - test_ExitProcess() sometimes fails on the 32-bit w8 VM:
loader.c:3529: Test failed: GetThreadContext should fail
loader.c:3530: Test failed: expected ERROR_INVALID_PARAMETER, got -559038737
loader.c:3538: Test failed: SetThreadContext should fail
loader.c:3539: Test failed: expected ERROR_ACCESS_DENIED, got -559038737
See https://test.winehq.org/data/patterns.html#kernel32:loader
This started on 2023-09-04 and happens in about 50% of the WineTest runs and is
most likely caused by the commit below:
commit d64200805b1848f782c8a4ce1fdbcb9292fffe51
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Thu Aug 31 18:08:50 2023 +0200
kernel32/tests: Remove some workarounds for old Windows versions.
--
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=49868
Bug ID: 49868
Summary: Hedgewars 1.0.0 crashes when a game against the
computer is started
Product: Wine
Version: 5.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ---
Created attachment 68209
--> https://bugs.winehq.org/attachment.cgi?id=68209
The console messages
Hedgewars crashes when the following steps are taken:
1) remove .wine directory
2) run wineboot
3) run the Hedgewars installer, accept the defaults. This will start Hedgewards
at the end of the installer
4) Press "Play a game on a single computer"
5) Press "Play a quick game against the computer with random settings"
6) Sometimes, the game now shows the error "The program hedgewars.exe has
encountered a serious problem and needs to close"
7) if the game does not crash, press escape and Y, and repeat step 5
My versions:
$ wine --version
wine-5.17 (Staging)
$ uname -a
Linux cedric-p4 5.8.10-arch1-1 #1 SMP PREEMPT Thu, 17 Sep 2020 18:01:06 +0000
x86_64 GNU/Linux
--
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=55585
Bug ID: 55585
Summary: Redraw problem at Notepad++
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: temp2004(a)freenet.de
Distribution: ---
Created attachment 75114
--> https://bugs.winehq.org/attachment.cgi?id=75114
Movie showing influence of left mouse button clicks at the degenerated document
list
There seems to be a problem affecting the Doc Switcher dialog of Notepad++:
When running Notepad++ for a long period inside Wine, file names are displayed
at wrong positions or appear multiple, sometimes only half lines are displayed.
Resizing Notepad++ main windows sometimes temporary corrects the complete file
list, but not always.
Clicking at a file name at his list always leads to a correct redraw of this
one file name
(watch attached movie).
Only the Doc Switcher dialog is affected: all other Notepad++ sub windows seem
to be correctly redrawn.
Seen at any releases of SuSE and Ubuntu during the last years. Also at
different computer hardware.
Seems to affect any Notepad++ releases (current I use 8.1.2).
At MS Windows this problem does not occur.
Steps:
Enable "Document List Panel=Show" at Menu Settings/Preferences/General.
Open and close some text files over a long period .
Right after start of Notepad++ everything seems to be OK.
The redraw problem needs some time (hours?) to appear.
Possibly computers Stand-By mode also has an influence.
If the problem appears, it will not go away until Notepad++ is restarted.
--
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=54530
Bug ID: 54530
Summary: Unable to find an entry point named
'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: uiautomationcore
Assignee: wine-bugs(a)winehq.org
Reporter: hunt3rgz(a)protonmail.com
Distribution: ---
Created attachment 74074
--> https://bugs.winehq.org/attachment.cgi?id=74074
Wine log
I runned a .NET 5.0 application written with Windows Forms
https://github.com/X-Hax/sa_tools
When i close the 'create gradient' window, it gives me this error
System.EntryPointNotFoundException: Unable to find an entry point named
'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'.
at Interop.UiaCore.UiaDisconnectProvider(IRawElementProviderSimple provider)
at System.Windows.Forms.Control.ReleaseUiaProvider(IntPtr handle)
at System.Windows.Forms.Control.WmDestroy(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr
wparam, IntPtr lparam)
--
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=55556
Bug ID: 55556
Summary: Contradicting support for Intel Arc GPUs while not
supporting DXVK in AppDB and/or Bugzilla
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linards.liepins(a)gmail.com
Distribution: ---
As per
https://www.tomshardware.com/news/intel-gpu-driver-optimizations-leverage-v…,
the Intel Arc drivers are already using/bundling-ion DXVK to handle DX9 APIs.
That means that if you support Intel Arc GPUs as GPU option, you automatically
support DXVK as well ( because Wine uses kernel driver as-is, correct? ). That
meanst that not accepting buzilla bugs with DXVK is
wrong/offernsive/unfriendly.
If that isa not true, then PLEASE fix the AppDB and Bugzilla to have
conditional handling of Intel GPU and non-Intel-GPU options and educate the
maintainers/reviewers accordingly.
--
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.