https://bugs.winehq.org/show_bug.cgi?id=50227
Bug ID: 50227
Summary: Logos 8 indexer crashes
Product: Wine
Version: 5.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galanlama(a)gmail.com
Distribution: ---
Created attachment 68735
--> https://bugs.winehq.org/attachment.cgi?id=68735
Backtrace produced by the wine debugger.
After opening Logos, indexer crashes after a few seconds. Same result by
running indexer.exe directly.
--
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=15505
Summary: STM_SETIMAGE does not handle bitmaps with alpha
correctly
Product: Wine
Version: 1.1.5
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
In XP, STM_SETIMAGE makes a copy of bitmaps with alpha, which allows
applications to delete the bitmaps they passed in. Many programmers expect this
as the default behavior, since they don't test on older Windows platforms.
Our STM_SETIMAGE implementation still follows the pre-XP behavior, which may
cause rendering problems for apps that use STM_SETIMAGE extensively.
I don't have a minimal test case just yet...
--
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=4123
temp82(a)luukku.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |temp82(a)luukku.com
--- Comment #14 from temp82(a)luukku.com ---
still valid wine 7.11.
--
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=53191
Bug ID: 53191
Summary: Dualsense controller with WINE is not on-par with
Steam Input
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gab.pulcio(a)gmail.com
Distribution: ---
Latest Steam beta update has the following enhancement in particular: improved
vibration on Dualsense controller with updated firmware, or something like
that.
Now, if I run a game with Steam, the Dualsense has the improved basic rumble
support, which as far as I know, it's implemented in the firmware but it's
improved.
Running games without Steam leaves me with the super aggressive vibration, it's
always on maximum, without any variation, a lot different that the one present
on Steam Input API or something like that.
Is there a way to work the problem? Something like: actually make everything
global and not local by relying on a bugged piece of software like Steam is?
--
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=53152
Bug ID: 53152
Summary: LarkSuite: Unhandled exception: page fault on read
access to 0x00000008 in 32-bit code
Product: Wine
Version: 7.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: simon(a)kingstonwireless.com
Distribution: ---
Created attachment 72585
--> https://bugs.winehq.org/attachment.cgi?id=72585
Backtrace
LarkSuite (Lark) is a Slack-like collaboration suite that incorporates email,
messaging, calendar, video calls, etc and is quite popular with Chinese
companies. The installer can be downloaded from
https://www.larksuite.com/download (Windows, macOS, iOS and Android versions
are available there).
The Lark installer appears to run fine but when the actual suite tries to load
up, a page fault error is given.
--
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=53255
Bug ID: 53255
Summary: d3d11:d3d11 sometimes crashes in test_generate_mips()
on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d11:d3d11 sometimes crashes in test_generate_mips() on Windows 7:
d3d11.c:30128: Tests skipped: Skipping test with DXGI_FORMAT_R8G8B8A8_UINT on
WARP.
d3d11.c:30128: Tests skipped: Skipping test with DXGI_FORMAT_R8G8B8A8_UINT on
WARP.
0d28:d3d11: unhandled exception c0000005 at 7FF9615D
https://test.winehq.org/data/patterns.html#d3d11:d3d11
Notice that a normal run has 4 of these skip messages instead of 2 which
suggests the crash happens in test_generate_mips().
There are two known instances of this crash:
* 2022-05-03 on w7u-2qxl
* 2022-06-22 on w7u-pt-PT
This makes this a pretty rare failure which can cause false positives.
--
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=53253
Bug ID: 53253
Summary: urlmon:url sometimes fails to create index.html on
Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:url sometimes fails to create index.html on Windows:
url.c:4073: bind to an object of not registered MIME type...
url.c:3774: Test failed: CreateFile failed
url.c:4078: file test (no callback)...
...
url.c:4184: emulated test reporting result in read...
url.c:4187: file test...
url.c:4190: file test (to file)...
url.c:4193: file test (to object)...
url.c:1534: Test failed: unexpected call QueryInterface_IWindowForBindingUI
url.c:1416: Test failed: unexpected call QueryService_IWindowForBindingUI
url.c:1342: Test failed: unexpected call GetWindow_ICodeInstall
url.c:1846: Test failed: binding failed: 80040154, expected 00000000
url.c:3524: Test failed: expected Obj_OnProgress_CLASSIDAVAILABLE
url.c:3533: Test failed: expected OnObjectAvailable
https://test.winehq.org/data/patterns.html#urlmon:url
These failures ahppen on Windows 7 to Windows 10 21H1 and are rare enough to
cause false positives.
--
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=53246
Bug ID: 53246
Summary: user32:sysparams - test_metrics_for_dpi() fails on
Windows 10 1709+
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:sysparams - test_metrics_for_dpi() fails on Windows 10 1709+:
sysparams.c:4175: testing GetSystemMetrics with your current desktop settings
sysparams.c:3002: Test failed: 28: wrong value 136 vs 258
sysparams.c:3002: Test failed: 34: wrong value 136 vs 258
...
sysparams.c:2430: testing SPI_{GET,SET}DESKWALLPAPER
sysparams.c:3002: Test failed: 28: wrong value 136 vs 258
sysparams.c:3002: Test failed: 34: wrong value 136 vs 258
https://test.winehq.org/data/patterns.html#user32:sysparams
Where:
* 28 == SPI_SETMENUDROPALIGNMENT
* 34 == SPI_SETICONTITLELOGFONT
test_metrics_for_dpi() is actually called from multiple places and
unfortunately the traces make it hard to know which calls actually fail.
The first pair of failures probably come from:
trace("testing GetSystemMetrics with your current desktop settings\n");
test_GetSystemMetrics( );
test_metrics_for_dpi( 192 );
The source of the second set of failures is less clear but presumably from the
other test_metrics_for_dpi( 192 ) call in test_dpi_aware(). Some
winetest_push_context() would be a good addition here.
--
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=53245
Bug ID: 53245
Summary: user32:sysparams: test_SPI_SETNONCLIENTMETRICS() fails
on Windows 10 1709+
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:sysparams: test_SPI_SETNONCLIENTMETRICS() fails on Windows 10 1709+:
sysparams.c:1488: testing SPI_{GET,SET}NONCLIENTMETRICS
sysparams.c:2823: Test failed: GetSystemMetrics(SM_CXSMICON): expected 16
actual 4
sysparams.c:2824: Test failed: GetSystemMetrics(SM_CYSMICON): expected 16
actual 4
https://test.winehq.org/data/patterns.html#user32:sysparams
The failure actually happens in test_GetSystemMetrics() which is called from
test_SPI_SETNONCLIENTMETRICS(). However there are 3 call locations and the
traces make it impossible to know which one fails which is another test bug in
its own right.
--
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=53244
Bug ID: 53244
Summary: user32:sysparams does not expect SPI_SETHANDEDNESS on
Windows 10 2004+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:sysparams does not expect SPI_SETHANDEDNESS on Windows 10 2004+.
Furthermore that message arrives at slightly different times in the tests
leading to different failure messages:
sysparams.c:1202: testing SPI_{GET,SET}DOUBLECLKWIDTH
sysparams.c:241: Test failed: too many changes counter=1 last change=29
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 29
sysparams.c:1236: testing SPI_{GET,SET}DOUBLECLKHEIGHT
sysparams.c:1271: testing SPI_{GET,SET}DOUBLECLICKTIME
sysparams.c:1326: testing SPI_{GET,SET}MOUSEBUTTONSWAP
sysparams.c:241: Test failed: too many changes counter=1 last change=33
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:347: Test failed: Wrong value in registry: Control Panel\Mouse
SwapMouseButtons '1' instead of '0'
sysparams.c:1341: Test failed: SM_SWAPBUTTON: got 1 instead of 0
sysparams.c:1345: Test failed: SwapMouseButton does not return previous state
(really 1)
sysparams.c:1358: testing SPI_GETFASTTASKSWITCH
sysparams.c:1376: testing SPI_{GET,SET}DRAGFULLWINDOWS
sysparams.c:241: Test failed: too many changes counter=1 last change=37
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 33 expected 37
or
sysparams.c:1236: testing SPI_{GET,SET}DOUBLECLKHEIGHT
sysparams.c:241: Test failed: too many changes counter=1 last change=30
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 30
sysparams.c:1271: testing SPI_{GET,SET}DOUBLECLICKTIME
sysparams.c:241: Test failed: too many changes counter=1 last change=32
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 32
sysparams.c:1326: testing SPI_{GET,SET}MOUSEBUTTONSWAP
sysparams.c:241: Test failed: too many changes counter=1 last change=33
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:347: Test failed: Wrong value in registry: Control Panel\Mouse
SwapMouseButtons '1' instead of '0'
sysparams.c:1341: Test failed: SM_SWAPBUTTON: got 1 instead of 0
sysparams.c:1345: Test failed: SwapMouseButton does not return previous state
(really 1)
sysparams.c:1358: testing SPI_GETFASTTASKSWITCH
sysparams.c:1376: testing SPI_{GET,SET}DRAGFULLWINDOWS
sysparams.c:241: Test failed: too many changes counter=1 last change=37
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 33 expected 37
or
sysparams.c:1236: testing SPI_{GET,SET}DOUBLECLKHEIGHT
sysparams.c:241: Test failed: too many changes counter=1 last change=8229
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:1271: testing SPI_{GET,SET}DOUBLECLICKTIME
sysparams.c:241: Test failed: too many changes counter=1 last change=32
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 32
sysparams.c:1326: testing SPI_{GET,SET}MOUSEBUTTONSWAP
sysparams.c:241: Test failed: too many changes counter=1 last change=33
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:347: Test failed: Wrong value in registry: Control Panel\Mouse
SwapMouseButtons '1' instead of '0'
sysparams.c:1341: Test failed: SM_SWAPBUTTON: got 1 instead of 0
sysparams.c:1345: Test failed: SwapMouseButton does not return previous state
(really 1)
sysparams.c:1358: testing SPI_GETFASTTASKSWITCH
sysparams.c:1376: testing SPI_{GET,SET}DRAGFULLWINDOWS
sysparams.c:241: Test failed: too many changes counter=1 last change=37
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 33 expected 37
https://test.winehq.org/data/patterns.html#user32:sysparams
Where:
* 30 == SPI_SETDOUBLECLKHEIGHT
* 32 == SPI_SETDOUBLECLICKTIME
* 33 == SPI_SETMOUSEBUTTONSWAP
* 37 == SPI_SETDRAGFULLWINDOWS
* 8229 == SPI_SETHANDEDNESS
Some of these variants are less common than others due to timing so when they
happen they are likely to cause false positives.
Clearly SPI_SETHANDEDNESS is a new setting that was introduced in Windows 10
2004 and which the test should take into account.
Maybe it should receive special treatment like SPI_SETWORKAREA & co?
(Though we don't currently test SPI_SETHANDEDNESS)
--
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.