wine-bugs December 2020

wine-bugs@winehq.org

1 participants
6870 discussions

[Bug 50037] New: wineconsole and mingw64 gdb.exe and keyboard input
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50037 Bug ID: 50037 Summary: wineconsole and mingw64 gdb.exe and keyboard input Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: vladimir.kokovic(a)gmail.com Distribution: --- After the last wineconsole commit, mingw64 gdb.exe(9.2) which works fine in wine17, does not have the ability to control the keyboard input. Any character that is typed on the keyboard is obviously not transferred to the process in which gdb.exe is! commit 627d31fcd9fa1e4657c781ca07ff25e437101820 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Oct 12 18:27:44 2020 +0200 wineconsole: Reimplement as AllocConsole wrapper. -- 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 10

[Bug 47950] New: Ys: Memories of Celceta crashes on launch
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=47950 Bug ID: 47950 Summary: Ys: Memories of Celceta crashes on launch Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: betaversiondot(a)gmail.com Distribution: --- Created attachment 65452 --> https://bugs.winehq.org/attachment.cgi?id=65452 terminal output Ys: Memories of Celceta crashes on launch. Clear wineprefix, launcher works, intro videos disabled. 4.17-staging, Linux-5.2.17, RX 580, Mesa3D 19.2.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.

1 5

