https://bugs.winehq.org/show_bug.cgi?id=52894
Bug ID: 52894
Summary: comdlg32:filedlg - test_arrange() fails in Wine in the
Japanese and Chinese locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
test_arrange() fails in Wine in the Japanese and Chinese locales:
filedlg.c:761: Test failed: Wrong height of dialog 301, expected 323
https://test.winehq.org/data/patterns.html#comdlg32:filedlg
The failure only happens in Wine and is 100% reproducible with the right
locale. So this looks very much like a bug in comdlg32.
--
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=52921
Bug ID: 52921
Summary: Resident Evil 5 DVD shows
E_INVALIDARG:XLiveInitialize(&xii)
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BOBBLOG(a)protonmail.com
Distribution: ---
Resident Evil 5 DVD shows E_INVALIDARG:XLiveInitialize(&xii) when i launch the
game.
This was tested with wine-7.7 in a clean wine prefix. I'll attach +d3d log.
--
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=52920
Bug ID: 52920
Summary: Resident Evil 5 DVD shows
E_INVALIDARG:XLiveInitialize(&xii)
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BOBBLOG(a)protonmail.com
Distribution: ---
Resident Evil 5 DVD shows E_INVALIDARG:XLiveInitialize(&xii) when i launch the
game.
This was tested with wine-7.7 in a clean wine prefix. I'll attach +d3d log.
--
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=52860
Bug ID: 52860
Summary: [Anno 2070]Crashes at launch (Assertion failed)
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Created attachment 72259
--> https://bugs.winehq.org/attachment.cgi?id=72259
Anno 2070 on Windows 11
Hello,
This game is a piece oh shit to update. If someone has the game :
1- Install UbisoftConnect & install the game
2- Cut Anno5 folder into a Windows partition.
3- Run Anno5.exe or Autopatcher.exe to update the game.
4- Retrieve the game folder.
5- Launch the game.
When you run the step 5, you need to have the Anno window to enable the game
(see attached screenshot). But with Wine 7.6, i have these lines in the output
console :
******
0100:fixme:d3d11:d3d11_device_context_SwapDeviceContextState D3D10 interface
emulation not fully implemented yet!
0100:fixme:d2d:d2d_device_context_PushLayer iface 06C93460, layer_parameters
0032F348, layer 06CBD938 stub!
0110:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
0100:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 07C114E8.
0100:fixme:d2d:d2d_text_renderer_DrawGlyphRun Ignoring options 0x2.
0100:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 07C114E8.
0100:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 07C114E8.
0100:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 07C114E8.
Assertion failed: iface->lpVtbl == (ID2D1DrawingStateBlockVtbl
*)&d2d_state_block_vtbl, file ../dlls/d2d1/state_block.c, line 189
******
--
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=52928
Bug ID: 52928
Summary: comctl32:toolbar - test_sizes() fails on Windows with
the UTF-8 codepage
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:toolbar's test_sizes() fails on Windows with the UTF-8 codepage:
toolbar.c:1594: Test failed: invalid rect (754,2)-(783,26) - expected
(754,2)-(784,26) - (button = 5, tbsize_numtests = 18)
toolbar.c:1597: Test failed: invalid rect (754,0)-(783,38) - expected
(754,0)-(784,38) - (button = 5, tbsize_numtests = 19)
toolbar.c:1626: Test failed: invalid rect (118,2)-(183,40) - expected
(118,2)-(184,40) - (button = 2, tbsize_numtests = 21)
toolbar.c:1634: Test failed: invalid rect (0,2)-(65,40) - expected
(0,2)-(66,40) - (button = 0, tbsize_numtests = 22)
toolbar.c:1661: Test failed: invalid rect (0,2)-(29,24) - expected
(0,2)-(30,24) - (button = 0, tbsize_numtests = 24)
https://test.winehq.org/data/patterns.html#comctl32:toolbar
This can be reproduced on w10pro64-hi-u8.
--
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=52927
Bug ID: 52927
Summary: comctl32:rebar - test_bandinfo() fails on Windows with
the UTF-8 codepage
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:rebar's test_bandinfo() fails on Windows with the UTF-8 codepage:
rebar.c:949: Test failed: expected 35 for 38 from line 990
rebar.c:949: Test failed: expected 40 for 43 from line 996
rebar.c:949: Test failed: expected 40 for 43 from line 1015
https://test.winehq.org/data/patterns.html#comctl32:rebar
Hindi + UTF-8 is the only locale where this test fails on Windows at this time.
In particular there is no failure on the standard Hindi locale (English system
locale) so this appears to be specific to UTF-8.
--
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=52926
Bug ID: 52926
Summary: usp10:usp10 The wgBlank and wgInvalid checks fail on
Windows with the UTF-8 codepage
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: usp10
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
usp10:usp10's wgBlank and wgInvalid checks in test_ScriptGetFontProperties()
fails on some truetype fonts with Hindi + UTF-8 codepage:
usp10.c:2634: Test failed: truetype font Symbol wgBlank 0000 gi[0] 0003
usp10.c:2645: Test failed: truetype font Symbol wgInvalid 0000 gi[0] 0003
usp10.c:2634: Test failed: truetype font Webdings wgBlank 0000 gi[0] 0003
usp10.c:2645: Test failed: truetype font Webdings wgInvalid 0000 gi[0] 0003
usp10.c:2634: Test failed: truetype font Wingdings wgBlank 0000 gi[0] 0003
usp10.c:2645: Test failed: truetype font Wingdings wgInvalid 0000 gi[0] 0003
https://test.winehq.org/data/patterns.html#usp10:usp10
See also bug 52925 which is a similar issue with wgBlank in a wider range of
locales, and for bitmap fonts instead of TrueType ones.
--
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=52896
Bug ID: 52896
Summary: gdi32:font has a test_GetCharABCWidths() failure on
all Windows 10 versions
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The following test_GetCharABCWidths() test fails on all Windows 10 versions:
ret = GetCharABCWidthsW(hdc, 'a', 'a', abc);
ok(!ret, "GetCharABCWidthsW should have failed\n");
font.c:1189: Test failed: GetCharABCWidthsW should have failed
https://test.winehq.org/data/patterns.html#gdi32:font
It was introduced in this pretty old commit:
commit 0dc765809c602cf62a87e28451e4eea81eeca0cb
Author: Hans Leidekker <hans(a)it.vu.nl>
AuthorDate: Sat Dec 8 22:55:01 2007 +0100
Commit: Alexandre Julliard <julliard(a)winehq.org>
CommitDate: Mon Dec 10 12:27:13 2007 +0100
gdi32: GetCharABCWidthsI does not require a scalable font.
--
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=45385
Bug ID: 45385
Summary: Wrong state of virtual keys after cycling windows.
Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every
key can be affected.
Product: Wine
Version: 3.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: johnfound(a)asm32.info
Distribution: ---
I noticed that the state of the keys sometimes sticks in pressed state.
This happens when cycling windows with some shortcut key combination.
For example if cycling with Alt+Tab, on pressing Alt, the program gets
WM_KEYDOWN and the state of the VK_MENU becomes pressed. But after cycling
windows, the program does not get WM_KEYUP because the window is not focused
and VK_MENU (and the respective VK_LMENU or VK_RMENU) remain in pressed state.
When cycling back to the program window, the window get focused only after
releasing Alt key, so it does not get this event as well.
If cycling windows with another shortcut key combination (for example
Alt+Shift+Tab - for backward cycling) both VK_MENU and VK_SHIFT keys stick.
In the same time, GetAsyncKeyState returns the proper state of the keys.
Note1: The problem is obviously in the wineserver code, because it handles the
key state tables for the different threads.
Note2: The effect happens only sometimes. It seems the code for proper
processing is already there, but some racing conditions have place.
Note3: There is some probability that the effect is in result of my application
code, but it never happens on real Windows, so I considered it a bug.
Note4: I tried to workaround this problem by reading the whole table by
GetAsyncKeyState and setting it then with SetKeyboardState on WM_ACTIVATE
message of the main window. This workaround actually works, but is too ugly
IMO.
The same trick on WM_ACTIVATEAPP does not work.
--
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=52737
Bug ID: 52737
Summary: winecfg not open
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jayjameshlw(a)gmail.com
Distribution: ---
archkubi@GnuChanOS ~> winecfg
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
MESA-INTEL: warning: Haswell Vulkan support is incomplete
0120:err:winediag:nodrv_CreateWindow Application tried to create a window, but
no driver could be loaded.
0120:err:winediag:nodrv_CreateWindow The explorer process failed to start.
--
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.