May 2021 - Wine-bugs - list.winehq.org

[Bug 51142] New: Tokyo Xanadu eX+: game crashes when trying to play videos with builtin qasf
by WineHQ Bugzilla 16 May '21

16 May '21

https://bugs.winehq.org/show_bug.cgi?id=51142 Bug ID: 51142 Summary: Tokyo Xanadu eX+: game crashes when trying to play videos with builtin qasf Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: jeremiahpwilson(a)yahoo.com Distribution: --- Created attachment 70011 --> https://bugs.winehq.org/attachment.cgi?id=70011 Terminal Output Hello, there! I'd like to report that Tokyo Xanadu eX+ hangs and then crashes in a manner very similar to that of https://bugs.winehq.org/show_bug.cgi?id=48857 with builtin qasf. Native qasf is a workaround. I'm on Arch Linux x86_64, using a clean prefix and Wine commit ce72f9b4263. I've attached the terminal output and the crash dialog. Thanks! -- 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 36282] New: valgrind shows an unitialized write in ieframe/tests/ie.c
by wine-bugs＠winehq.org 16 May '21

16 May '21

https://bugs.winehq.org/show_bug.cgi?id=36282 Bug ID: 36282 Summary: valgrind shows an unitialized write in ieframe/tests/ie.c Product: Wine Version: 1.3.13 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==16468== Thread 6: ==16468== Syscall param write(buf) points to uninitialised byte(s) ==16468== at 0x4EA8262B: ??? (in /usr/lib/libpthread-2.18.so) ==16468== by 0x7BC46BB8: NtWriteFile (file.c:1073) ==16468== by 0x7B83E0AA: WriteFile (file.c:563) ==16468== by 0x5A01BB8: rpcrt4_conn_np_write (rpc_transport.c:444) ==16468== by 0x59F6B27: rpcrt4_conn_write (rpc_binding.h:189) ==16468== by 0x59F8AA9: RPCRT4_SendWithAuth (rpc_message.c:849) ==16468== by 0x59F9BA0: RPCRT4_Send (rpc_message.c:1245) ==16468== by 0x59FCD02: process_request_packet (rpc_server.c:464) ==16468== by 0x59FCF82: RPCRT4_process_packet (rpc_server.c:519) ==16468== by 0x59FD115: RPCRT4_worker_thread (rpc_server.c:541) ==16468== by 0x7BC909EA: worker_thread_proc (threadpool.c:110) ==16468== by 0x7BC87087: ??? (signal_i386.c:2571) ==16468== by 0x7BC870D0: call_thread_func (signal_i386.c:2630) ==16468== by 0x7BC87065: ??? (signal_i386.c:2571) ==16468== by 0x7BC8E4B0: start_thread (thread.c:428) ==16468== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==16468== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==16468== Address 0x47f9cf4 is 44 bytes inside a recently re-allocated block of size 92 alloc'd ==16468== at 0x7BC4C735: notify_alloc (heap.c:255) ==16468== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==16468== by 0x59F88E9: RPCRT4_SendWithAuth (rpc_message.c:808) ==16468== by 0x59F9BA0: RPCRT4_Send (rpc_message.c:1245) ==16468== by 0x59FCD02: process_request_packet (rpc_server.c:464) ==16468== by 0x59FCF82: RPCRT4_process_packet (rpc_server.c:519) ==16468== by 0x59FD115: RPCRT4_worker_thread (rpc_server.c:541) ==16468== by 0x7BC909EA: worker_thread_proc (threadpool.c:110) ==16468== by 0x7BC87087: ??? (signal_i386.c:2571) ==16468== by 0x7BC870D0: call_thread_func (signal_i386.c:2630) ==16468== by 0x7BC87065: ??? (signal_i386.c:2571) ==16468== by 0x7BC8E4B0: start_thread (thread.c:428) ==16468== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==16468== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==16468== Uninitialised value was created by a client request ==16468== at 0x7BC4C52C: mark_block_uninitialized (heap.c:209) ==16468== by 0x7BC4C697: initialize_block (heap.c:240) ==16468== by 0x7BC50FA3: RtlAllocateHeap (heap.c:1717) ==16468== by 0x501E635: IMalloc_fnAlloc (ifs.c:186) ==16468== by 0x501EF50: CoTaskMemAlloc (objidl.h:1236) ==16468== by 0x505C935: RemUnknown_RemQueryInterface (stubmanager.c:690) ==16468== by 0x50661C6: IRemUnknown_RemQueryInterface_Stub (dcom_p.c:369) ==16468== by 0x59CA5BF: CStdStubBuffer_Invoke (cstub.c:477) ==16468== by 0x503D280: RPC_ExecuteCall (objidl.h:9086) ==16468== by 0x4FFC1ED: apartment_wndproc (compobj.c:1460) ==16468== by 0x548C509: ??? (winproc.c:173) ==16468== by 0x548C67E: call_window_proc (winproc.c:244) ==16468== by 0x548E817: WINPROC_call_window (winproc.c:900) ==16468== by 0x544FBE4: DispatchMessageW (message.c:4019) ==16468== by 0x4793F60: IEWinMain (iexplore.c:1061) ==16468== by 0x472CA34: wWinMain (main.c:84) ==16468== by 0x472CD21: wmain (exe_wmain.c:51) ==16468== by 0x472CBFC: __wine_spec_exe_wentry (exe_wentry.c:36) ==16468== by 0x7B864247: ??? (process.c:1045) ==16468== by 0x7B864394: start_process (process.c:1097) ==16468== -- 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 3

