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

[Bug 53850] New: Mery, TeraPad : When using Japanese input method (IM), undetermined strings are not displayed (regression)
by WineHQ Bugzilla July 24, 2023

July 24, 2023

https://bugs.winehq.org/show_bug.cgi?id=53850 Bug ID: 53850 Summary: Mery, TeraPad : When using Japanese input method (IM), undetermined strings are not displayed (regression) Product: Wine Version: 7.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: su_zu_me(a)hotmail.com Distribution: --- Created attachment 73380 --> https://bugs.winehq.org/attachment.cgi?id=73380 input after "そうか" ("souka"), but not displayed Mery and TeraPad are text editors. When using input method (IM) to input Japanese characters, undetermined strings are not displayed. Candidates are displayed. Conversions are done successfully. It occurs with Wine 7.13 or later. Undetermined strings are displayed inline with Wine 7.12 or earlier, after several conversion after starting the application. note: Right after starting the application, undetermined string is not displayed with all tested version of Wine, but it should be another bug. Application: Mery (x86) Version 2.6.7 Download site: https://forest.watch.impress.co.jp/library/software/mery/ SHA1: edef7350aeed6bab083612e2d316607561f5f31c MerySetup-2.6.7.exe tested Wine version: 6.0.3 (Ubuntu 6.0.3~repack-1) 7.11 7.12 7.13 7.15 7.19 Application: TeraPad Version 1.09 Download site: - SHA1: 3ff8f3741ce82dcea54a385cea484b861007c260 tpad109.zip tested Wine version: 6.0.3 (Ubuntu 6.0.3~repack-1) 7.11 7.12 7.13 7.15 7.19 Application: TeraPad Version 1.10 Download site: https://tera-net.com/library/tpad.html SHA1: ae28027af722c3ea7f6431d04c65582d16c60832 tpad110.exe tested Wine version: 7.12 7.19 terminal output: N/A OS: Ubuntu 22.04.1 LTS (amd64) Display server: Wayland Input Method Framework: IBus Input Method Engine: Mozc installed Wine: winehq-devel -- 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.

1 8

[Bug 55018] New: d2d1:d2d1 sometimes times out on Linux
by WineHQ Bugzilla July 24, 2023

July 24, 2023

https://bugs.winehq.org/show_bug.cgi?id=55018 Bug ID: 55018 Summary: d2d1:d2d1 sometimes times out on Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d2d1:d2d1 sometimes times out on Linux. Apparently something causes the whole test to lock up but because the test is multithreaded this can happen at any point. d2d1:d2d1 start dlls/d2d1/tests/d2d1.c d2d1:d2d1:0810 done (258) in 120s 0B or d2d1:d2d1 start dlls/d2d1/tests/d2d1.c d2d1.c:2692: Test marked todo: Surface does not match. ... d2d1.c:10042: Test marked todo: Test 1: Got unexpected dpi_y 2.88000000e+002, expected 0.00000000e+000. d2d1.c:10039: Test marked todo: Test 2: Got unexpected dpi_x 6.00000000e+001, expected 0.00000000e+000. d2d1:d2d1:077c done (258) in 120s 13391B See https://test.winehq.org/data/patterns.html#d2d1:d2d1 Note that this only happens in the 64-bit tests (including on gitlab-debian-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.

1 4

[Bug 53247] New: user32:sysparams - test_dpi_context() fails on Windows 10 1909+
by WineHQ Bugzilla July 24, 2023

July 24, 2023

https://bugs.winehq.org/show_bug.cgi?id=53247 Bug ID: 53247 Summary: user32:sysparams - test_dpi_context() fails on Windows 10 1909+ 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_dpi_context() fails on Windows 10 1909+: sysparams.c:3813: Test failed: got 0 sysparams.c:3814: Test failed: wrong value -1 https://test.winehq.org/data/patterns.html#user32:sysparams These traces could include a bit more information rather than leaving most of it to the source line number. -- 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.

1 2

[Bug 54015] New: Accessing shared memory from Linux
by WineHQ Bugzilla July 23, 2023

July 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=54015 Bug ID: 54015 Summary: Accessing shared memory from Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: berarma(a)hotmail.com Distribution: --- Some Windows games and applications share some internals through shared memory with external tools. Shared memory is preferred over sockets because it adds no overhead with no latency. It's mostly used in driving and flying simulators to provide visual overlays, data on additional displays, telemetry, rig movement, etc. from external tools. There's also scientific apps using it for similar purposes or general inter-process communication. It's common to use tagged shared memory blocks that external tools can then access using the already known tag. Here's an example from a Python application for rFactor 2: self._rf2_tele = mmap.mmap(0, ctypes.sizeof(rF2Telemetry), f"$rFactor2SMMP_Telemetry${input_pid}") self._rf2_scor = mmap.mmap(0, ctypes.sizeof(rF2Scoring), f"$rFactor2SMMP_Scoring${input_pid}") self._rf2_ext = mmap.mmap(0, ctypes.sizeof(rF2Extended), f"$rFactor2SMMP_Extended${input_pid}") self._rf2_ffb = mmap.mmap(0, ctypes.sizeof(rF2ForceFeedback), "$rFactor2SMMP_ForceFeedback$") Allowing these shared memory blocks to be accessed from Linux would allow us to port some of these tools or even implement or own. Then these tools could access resources or hardware that isn't available from inside the Wine prefix. Some of these tools also fail to run on Wine. Since I guess Wine is already using Linux shared memory mechanism to implement Windows shared memory, the blocks are already available at /dev/shm but they use generic names that can't be associated to the tag used on Windows. Having these shared memory blocks created in the prefix directory with a name containing the tag used on creation would allow us to use it from our native applications. Or any other way to find them using the tags used on Windows. Thanks for your attention. -- 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.

