https://bugs.winehq.org/show_bug.cgi?id=51471
Bug ID: 51471
Summary: user32:input receives unexpected WM_SYSTIMER messages
in test_SendInput()
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:input sometimes receives unexpected WM_SYSTIMER messages in
test_SendInput():
https://test.winehq.org/data/patterns.html#user32:input
input.c:4477: Test failed: SendInput triggered unexpected message 0x118
Notes:
* This is random: there is no machine where it happens systematically; and
different machines don't necessarily have the issue on the same day.
* This does not happen on a specific Windows version though not all seem to be
impacted either. Specifically this issue has been seen on the following
machines:
win7_newtb-w7u-2qxl
win7_newtb-w7u-de
win7_newtb-w7u-el
win7_newtb-w7u-es
win7_newtb-w7u-pt-PT
2008_newtb-w2008s64
win81_cw-rx460
win1507_cw-gtx560-1507
win1507_cw-rx460-1507
win1909_cw-gtx560-1909
win2009_cw-gtx560-2009
win2009_cw-rx460-2009
* Maybe the following article can be useful:
https://devblogs.microsoft.com/oldnewthing/20160624-00/?p=93745
--
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=42784
Bug ID: 42784
Summary: Lost Planet dx10 demo black screen after starting new
game
Product: Wine
Version: 2.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andras(a)sth.sze.hu
Distribution: ---
Created attachment 57802
--> https://bugs.winehq.org/attachment.cgi?id=57802
+d3d11, + d3d_shader
After starting new game or performance test in Lost Planet dx10 demo, it shows
only black screen. It tries to create a geometry shader and fails. As far as I
see, it want to use a vertex shader as geometry shader.
See log file.
--
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=50475
Bug ID: 50475
Summary: ENM (Externes Notenmodul / external mark module)
crashes on opening
Product: Wine
Version: 5.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sebastian.arnhold387(a)gmail.com
Distribution: ---
Created attachment 69111
--> https://bugs.winehq.org/attachment.cgi?id=69111
Terminal log
ENM is a teacher's tool for grading students, released by the government of the
state of North-Rhine Westphalia (NRW) in Germany.
Requirements for wine:
winetricks mdac28 msls31 riched30 vb6run winbind
Description of the bug:
When trying to install the latest version of ENM ("ENM-Setup 1.4.8.1 Stand
21.12.2020") downloaded from the official government website, the installer
works fine. When trying to open the installed executable, the program crashes
immediately with an "unhandled exception" error.
I tried to run it using both wine and wine-development package, trying both 64
bit and 32 bit prefix, on Ubuntu 20.04 amd64. Results are identical.
Terminal output log included.
Link to software (installer):
https://www.svws.nrw.de/system/files/zip_und_exe/2020-12/ENM-Setup_1_4_8_1.…
Link to WineHQ database entry (outdated and unmaintained):
https://appdb.winehq.org/objectManager.php?sClass=application&iId=9047
Additional problem solving analysis:
Older versions of the software definitely worked fine until June 2020, as e.g.
this blog entry proves (http://www.tohschneider.de/extnotmodlinux/). Suspected
a problem with ENM software itself, but when trying older version from before
that time, these versions that once worked fine now also throw an "unhandled
exception" error. This proves that something in wine must have changed.
Contacted developer of ENM software. Developer suspects a problem with the way
wine handles the ADO drivers. Other softwares from the government school
software suite show similar behaviour. Government institution sadly does not
support Linux, but is interested in getting ENM software to work again.
In the interest of free education, solution would be highly appreciated.
Thanks!
--
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=51474
Bug ID: 51474
Summary: user32:input SendInput() triggers an unexpected
message 0x60 on Windows 10 1709
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 70310
--> https://bugs.winehq.org/attachment.cgi?id=70310
Trace all window handles and 0x60 message
SendInput() triggers an unexpected message 0x60 in test_SendInput() on Windows
10 1709:
https://test.winehq.org/data/patterns.html#user32:input
input.c:4451: Test failed: SendInput triggered unexpected message 0x60
* This failure is almost but not 100% systematic on Windows 10 1709: it
happened 202 times out of 205.
* I could not find any documentation on this 0x60 message.
* But the attached patch shows that:
- The message is sent to a window belonging to our process.
- The test did not directly create that window.
- The window class is UserAdapterWindowClass which seems to be related to IME
despite these machines running in a regular en_US locale.
input.c:4404: 4404 hwnd=0000000000020274
input.c:4474: Test failed: SendInput triggered unexpected message 0x60
input.c:4480: hwnd=0000000000020274 pid=7016 tid=7012 now=64359
input.c:4481: hwnd=0000000000040048 message=0060 wParam=1 lParam=0 time=64359
pt=(512,384)
input.c:4485: wnd: pid=7016 tid=7012 class=22 L"UserAdapterWindowClass" text=0
L""
--
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=50785
Bug ID: 50785
Summary: wineserver corruption with :
msg:get_server_queue_handle Cannot get server thread
queue
Product: Wine
Version: 6.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lanthruster(a)gmail.com
Distribution: ---
Created attachment 69593
--> https://bugs.winehq.org/attachment.cgi?id=69593
wineserver explorer.exe flood
A very frustrating bug:
Install Wine 6.0
Install Adobe Acrobat DC (any version) or Adobe Acrobat XI (any version)
Now run acrord32.exe
acrord32.exe will launch and work BUT
1. you won't be able to run any more wine applications but existing will
continue to work
2. when a wine application is launched the process lists is flooded with
explorer.exe /desktop (hundreds of them are spawned leading to resource
exhaustion)
3. when you kill them with killall explorere.exe - the currently running wine
applications will continue to run normally as well as acrord32.exe
4. you can still launch wineapp from another wine app but not with wine or
winecosole because of 2
5. when acrord32.exe is closed wine won't return to normal it will still 2.
6. after wineserver -k everything is back to normal
the console is flooded with
01fc:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
0218:err:msg:get_server_queue_handle Cannot get server thread queue
021c:err:msg:get_server_queue_handle Cannot get server thread queue
0220:err:msg:get_server_queue_handle Cannot get server thread queue
0220:err:win:GetDesktopWindow failed to create desktop window
0220:err:msg:get_server_queue_handle Cannot get server thread queue
0220:err:win:GetDesktopWindow failed to create desktop window
0220:err:msg:get_server_queue_handle Cannot get server thread queue
0220:err:win:GetDesktopWindow failed to create desktop window
0220:err:ole:apartment_createwindowifneeded CreateWindow failed with error 1411
0584:err:module:LdrInitializeThunk Initializing dlls for
L"C:\\windows\\system32\\explorer.exe" failed, status c000013a
(see attachment)
--
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=42999
Bug ID: 42999
Summary: 3D Engine in NosTale not reacts for mouse on Mac
Product: Wine-staging
Version: 2.7
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: artrixdev(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Created attachment 58140
--> https://bugs.winehq.org/attachment.cgi?id=58140
Simple logs from cmd and graphic bug in game.
If try change camera position nothing to do and if I clicked on items in
equipment it's changing to "question mark" graphic.
--
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=38235
Bug ID: 38235
Summary: Blindwrite 7 does not detect any CD/DVD drive.
Product: Wine
Version: 1.7.38
Hardware: x86
URL: http://de.vso-software.fr/products/Blindwrite/blindwri
te.php
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mountmgr.sys
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)vr-web.de
Distribution: Debian
Created attachment 51041
--> https://bugs.winehq.org/attachment.cgi?id=51041
Save user mode accessible device in HKLM\SYSTEM\MountedDevices "\DosDevices\X:"
Having a CD in the drive and that one mounted it is accessible through e.g.
cmd.
But Blindwrite (7.0.0.0) does not show any drive in its user interface.
When looking into a "WINEDEBUG=+reg,+file,+debugstr" an access to
HKLM\SYSTEM\MountedDevices
appears.
There is for any device an entry e.g. "\DosDevices\E:".
This entry holds in my case the mount point of the CD as ASCII.
Blindwrite tries now to access the drive by opening this interpreted as
unicode string, which fails.
trace:file:CreateFileW
L"\6d2f\6465\6169\622f\7265\686e\7261\2f64\4642\3931\3234\325f1" GENERIC_READ
GENERIC_WRITE FILE_SHARE_READ FILE_SHARE_WRITE creation 3 attributes 0x0
...
trace:file:CreateFileW returning 0xffffffff
...
trace:file:DeviceIoControl
(0xffffffff,4d014,0x33f3a4,80,0x33f3a4,80,0x33f3f8,(nil))
...
warn:debugstr:OutputDebugStringA "IOCTL_CDROM_GET_INQUIRY_DATA - Ung\xfcltiges
Handle.\r\n Error 0x00000006 - Ung\xfcltiges Handle.\r\n"
Blindwrite even tries to access this invalid file handle and silently fails.
-----------------
Changing HKLM\SYSTEM\MountedDevices "\DosDevices\E:" to an unicode
representation of "\\.\E:" makes Blindwrite happy and the drive shows up,
and successfully create an image.
Attached is a patch that tries to do this automatically for "DosDevices"
with a drive letter.
(But I am not sure about any side effects or if it could already be
sent to wine-patches.)
--
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=48078
Bug ID: 48078
Summary: Astro Avenger 2 fails to run with
seh:setup_exception_record stack overflow
Product: Wine
Version: 4.19
Hardware: x86-64
URL: https://astro-avenger.en.softonic.com/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: iodreamify(a)gmail.com
Distribution: Ubuntu
Created attachment 65628
--> https://bugs.winehq.org/attachment.cgi?id=65628
winedebug warn+all log
Astro Avenger 2 manages to launch but clicking "Run" in the launcher makes the
game freeze forever with a
"002a:err:seh:setup_exception_record stack overflow 816 bytes in thread 002a
eip
00ac1926 esp 00231000 stack 0x230000-0x231000-0x330000" error.
Tried it both in 64bit and 32bit prefixes in windows 7, XP, 2000 and 98 modes
and also disabling csmt.I've added a winedebug=warn+all log below.
A demo 60 min trial can be found at the link above.
I've also done a +relay log but i'm not sure if it's relevant. 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.