[Bug 28831] New: secur32/tests/schannel.ok: occasional uninitialised memory read in _gnutls_recv_int() in test_communication()?
by wine-bugs＠winehq.org 16 May '21

16 May '21

http://bugs.winehq.org/show_bug.cgi?id=28831 Bug #: 28831 Summary: secur32/tests/schannel.ok: occasional uninitialised memory read in _gnutls_recv_int() in test_communication()? Product: Wine Version: 1.3.30 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: secur32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified I don't see this on every run, but sometimes Valgrind complains: Conditional jump or move depends on uninitialised value(s) at _gnutls_recv_int (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by schan_InitializeSecurityContextW (schannel.c:728) by schan_InitializeSecurityContextA (schannel.c:775) by InitializeSecurityContextA (wrapper.c:282) by test_communication (schannel.c:644) by func_schannel (schannel.c:773) by run_test (test.h:556) by main (test.h:624) Uninitialised value was created by a client request by mark_block_uninitialized (heap.c:208) by initialize_block (heap.c:239) by RtlAllocateHeap (heap.c:1703) by init_buffers (schannel.c:496) by test_communication (schannel.c:633) by func_schannel (schannel.c:773) by run_test (test.h:556) by main (test.h:624) -- 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.

2 4

[Bug 50973] New: winedbg --gdb exits immediately
by WineHQ Bugzilla 16 May '21

16 May '21

https://bugs.winehq.org/show_bug.cgi?id=50973 Bug ID: 50973 Summary: winedbg --gdb exits immediately Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: grandchild(a)mailbox.org Distribution: --- Hi, similar to https://bugs.winehq.org/show_bug.cgi?id=50117 but from version 6.5 onwards, "winedbg --gdb" exits immediately and runs the program, instead of showing the gdb shell, which used to stop after loading but before running the program. Version 6.4 does not have this issue. I've git-bisected it down to this commit: 28fe84da45bea7de56539b50eac8ebcec54342de Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Mar 24 10:53:53 2021 +0100 ntdll: Load the main image from the Unix side. Unfortunately this is a massive commit, and I can't right now put in the time to dig deeper into what might be causing the gdb mode to exit early. Also it doesn't revert easy on the latest version, 6.6. Maybe someone has a quicker understanding of where to look within that change. If not I can start digging deeper myself. To reproduce: winedbg --gdb notepad.exe OS info: latest Archlinux x86-64 Regards, Jakob -- 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 11

[Bug 51055] New: winecfg: Redirection stdout stream
by WineHQ Bugzilla 16 May '21

16 May '21

https://bugs.winehq.org/show_bug.cgi?id=51055 Bug ID: 51055 Summary: winecfg: Redirection stdout stream Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iroalexis(a)outlook.fr Distribution: --- Since Wine 5.18, the stdout stream is completly "ignore/redirect" (I don't know if it is the good words for describe this behavior) in the main function of winecfg.c. This means that the `winecfg -v` and/or `winecfg -?` commands do not display anything I bisect for found the wrong commit, but I did not succeed. I found only a commits window. It's located between a014f413d6719cce883cafe9f40ec0b6468de097 and b16f552e195048f434d486a084fad0fa3afcf712. Before a014f413d6719cce883cafe9f40ec0b6468de097, winecfg displays well the different information of the -? and -v commands. But from b16f552e195048f434d486a084fad0fa3afcf712, this commands don't display nothing. -- 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 51066] New: Fallout New Vegas GOG Edition (1.4.0.525 GOG): Music looping too early
by WineHQ Bugzilla 16 May '21