[Bug 50169] New: Regression: Microsoft Flight Simulator X hangs on startup (bisected)
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50169 Bug ID: 50169 Summary: Regression: Microsoft Flight Simulator X hangs on startup (bisected) Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: czbd(a)o2.pl CC: julliard(a)winehq.org Regression SHA1: 871d9863bc2d1c9406b47aa644974768d5c6d2c4 Distribution: ArchLinux Created attachment 68686 --> https://bugs.winehq.org/attachment.cgi?id=68686 Git bisect result With the 5.22 release of Wine, Microsoft Flight Simulator X has ceased to launch correctly - instead, it hangs on startup. I attach the git bisect result (of regular Wine), a log taken with Wine Staging 5.21 in which I launch FSX and then close it as soon as it properly loads into main menu, and a log taken with Wine Staging 5.22. -- 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 50240] New: CLR console applications loop output infinitely
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50240 Bug ID: 50240 Summary: CLR console applications loop output infinitely Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- When running any .NET console application, including a simple "hello world" C# example, the first line printed with Console.WriteLine is repeated infinitely. The easiest way to test this is to run c:\windows\Microsoft.Net\Framework\v4.0.30319\csc.exe on a clean Wine prefix. bisect results: 09b6efd685c585e9bcac9a42d9882ead4f84ce92 is the first bad commit commit 09b6efd685c585e9bcac9a42d9882ead4f84ce92 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Tue Dec 1 19:21:58 2020 +0100 server: Block console write until conhost processes ioctl. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=50236 Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 50204] New: wineserver from Wine 5.22-195-gcbca9f847f6 debug dumps NLS object information on shutdown
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50204 Bug ID: 50204 Summary: wineserver from Wine 5.22-195-gcbca9f847f6 debug dumps NLS object information on shutdown Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, since Fri Nov 27 2020 series of commits (Wine 5.22-195-gcbca9f847f6), wineserver now debug dumps objects information on shutdown with default debug verbosity. --- snip --- $ wineboot -u ... 0x2249030:1: Inode device=0x2248eb0 ino=108b5c4 0x2248eb0:1: Device dev=fd01 0x2248d20:1: Fd unix_fd=18 user=(nil) options=00000060 inode=0x2249030 unlink=0 --- snip --- Debugging wineserver yields: --- snip --- ... attach 198986 Attaching to process 198986 Reading symbols from /home/focht/projects/wine/mainline-install-x86_64/bin/wineserver... Reading symbols from /lib64/libdl.so.2... Reading symbols from /usr/lib/debug/usr/lib64/libdl-2.31.so.debug... Reading symbols from /lib64/libc.so.6... Reading symbols from /usr/lib/debug/usr/lib64/libc-2.31.so.debug... Reading symbols from /lib64/ld-linux-x86-64.so.2... Reading symbols from /usr/lib/debug/usr/lib64/ld-2.31.so.debug... 0x00007ff08e3c9c1a in epoll_wait (epfd=9, events=0x7ffd35ea00c0, maxevents=128, timeout=16) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 30 return SYSCALL_CANCEL (epoll_wait, epfd, events, maxevents, timeout); (gdb @ 1:epoll_wait) b inode_dump Breakpoint 1 at 0x410b70: file /home/focht/projects/wine/mainline-src/server/fd.c, line 1132. (gdb @ 1:epoll_wait) c Continuing. Breakpoint 1, inode_dump (obj=0xbdf030, verbose=1) at /home/focht/projects/wine/mainline-src/server/fd.c:1132 1132 fprintf( stderr, "Inode device=%p ino=", inode->device ); (gdb @ 1:inode_dump) bt #0 inode_dump (obj=0xbdf030, verbose=1) at /home/focht/projects/wine/mainline-src/server/fd.c:1132 #1 0x000000000041e813 in dump_objects () at /home/focht/projects/wine/mainline-src/server/object.c:64 #2 0x0000000000432193 in close_socket_timeout (arg=<optimized out>) at /home/focht/projects/wine/mainline-src/server/request.c:950 #3 0x00000000004107df in get_next_timeout () at /home/focht/projects/wine/mainline-src/server/fd.c:953 #4 0x0000000000411c1d in main_loop_epoll () at /home/focht/projects/wine/mainline-src/server/fd.c:599 #5 0x0000000000411f1e in main_loop () at /home/focht/projects/wine/mainline-src/server/fd.c:986 #6 0x00000000004039fb in main () --- snip --- --- snip --- $ ls -la /proc/198986/fd total 0 dr-x------. 2 focht focht 0 Nov 28 11:33 . dr-xr-xr-x. 9 focht focht 0 Nov 28 11:33 .. lrwx------. 1 focht focht 64 Nov 28 11:33 0 -> /dev/null lrwx------. 1 focht focht 64 Nov 28 11:45 1 -> /dev/null lr-x------. 1 focht focht 64 Nov 28 11:45 18 -> /home/focht/projects/wine/mainline-install-x86_64/share/wine/nls/l_intl.nls lrwx------. 1 focht focht 64 Nov 28 11:45 2 -> /dev/pts/2 lr-x------. 1 focht focht 64 Nov 28 11:45 4 -> /home/focht/.wine lr-x------. 1 focht focht 64 Nov 28 11:45 5 -> /tmp/.wine-1000/server-fd01-dd2014 l-wx------. 1 focht focht 64 Nov 28 11:45 6 -> /tmp/.wine-1000/server-fd01-dd2014/lock lrwx------. 1 focht focht 64 Nov 28 11:45 9 -> 'anon_inode:[eventpoll]' --- snip --- fd 18 -> '/home/focht/projects/wine/mainline-install-x86_64/share/wine/nls/l_intl.nls' I didn't do regression test but using above info my bet would be https://source.winehq.org/git/wine.git/commitdiff/8fa03e494acb10303fef360b5… ("server: Create the NLS section object for the l_intl.nls file.)" $ wine --version wine-5.22-195-gcbca9f847f6 Regards -- 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 50105] New: New Vegas Heap Replacer requires unimplemented d3d9 function D3DXMatrixMultiply
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50105 Bug ID: 50105 Summary: New Vegas Heap Replacer requires unimplemented d3d9 function D3DXMatrixMultiply Product: Wine Version: 5.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: katisntgood(a)gmail.com Distribution: --- Created attachment 68596 --> https://bugs.winehq.org/attachment.cgi?id=68596 Crash report New Vegas Heap Replacer, a heap replacement for Fallout: New Vegas in the form of a modified d3d9_38.dll uses D3DXMatrixMultiply which is unimplemented in Wine (the version used by Proton, but this isn't a problem related to that) -- 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 50192] New: [5.22 regression] Python "import sys" crashes with Unhandled exception
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50192 Bug ID: 50192 Summary: [5.22 regression] Python "import sys" crashes with Unhandled exception Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xantares09(a)hotmail.com Distribution: --- the new wine 5.22 crashes on a simple "import sys" in Python: $ wget https://www.python.org/ftp/python/3.8.6/python-3.8.6-embed-win32.zip && unzip python-3.8.6-embed-win32.zip $ wine python.exe -c "import sys" Unhandled exception: page fault on write access to 0x46000004 in 32-bit code (0x7bc29c12). 00ac:fixme:dbghelp:i386_stack_walk new PC=0 different from Eip=70b75362 00ac:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file in module L"python38" Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7bc29c12 ESP:0060f928 EBP:00000006 EFLAGS:00010202( R- -- I - - - ) EAX:002800e8 EBX:00000002 ECX:46000000 EDX:002800e9 ESI:00280000 EDI:00000010 Stack dump: 0x0060f928: 00280094 1037c82c 00000000 00000010 ... 0x0060f978: 00000006 00000006 0060f9cc 70b74645 Backtrace: =>0 0x7bc29c12 EntryPoint+0xffffffff() in ntdll (0x00000006) 1 0x70b74645 EntryPoint+0xffffffff() in ucrtbase (0x0060f9cc) 2 0x70b75362 EntryPoint+0xffffffff() in ucrtbase (0x0060f9cc) 3 0x101405e6 EntryPoint+0xffffffff() in python38 (0x0060f9cc) ... 12 0x7b62c6cc EntryPoint+0xffffffff() in kernel32 (0x0060ff5c) 13 0x7bc550d7 EntryPoint+0xffffffff() in ntdll (0x0060ff5c) 14 0x7bc55310 EntryPoint+0xffffffff() in ntdll (0x0060ffec) 0x7bc29c12 EntryPoint+0xffffffff in ntdll: movl %eax,0x4(%ecx) -- 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 49975] New: Battlefield 1, 4 and V not start from with wine-staging 5.17 on
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=49975 Bug ID: 49975 Summary: Battlefield 1, 4 and V not start from with wine-staging 5.17 on Product: Wine-staging Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: llenort(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68376 --> https://bugs.winehq.org/attachment.cgi?id=68376 crash dump wine-staging 5.19 - BF 1 Hi, from Version 5.17 on, current Version 5.19, no Battlefield game i tested can't start. Tested with wine-staging Version 5.17, 5.18 and 5.19. I attached a crash dump file. Wine-staging Version 5.16 works perfect for all BF Games i tested so far. Thank you for your support. All the Best :-) lle -- 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 46237] New: Far 3.0 x86 crashes starting from build 5288
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=46237 Bug ID: 46237 Summary: Far 3.0 x86 crashes starting from build 5288 Product: Wine Version: 3.21 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)chatty.de Created attachment 62934 --> https://bugs.winehq.org/attachment.cgi?id=62934 Build 5287 runs fine. Starting from build 5288 Far 3.0 x86 crashes at startup. -- 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 22

