July 2023 - Wine-bugs - list.winehq.org

[Bug 46676] New: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=46676 Bug ID: 46676 Summary: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13 Product: Wine Version: 4.0 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: martin(a)hinner.info Created attachment 63628 --> https://bugs.winehq.org/attachment.cgi?id=63628 suspected problematic function Tested on: Mac OS/X 10.9, 10.13 WineBottler (Wine 1.8) works fine; Wine 4.0 (from .pkg) does not work Our application is trying to enumerate serial ports by using setupapi functions. I have not checked where exactly is the problem as debugging on OS/X is a bit difficult for me, however suspected function is attached (it's goal is to get device description). The affected apps are http://obdtester.com/ficom , http://obdtester.com/bimcom , http://obdtester.com/fcom ; I have tried to create symlink in dosdevices (required for WineBottler to get it working), one OS/X 10.13 my link got deleted everytime I ran the app; on OS/X 10.9 link persisted, but not possible to enumerate any serial port(s). I can provide login for download by personal e-mail (not to be disclosed). I have talked about this on wine mailing list a long time ago, it would be super easy if Wine-enabled application can have a way to load system native .so to talk directly to the host system, I have many examples of device drivers that would be super easy to implement. FYI I have already written "winegate.dll.so" which solves this real world problem, but it was rejected for submission to Wine because of "Wine must be 100% transparent" ideology. -- 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 9

[Bug 50778] New: TortoiseMerge closes before showing a window
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=50778 Bug ID: 50778 Summary: TortoiseMerge closes before showing a window Product: Wine Version: 6.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lexlexlex(a)gmail.com Distribution: --- Created attachment 69576 --> https://bugs.winehq.org/attachment.cgi?id=69576 Terminal log for TortoiseMerge startup and subsequent closing with wine Steps to reproduce: 1. Install TortoiseSVN in a 64-bit wine prefix. 2. Try to run TortoiseMerge.exe with the wine prefix mentioned in step 1. For example, run "wine TortoiseMerge.exe" from a terminal if the default wine prefix was used. Current behavior: TortoiseMerge closes before showing a window. No TortoiseMerge window appears. Expected behavior: TortoiseMerge is expected to start, allowing the user to compare and merge files in a windowed GUI. Additional information: A download for the current version of the TortoiseSVN installer as of this report is at https://osdn.net/projects/tortoisesvn/storage/1.14.1/Application/TortoiseSV… A log showing terminal output when trying to run "wine TortoiseMerge.exe" is attached. Opinion: This is one of 2 bugs preventing using TortoiseSVN fully in wine. The other is 50756. If these 2 bugs are fixed, TortoiseSVN could be used fully, easing the transition of users whose jobs rely on SVN to Linux. Currently some companies still use SVN and I've tried all the free SVN clients for Linux, and none of them come close to the level of convenience and intuitiveness that TortoiseSVN provides. I have nemo actions ready to enable full usage in of TortoiseSVN in Linux if these 2 bugs are fixed. This would help me personally tremendously, as digging through old revisions in alternate SVN branches is part of my job and extremely difficult with any SVN client other than TortoiseSVN using TortoiseMerge. Thanks for reading this. -- 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 7

[Bug 51212] New: i want to install itunes, it installed through wine but giving some error while to launch the program
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51212 Bug ID: 51212 Summary: i want to install itunes, it installed through wine but giving some error while to launch the program Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: robinssgraphics(a)gmail.com Distribution: --- Created attachment 70086 --> https://bugs.winehq.org/attachment.cgi?id=70086 i want to install itunes, it installed through wine but giving some error while to launch the program i want to install itunes, it installed through wine but giving some error while to launch the program -- 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 53850] New: Mery, TeraPad : When using Japanese input method (IM), undetermined strings are not displayed (regression)
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

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 24 Jul '23

24 Jul '23

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 55318] New: ntdll:time - test_TimerResolution() fails on Windows 11
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55318 Bug ID: 55318 Summary: ntdll:time - test_TimerResolution() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:time - test_TimerResolution() fails on Windows 11: time.c:284: Test failed: expected new timer resolution 5000, got 4882 time.c:284: Test failed: NtQueryTimerResolution() expected timer resolution 4882, got 5000 See https://test.winehq.org/data/patterns.html#ntdll: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.

1 1

[Bug 53247] New: user32:sysparams - test_dpi_context() fails on Windows 10 1909+
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

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 55308] New: tools/winebuild/res16.c:156:5: runtime error: null pointer passed as argument 1, which is declared to never be null (UndefinedBehaviorSanitizer)
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55308 Bug ID: 55308 Summary: tools/winebuild/res16.c:156:5: runtime error: null pointer passed as argument 1, which is declared to never be null (UndefinedBehaviorSanitizer) Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian Created attachment 74908 --> https://bugs.winehq.org/attachment.cgi?id=74908 build log I've been using UndefinedBehaviorSanitizer at my day job and found it pretty useful, so did some brief testing on it with Wine. Not everything builds (notably loader/ and dlls/ntdll/unix/), but most other stuff does. For this issue, just recompiling tools/winebuild is enough to see the issue: ./configure && make -j12 cd tools/winebuild make clean make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined" cd ../../dlls/avifile.dll16/ make clean && make tools/winegcc/winegcc -o dlls/avifile.dll16/i386-windows/avifile.dll16 --wine-objdir . -b i686-w64-mingw32 -Wl,--wine-builtin -shared \ dlls/avifile.dll16/avifile.dll16.spec -m16 -Wb,--main-module,avifil32.dll \ dlls/avifile.dll16/i386-windows/main.o dlls/avifil32/i386-windows/libavifil32.a \ dlls/winecrt0/i386-windows/libwinecrt0.a dlls/ucrtbase/i386-windows/libucrtbase.a \ dlls/krnl386.exe16/i386-windows/libkernel.a dlls/kernel32/i386-windows/libkernel32.a \ dlls/ntdll/i386-windows/libntdll.a -Wl,--disable-stdcall-fixup tools/winebuild/res16.c:156:5: runtime error: null pointer passed as argument 1, which is declared to never be null Seems to affect most win16 dlls, there are a total of 44 occurrences (build log attached). -- 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 1

[Bug 54015] New: Accessing shared memory from Linux
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

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 55315] New: tools/wrc/parser.l:626:5: runtime error: null pointer passed as argument 2, which is declared to never be null (UndefinedBehaviorSanitizer)
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55315 Bug ID: 55315 Summary: tools/wrc/parser.l:626:5: runtime error: null pointer passed as argument 2, which is declared to never be null (UndefinedBehaviorSanitizer) Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian +++ This bug was initially created as a clone of Bug #55314 +++ For this issue, just recompiling tools/wrc is enough to see the issue: ./configure && make -j12 cd tools/wrc make clean make CFLAGS="-fsanitize=undefined" LDFLAGS="-fsanitize=undefined" tools/wrc/wrc -u -o programs/winedbg/winedbg.res --nostdinc --po-dir=po -Iprograms/winedbg -Iinclude -Iinclude/msvcrt \ -Ilibs/zydis/include -D_UCRT -D__WINESRC__ programs/winedbg/winedbg.rc tools/wrc/parser.l:626:5: runtime error: null pointer passed as argument 2, which is declared to never be null -- 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 0