16 May '21

https://bugs.winehq.org/show_bug.cgi?id=51066 Bug ID: 51066 Summary: Fallout New Vegas GOG Edition (1.4.0.525 GOG): Music looping too early Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wineburn(a)protonmail.com Distribution: --- When playing the GOG version of Fallout:NV, the music loops abruptly every appox. 20 seconds. This affects both the ambient music and the radio. I have tried: - installing the dsound, directshow and quartz verbs - disabling all mods, including official DLCs - Using a completely vanilla installation (this happens in both when using the exe directly and NVSE/ModOrganizer) I am using wine 6.7 staging. EXE SHA1: 946d2eaba04a75ff361b8617c7632b49f1ede9d3 FalloutNV.exe -- 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 50879] New: STDOUT output lost from Winelib applications in Wine 6.5 because of start.exe
by WineHQ Bugzilla 16 May '21

16 May '21

https://bugs.winehq.org/show_bug.cgi?id=50879 Bug ID: 50879 Summary: STDOUT output lost from Winelib applications in Wine 6.5 because of start.exe Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Distribution: --- (split from bug 50869, see there for some other related issues) When launching Winelib applications in Wine 6.5, all output written to STDOUT gets lost. I tested this with a simple C++ file compiled with wineg++ that tries to print some text using both `printf()` and `std::cout`. Printing to STDERR using `std::cerr` still works fine. -- 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 49017] New: Samsung DeX: Does not install
by WineHQ Bugzilla 16 May '21

16 May '21

https://bugs.winehq.org/show_bug.cgi?id=49017 Bug ID: 49017 Summary: Samsung DeX: Does not install Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mayhem6328(a)gmail.com Distribution: --- Created attachment 66998 --> https://bugs.winehq.org/attachment.cgi?id=66998 The logs are here SamsungDeXSetupWin.exe does not want to install! The Sha1sum of it is 39f9216682b56f6d26daa6e7716251d353524eae and the link to download is https://www.samsung.com/global/download/SamsungDeXWin -- 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 51141] New: wine crash at some point when opening 1 specific program input file , but not on others
by WineHQ Bugzilla 15 May '21

15 May '21

https://bugs.winehq.org/show_bug.cgi?id=51141 Bug ID: 51141 Summary: wine crash at some point when opening 1 specific program input file , but not on others Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fluid_02(a)fastmail.fm Distribution: --- Created attachment 70008 --> https://bugs.winehq.org/attachment.cgi?id=70008 generated by wine I am still using an old 16-bit drawing package called "DrawingBoard" from Ashlar. I have been running this under Oracle's VirtualBox until last year, when VirtualBox upgraded to version 6 and DrawingBoard became very slow (more than 10 minutes to open a VLM drawing file which would normally take a few seconds. Than I tried DrawingBoard under wine and it actually works flawlessly, it opens any VLM file quickly and everything seems to work. However there is 1 particular VLM file where wine crashes at the end of reading the VLM file. See attached backtrack.txt. I copied this file from backups to make sure the file is not corrupt, but still a crash. Than I run DrawingBoard again under VirtualBox and the same VLM file did open (but slowly), I made a small change and saved this new drawing under a different name. I tried wine again on this new file, but again wine crashed. -- 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

[Bug 37849] New: Wine causing color temperature setting(redshift) not working for a short time
by wine-bugs＠winehq.org 14 May '21

14 May '21

https://bugs.winehq.org/show_bug.cgi?id=37849 Bug ID: 37849 Summary: Wine causing color temperature setting(redshift) not working for a short time Product: Wine Version: 1.7.32 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: anonymous_temp_mail(a)yahoo.co.jp Distribution: --- [Bug] While using redshift(a display color temperature) and entered the sunset time, if then use wine to start a GUI program, the current display color temperature will be reset for several seconds and return back. [Reproducer] 1. Start redshift and ensure it entered sunset color. Better use -l LAT:LON to fake that you are in somewhere sun is already set. Default redshift will use randr backend to reset the color temp, so no extra setting is needed to reproduce. And default redshift will use 5500K for daytime and 3500K for nighttime, so the color temp change will be quite obvious. 2. Start wine GUI program I'm using Startcraft2 an galgame called "月に寄り添う乙女の作法2", both of them cause the display color temperature reset for several seconds. [Version] wine: 1.7.33 redshift: 1.9.1 -- 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