1 13

[Bug 51669] New: EverQuest d3d:wined3d acquires unexpected context
by WineHQ Bugzilla July 23, 2023

July 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=51669 Bug ID: 51669 Summary: EverQuest d3d:wined3d acquires unexpected context Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: johnherschelfreeman2013(a)gmail.com Distribution: --- Created attachment 70543 --> https://bugs.winehq.org/attachment.cgi?id=70543 err wined3d_context_gl_reacquire In game launcher and game client -- 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.

1 5

[Bug 53198] New: ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507
by WineHQ Bugzilla July 23, 2023

July 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=53198 Bug ID: 53198 Summary: ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507: protocol.c:2459: Test failed: Test 0: Got unexpected ret 0 protocol.c:2459: Test failed: Test 1: Got unexpected ret 0 protocol.c:2459: Test failed: Test 2: Got unexpected ret 0 protocol.c:2459: Test failed: Test 3: Got unexpected ret 0 protocol.c:2459: Test failed: Test 4: Got unexpected ret 0 protocol.c:2459: Test failed: Test 5: Got unexpected ret 0 protocol.c:2459: Test failed: Test 12: Got unexpected ret 0 protocol.c:2459: Test failed: Test 13: Got unexpected ret 0 protocol.c:2459: Test failed: Test 14: Got unexpected ret 0 protocol.c:2459: Test failed: Test 15: Got unexpected ret 0 protocol.c:2459: Test failed: Test 16: Got unexpected ret 0 protocol.c:2459: Test failed: Test 28: Got unexpected ret 0 protocol.c:2459: Test failed: Test 29: Got unexpected ret 0 https://test.winehq.org/data/patterns.html#ws2_32:protocol This really looks like a Windows 10 1507 bug so it's tempting to add a broken((hinttests[i].family == AF_UNSPEC && hinttests[i].sock_type != 999) && ...). But it's strange that there is no failure on index 6 for instance since it's the same test after line 2455 (hint.ai_family = AF_INET6): 0: {AF_UNSPEC, SOCK_STREAM, IPPROTO_TCP, 0}, /* 0 */ 6: {AF_INET, SOCK_STREAM, IPPROTO_TCP, 0}, -- 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.

1 2

[Bug 52826] New: All windows are grayed out. text is unreadable
by WineHQ Bugzilla July 23, 2023

July 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=52826 Bug ID: 52826 Summary: All windows are grayed out. text is unreadable Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmikeinsantarosa(a)gmail.com Distribution: --- Created attachment 72213 --> https://bugs.winehq.org/attachment.cgi?id=72213 grayed out windows sample cardfile.exe windows are grayed out. No text is readable. Bug has been present since wine-6.6. link to cardfile.exe and its help file on my google drive https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=… -- 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.

1 9

[Bug 52117] New: All windows are blacked out when running 16 bit cardfile.exe
by WineHQ Bugzilla July 23, 2023

July 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=52117 Bug ID: 52117 Summary: All windows are blacked out when running 16 bit cardfile.exe Product: Wine-staging Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmikeinsantarosa(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71147 --> https://bugs.winehq.org/attachment.cgi?id=71147 top window is unreadable due to being filled with black. All windows are blacked out when running 16 bit cardfile.exe. The program runs but text in any visible window is blacked out. The cardfile.exe and its help can be downloaded from this link https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=… -- 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.

1 12

[Bug 52576] New: Cardfile windows are grayed out
by WineHQ Bugzilla July 23, 2023

July 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=52576 Bug ID: 52576 Summary: Cardfile windows are grayed out Product: Wine-staging Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmikeinsantarosa(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71902 --> https://bugs.winehq.org/attachment.cgi?id=71902 selected window grayed out Program: cardfile.exe (16bit originally released in windows 3.1) Symptom: selected windows are grayed out making any text unreadable. History: this bug has been present in wine & wine-staging since release 6.6 The bug was not present in wine/wine-staging 6.5 -- 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.

1 3

[Bug 44823] New: Steam doesn' t close on exit. Will continue running in background.
by wine-bugs＠winehq.org July 23, 2023

July 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=44823 Bug ID: 44823 Summary: Steam doesn't close on exit. Will continue running in background. Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Created attachment 60857 --> https://bugs.winehq.org/attachment.cgi?id=60857 Steam system information and version Running the latest Steam client, I find that Steam doesn't actually close entirely after I exit normally with Steam>Exit. I have to open System Monitor and kill all steam and wine related processes. I can't open steam again until I do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in the background until I do so. -- 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.

2 14