[Bug 49116] New: Windows 10 1903 SDK (10.0.18362.0) installer crashes (method invocation on wrong CCW interface?)
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=49116 Bug ID: 49116 Summary: Windows 10 1903 SDK (10.0.18362.0) installer crashes (method invocation on wrong CCW interface?) Product: Wine Version: 5.7 Hardware: x86 URL: https://web.archive.org/web/20200215010843/https://dow nload.microsoft.com/download/4/2/2/42245968-6A79-4DA7- A5FB-08C0AD0AE661/windowssdk/winsdksetup.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- It calls _AppDomain::CreateInstance() from unmanaged code to retrieve a COM pointer to one of its own objects (specifically, BootstrapperApplicationFactory, hosted in BootstrapperCore.dll), and then tries to invoke a method on the object. The problem is that the method it invokes has vtbl offset 0x38, but Mono gives us back what *seems* to be an IDispatch vtbl, so it ends up invoking junk. This consistently results in an execute fault for me. Relevant disassembly, from mbahost.dll: 1286: 8b 45 08 >mov eax, [ebp+08h] 1289: 8d 55 fc lea edx, [ebp-04h] 128c: 52 push edx 128d: 57 push edi 128e: 53 push ebx 128f: 8b 08 mov ecx, [eax] 1291: 50 push eax 1292: ff 91 94 00 00 00 call dword [ecx+00000094h] // CreateInstance(), apparently 1298: 8b f0 mov esi, eax 129a: 85 f6 test esi, esi 129c: 79 08 jns 12a6 // jump if SUCCEEDED 129e: 56 push esi 129f: 68 1f 02 00 00 push dword 0000021Fh 12a4: eb 48 jmp 12ee 12a6: 8b 45 fc >mov eax, [ebp-04h] 12a9: 8d 55 ec lea edx, [ebp-14h] 12ac: 52 push edx 12ad: 50 push eax 12ae: 8b 08 mov ecx, [eax] 12b0: ff 51 38 call dword [ecx+38h] // crashes Presumably Mono is wrong in returning IDispatch here, but I'm not sure why, and it's not clear what should be returned in its stead. The class in question actually has a ClassInterfaceType of AutoDispatch, but maybe that doesn't actually mean we should return IDispatch? But the CIL interface that class explicitly implements, IBootstrapperApplicationFactory, only has one method, so I'm not sure how an offset of 0x38 makes sense there either. When I get the time I'll build and run a testcase... -- 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 20

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2020