February 2023 - Wine-Bugs - list.winehq.org

[Bug 54593] gdi32:dc - The SetDeviceGammaRamp() tests fails on Windows 10 1909

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54593 --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- Created attachment 74125 --> https://bugs.winehq.org/attachment.cgi?id=74125 Trace the gamma ramps and some -- 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.

Feb. 27, 2023

[Bug 54593] New: gdi32:dc - The SetDeviceGammaRamp() tests fails on Windows 10 1909

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54593 Bug ID: 54593 Summary: gdi32:dc - The SetDeviceGammaRamp() tests fails on Windows 10 1909 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 gdi32:dc - The SetDeviceGammaRamp() fails on Windows 10 1909: dc.c:1271: Test failed: SetDeviceGammaRamp succeeded dc.c:1276: Test failed: SetDeviceGammaRamp succeeded dc.c:1288: Test failed: SetDeviceGammaRamp succeeded See https://test.winehq.org/data/patterns.html#gdi32:dc The tests tries to set 3 types of invalid gamma ramps and expects Windows to reject them. These failures are 100% reproducible even when running the test on its own (so the failures are not caused by interference from another test). Up until Windows 10 1809 all the tests are skipped: dc.c:1262: Tests skipped: SetDeviceGammaRamp failed, skipping tests And on Windows 10 2004+ the tests succeed. So it looks like 1909 just did not perform all the gamma ramp validation checks. Except that on 2022-07-12 and 2022-11-11, the test had the exact same failures (same lines too) on w1064-tsign which is Windows 10 21H2. -- 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.

Feb. 27, 2023

[Bug 53728] Escape from Tarkov needs DisplayConfigGetDeviceInfo(DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME) implementation

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53728 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |21c373560fa8a8095fc06358441 | |02fe73efc3b51 CC| |zzhang(a)codeweavers.com Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Fixed by 21c373560fa8a8095fc0635844102fe73efc3b51 -- 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.

Feb. 27, 2023

[Bug 54563] The gif is displaying wrongly, with weird backgrounds of various colors

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54563 --- Comment #5 from 399989567(a)qq.com --- (In reply to Dmitry Timoshkov from comment #4) > Created attachment 74118 [details] > patch > > Thanks for the detailed bug report. > > Attached patch does fix the background of the problematic GIF image, however > I'm not sure that it's the proper solution. Your modification can indeed solve the problem, I have tried to modify it in this way before, if I remember correctly, this modification can only solve the pink background problem, can not solve the black background problem (I can test it again later) The essence of this modification is to adjust the transparency of the background color to zero, I think this modification is not correct, the essence of the problem should still be in the parsing of the gif when there is a problem. I seem to have found something that might be causing a problem, in the function "copypixels_to_32bppBGRA" I output. " FIXME("source_format:%d %d %d\n",source_format,format_32bppRGB,format_32bppBGRA); " When I use the official gdiplus.dll (native than buildin) , the problem does not arise and the output here is always: source_format=3; when I use wine's own code, the problem occurs and the output here is alternately "source_format=3 ; source_format=17 " -- 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.

Feb. 27, 2023

[Bug 54462] Mouse cursor invisible

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54462 --- Comment #1 from Daniel <daniel.john.magnus(a)gmail.com> --- I found the line of code, that makes the cursor invisible in Wine, that didn't make it invisible on Windows. window_class.hCursor = LoadCursor(hInstance, IDC_ARROW); The cursor gets visible in Wine if changed to... window_class.hCursor = LoadCursor(NULL, IDC_ARROW); Even if the row is changed to... window_class.hCursor = LoadCursor(GetModuleHandle(NULL), IDC_ARROW); ...then it's still invisible. So, It's some edge cases that makes Wine to not behave exactly the same as Windows with badly written code that was based on code examples in tutorials found on Windows programming on the internet, that people think is "ok". But if I remember correct, it may be that in those examples this row was left out entirely. And that i tried to make is visible in Wine by adding that row according to different examples i found in forums and such. And then you leave out the row, the cursor also become invisible in Wine. So the row should be... window_class.hCursor = LoadCursor(NULL, IDC_ARROW); ...to make it visible in wine. But... window_class.hCursor = LoadCursor(hInstance, IDC_ARROW); ...or... window_class.hCursor = LoadCursor(GetModuleHandle(NULL), IDC_ARROW); ...or leaving it out completely makes in invisible in Wine but not on Windows. -- 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.

Feb. 27, 2023

[Bug 54575] False positive detection of mmc reader as hard drive since kernel 6.1

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54575 --- Comment #4 from Łukasz Buśko <busko.lukasz(a)pm.me> --- Easiest temporary fix put sd card to reader, card do not need to be mounted. -- 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.

Feb. 26, 2023

[Bug 54528] Shamela doesn't run

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54528 --- Comment #28 from ardv <dz.wbdev(a)gmail.com> --- i've copied the patch in a new ile an run it as a command but seems nothing changes same errors -- 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.

Feb. 26, 2023

[Bug 54528] Shamela doesn't run

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54528 --- Comment #27 from ardv <dz.wbdev(a)gmail.com> --- i've attached the logs WINEDEBUG=+cmd wine shamela.exe >& log WINEDEBUG=+cmd wine launcher.exe >& 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.

Feb. 26, 2023

[Bug 54528] Shamela doesn't run

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54528 --- Comment #26 from ardv <dz.wbdev(a)gmail.com> --- Created attachment 74124 --> https://bugs.winehq.org/attachment.cgi?id=74124 launcher.exe log launcher.exe 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.

Feb. 26, 2023

[Bug 54528] Shamela doesn't run

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54528 --- Comment #25 from ardv <dz.wbdev(a)gmail.com> --- Created attachment 74123 --> https://bugs.winehq.org/attachment.cgi?id=74123 shamela.exe log shamela.exe 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.

Feb. 26, 2023