https://bugs.winehq.org/show_bug.cgi?id=51285
Bug ID: 51285
Summary: The bmpcoreimage test in user32:cursoricon fails on
most Windows versions
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
The bmpcoreimage test in user32:cursoricon fails on most Windows versions.
The failure is either:
cursoricon.c:1217: Test failed: BMP (coreinfo): IMAGE_BITMAP failed.
or cursoricon.c:1162: Test failed: BMP (coreinfo): Pixel is 0x00000000
https://test.winehq.org/data/patterns.html#user32:cursoricon
A given Windows version can have different results.
The result seems to depend on the user32.dll version, as if Microsoft issued a
security fix that changed the handling of this bitmap and progressively
converged on the "Pixel is 0" result. Here's the detailed result per platform
and user32 version:
vista 6.0.6002.18005 ok
vistau64 6.0.6002.18005 ok
w2008 6.0.6002.19714 ok
w7pro64 6.1.7601.23594 ok
w7u 6.1.7601.24546 Pixel is 0x00000000
w8 6.3.9600.17031 ok
w864 6.3.9600.17031 ok
w8.gtx 6.3.9600.17415 ok
w8.rx 6.3.9600.19920 Pixel is 0x00000000
w1507 10.0.10240.16384 ok
w1507.gtx 10.0.10240.16384 ok
w1507.rx 10.0.10240.16384 ok
w1607 10.0.14393.0 ok
w1709.rx 10.0.16299.15 ok
w1709 10.0.16299.125 ok
w1709.gtx 10.0.16299.125 ok
w1809.gtx 10.0.17763.168 ok
w1809.rx 10.0.17763.168 ok
w1809 10.0.17763.1339 IMAGE_BITMAP failed
w1909.gtx 10.0.18362.719 IMAGE_BITMAP failed
w1909.rx 10.0.18362.719 IMAGE_BITMAP failed
w1909 10.0.18362.1110 Pixel is 0x00000000
w2004 10.0.19041.388 IMAGE_BITMAP failed
w2009.fg 10.0.19041.610 Pixel is 0x00000000
w2009 10.0.19041.685 Pixel is 0x00000000
w2009.gtx 10.0.19041.906 Pixel is 0x00000000
w2009.rx 10.0.19041.906 Pixel is 0x00000000
Note that w1507, w1607 and w1709 may be missing updates (but installing them
without upgrading to the next Windows version would be hard), which may be why
they don't fail.
So either this test should be removed, or it should be changed to expect 'pixel
== 0' and allow for broken results (which does not fit with the way
test_LoadImageFile() is currently implemented).
We may also want to update Wine's BITMAP_Load() implementation to match the
current Windows behavior.
For reference this test bitmap was introduced in the commit below:
commit 0dfedd50c38356c8049aef48e69b630204de0f79
Author: Wolfram Sang <wolfram(a)the-dreams.de>
AuthorDate: Sat Jun 5 05:57:19 2010 +0200
user32: No sanity checks for BITMAPCOREINFO in BITMAP_Load.
--
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=50893
Bug ID: 50893
Summary: Wine cannot see home directory
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehome(a)dispostable.com
Distribution: ---
Created attachment 69703
--> https://bugs.winehq.org/attachment.cgi?id=69703
output of "wine explorer ~/"
Steps to reproduce: With a fresh install and prefix (WINEARCH 32 or 64 bit),
run "wine explorer" and navigate to /home.
Expected behaviour: A list of all folders in /home appears.
Actual behaviour: One user home folder, /home/user1, is missing from the list.
Other user home folders, e.g. /home/user2, are shown as expected.
Permissions for /home/user1 and /home/user2 are the same. The absence of
/home/user1 persists, regardless of whether wine is run under user1 or user2.
Running "wine explorer ~/" gives
0144:err:explorer:make_explorer_window Failed to create PIDL for
L"Z:\\home\\user1".
This also affects all file dialogs in other software and opening a file in
/home/user1 with an associated wine executable.
--
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=25759
Summary: crash when running game "Polda" and moving their
(game) window
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: prescott66(a)gmail.com
Created an attachment (id=32832)
--> (http://bugs.winehq.org/attachment.cgi?id=32832)
crash log game "Polda"
this bug is about one older game named "Polda".it is edited to works OK on
Windows XP and it works on real Windows XP.
But when i run it on Linux (Fedora 14, 32-bit, wine ver:1.3.11) game hangs and
when i try to move window, game crashes. log is attached.
i can upload somewhere that game if you will, thats no problem because its not
big game(cca 100MB).
--
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=53516
Bug ID: 53516
Summary: user32:input failed due to unexpected WM_TIMECHANGE
message
Product: Wine
Version: unspecified
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 failed due to unexpected WM_TIMECHANGE message:
input.c:4525: Test failed: SendInput triggered unexpected message 0x1e
https://test.winehq.org/data/patterns.html#user32:input
This happened on 2022-08-05 in the w10pro64-fr-64 test configuration.
But user32:msg has also received such an unexpected message on 2022-08-02 on
w10pro64-pt-BR-64 (see bug 53273).
It appears this message is sent by Windows when an application modifies the
system time. If the application is another test then it should make sure all
such messages have been sent before continuing.
But it is quite possible that this message is sent when Windows resynchronizes
with some internet time server in which case this message could arrive in any
test at any time.
--
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=51477
Bug ID: 51477
Summary: user32:input test_Input_blackbox() gets unexpected
00&41(A) keystate changes
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
test_Input_blackbox() gets unexpected 00&41(A) keystate changes:
https://test.winehq.org/data/patterns.html#user32:input
input.c:757: Test failed: 0 (a4/0): 00 from 00 -> 81 unexpected
input.c:757: Test failed: 0 (a4/0): 41 from 00 -> 01 unexpected
* This exclusively happens for the first sendinput_test entry which is supposed
to simulate pressing the left Alt key (VK_LMENU == 0xa1).
* I do not know what the 00 virtual key code corresponds to. According to the
failure message this key is getting pressed down and toggled.
* The 41 virtual key code should be the 'A' key but that's not a toggle key
(unlike, e.g., Caps Lock) so the low order bit should be meaningless. So it's
strange that it changed from off to toggled.
* These failures happen on the following machines:
(41 corresponds to 100% reproducible, some machines may have fewer than 41
runs)
17 2008_newtb-w2008s64-32
1 2008_newtb-w2008s64-64
5 win7_newtb-w7u-2qxl
7 win81_cw-rx460-32
4 win1507_cw-gtx560-1507-32
5 win1507_cw-rx460-1507-32
1 win1709_cw-rx460-1709-64
39 win2009_cw-gtx560-2009-32
39 win2009_cw-gtx560-2009-64
41 win2009_cw-rx460-2009-32
41 win2009_cw-rx460-2009-64
--
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=17414
Summary: user32/dde test crashes if +heap enabled
Product: Wine
Version: 1.1.15
Platform: PC
URL: http://test.winehq.org/data/6a1537c4b5037be5253c33021fda
3a02430533f7/wine_xp_ae-ub-810-heap/riched32:editor.html
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: enhancement
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=19484)
--> (http://bugs.winehq.org/attachment.cgi?id=19484)
backtrace in 1.1.15
wine: Unhandled page fault on read access to 0x00130000 at address 0x6045971b
(thread 0009), starting debugger...
...
=>0 0x6045971b CompareStringW+0x13b(lcid=1033, style=0, str1=0x130000, len1=0,
str2=0x6074c780, len2=-1)
[/home/austin/wine-git/dlls/kernel32/../../include/wine/unicode.h:216] in
kernel32 (0x0032f848)
1 0x6045bed4 lstrcmpW+0x64(str1=<register EDI not in topmost frame>,
str2=<register ESI not in topmost frame>)
[/home/austin/wine-git/dlls/kernel32/locale.c:2834] in kernel32 (0x0032f878)
2 0x60681d7a dde_server_wndprocW+0x3da(hwnd=0xe0028, msg=1000, wparam=458798,
lparam=<register EDI not in topmost frame>)
[/home/austin/wine-git/dlls/user32/tests/dde.c:1215] in user32_test
(0x0032f8b8)
3 0x6082337a WINPROC_wrapper+0x1a() in user32 (0x0032f8e8)
4 0x608237ca call_window_proc+0x6a(hwnd=<register EDI not in topmost frame>,
msg=<register ESI not in topmost frame>, wp=458798, lp=1204994,
result=0x32f998, arg=0x606819a0)
[/home/austin/wine-git/dlls/user32/winproc.c:458] in user32 (0x0032f928)
5 0x60828af7 WINPROC_call_window+0xf7(hwnd=<register EDI not in topmost
frame>, msg=1000, wParam=458798, lParam=1204994, result=0x32f998, unicode=1,
mapping=WMCHAR_MAP_DISPATCHMESSAGE)
[/home/austin/wine-git/dlls/user32/winproc.c:2218] in user32 (0x0032f968)
6 0x607e7ee6 DispatchMessageW+0x96(msg=<register EDI not in topmost frame>)
[/home/austin/wine-git/dlls/user32/message.c:3122] in user32 (0x0032f9a8)
7 0x607a4037 WDML_SyncWaitTransactionReply+0xe7(hConv=0x1254b8,
dwTimeout=<register ESI not in topmost frame>, pXAct=0x125508, ack=0x32fb84)
[/home/austin/wine-git/dlls/user32/dde_client.c:1069] in user32 (0x0032fa08)
8 0x607a4b21 DdeClientTransaction+0x651(pData="test dde command", cbData=17,
hConv=0x1254b8, hszItem=0xdead, wFmt=48879, wType=16464, dwTimeout=1000,
pdwResult=0x32fb84) [/home/austin/wine-git/dlls/user32/dde_client.c:1225] in
user32 (0x0032fa68)
9 0x60686158 test_dde_aw_transaction+0x638()
[/home/austin/wine-git/dlls/user32/tests/dde.c:1374] in user32_test
(0x0032fb98)
...
216 while (*s) s++;
Attached is the backtrace...I've stripped out +heap, so the output is readable,
but easily reproducible.
--
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=51473
Bug ID: 51473
Summary: user32:input Some SendInput() set LastError to
ERROR_ACCESS_DENIED on cw-rx460 19.11.3
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
More specifically some cw-rx460 machines have the following failures:
https://test.winehq.org/data/patterns.html#user32:input
input.c:4410: Test failed: SendInput returned 1, error 0x5
input.c:4413: Test failed: SendInput returned 16, error 0x5
input.c:4464: Test failed: SendInput returned 16, error 0x5
These fail not because SendInput() failed, but because it modified LastError,
setting it to ERROR_ACCESS_DENIED.
This only happens on the following machines which have in common that they use
the 19.11.3 Radeon driver which is the latest version that will run on these
Windows versions:
win1507_cw-rx460-1507-32
win1507_cw-rx460-1507-64
win81_cw-rx460-32
win81_cw-rx460-64
The failure is systematic on these machines.
--
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=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.