wine-bugs November 2022

wine-bugs@winehq.org

1 participants
3847 discussions

[Bug 46538] New: Unreal Tournament (UT99): mouse clicks in main menu work only once (regression)
by wine-bugs＠winehq.org 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=46538 Bug ID: 46538 Summary: Unreal Tournament (UT99): mouse clicks in main menu work only once (regression) Product: Wine Version: 4.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nowic(a)wenner.ch Distribution: --- Created attachment 63395 --> https://bugs.winehq.org/attachment.cgi?id=63395 Commandline output The main menu drop downs only works the first time using the mouse. After the first click only navigation using the keyboard works which is quite annoying. I remember that this worked without issues in a previous version of wine. Probably wine < 3.0. GPU: GeForce 940MX -- 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 8

[Bug 54000] New: user32:win - test_mouse_input() gets an unexpected 0x60 message on Windows 11
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54000 Bug ID: 54000 Summary: user32:win - test_mouse_input() gets an unexpected 0x60 message on Windows 11 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:win - test_mouse_input() gets an unexpected 0x60 message on Windows 11: win.c:4513: Test failed: hwnd 0000000000C6043C message 0060 win.c:4519: Test failed: message 0060 available See https://test.winehq.org/data/patterns.html#user32:win I could not find the what the 0x60 message corresponds to but, according to the tests, it is specific to Windows 11. -- 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 53911] New: DC++ is no longer able to retrieve file list from another user.
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53911 Bug ID: 53911 Summary: DC++ is no longer able to retrieve file list from another user. Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: dee3shee7aeno4(a)mailinator.com Distribution: --- Since following commit DC++ is no longer able to retrieve the file list from another user: commit 8312539efe18533f6e2b35882d12e9d1bcbefa0d Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Fri Jun 25 20:21:08 2021 -0500 ws2_32: Use IOCTL_AFD_WINE_GET_SO_RCVBUF. Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> It looks like the application retrieves the buffer size via a call to getsockopt(SO_RCVBUF), but unfortunately receives a size of zero since the above commit. The commit seems to not call getsockopt in the DC++ process any longer, instead it returns the value from a wineserver call. Wine-gdb> bt #0 WS_getsockopt (s=<optimized out>, level=<optimized out>, optname=<optimized out>, optval=0x3f2fba8 "", optlen=<optimized out>) at wine/dlls/ws2_32/socket.c:2571 #1 0x0000000000667c7f in <lambda()>::operator() (__closure=<synthetic pointer>) at dcpp/Socket.cpp:510 #2 dcpp::(anonymous namespace)::check<dcpp::Socket::getSocketOptInt(int)::<lambda()> > (blockOk=false, f=...) at dcpp/Socket.cpp:52 #3 dcpp::Socket::getSocketOptInt (this=0x29d6fc0, option=option@entry=4098) at dcpp/Socket.cpp:510 #4 0x00000000005bd3aa in dcpp::BufferedSocket::threadAccept (this=this@entry=0x29d8820) at dcpp/BufferedSocket.cpp:179 #5 0x00000000005c4418 in dcpp::BufferedSocket::checkEvents (this=this@entry=0x29d8820) at dcpp/BufferedSocket.cpp:463 #6 0x00000000005c48e8 in dcpp::BufferedSocket::run (this=0x29d8820) at dcpp/BufferedSocket.cpp:498 #7 0x000000000098c3da in dcpp::Thread::starter (p=<optimized out>) at dcpp/Thread.h:107 https://sourceforge.net/p/dcplusplus/code/ci/default/tree/dcpp/Socket.cpp#l… https://sourceforge.net/p/dcplusplus/code/ci/default/tree/dcpp/BufferedSock… The wineserver sock->rcvbuf gets initialized here: (gdb) bt #0 create_socket () at wine/server/file.h:240 #1 0x0000555946fd7619 in accept_socket (sock=0x555949c36cc0) at wine/server/sock.c:1618 #2 0x0000555946fd9c9e in sock_ioctl (fd=<optimized out>, code=<optimized out>, async=0x555949c3fb40) at wine/server/sock.c:2016 #3 0x0000555946fb4481 in req_ioctl (req=0x555949c371c8, reply=0x7ffcfd2ec140) at wine/server/fd.c:2794 #4 0x0000555946fd39cb in call_req_handler (thread=<optimized out>) at wine/server/request.c:312 #5 0x0000555946fdcd10 in thread_poll_event (fd=<optimized out>, event=<optimized out>) at wine/server/thread.c:388 #6 0x0000555946fb1c67 in main_loop_epoll () at wine/server/fd.c:525 #7 0x0000555946fb1ece in main_loop () at wine/server/fd.c:985 #8 0x0000555946fa3a80 in main () And following change makes DC++ work again with wine-7.21, unsure if this is correct: --- a/server/sock.c +++ b/server/sock.c @@ -1998,6 +1998,7 @@ static struct sock *accept_socket( struct sock *sock ) acceptsock->window = sock->window; acceptsock->message = sock->message; acceptsock->connect_time = current_time; + acceptsock->rcvbuf = sock->rcvbuf; if (sock->event) acceptsock->event = (struct event *)grab_object( sock->event ); -- 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 53595] New: Iran Timezone is not detected correctly
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53595 Bug ID: 53595 Summary: Iran Timezone is not detected correctly Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aria.moradi007(a)gmail.com Distribution: --- I get errors like ``` 00f0:fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for +0430, bias -210, std (d/m/y): 22/09/2022, dlt (d/m/y): 22/03/2022 00f8:fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for +0430, bias -210, std (d/m/y): 22/09/2022, dlt (d/m/y): 22/03/2022 0100:fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for +0430, bias -210, std (d/m/y): 22/09/2022, dlt (d/m/y): 22/03/2022 ``` Programs hang and don't run after errors like that, deleting the wine prefix and running the program again tends to fix the issue, but running the same (or any) program after that yields the issue, Also I didn't encounter the issue while running lutris' wine builds. I'm running Arch Linux if that's related to anything and `/etc/localtime` is symliked to `/usr/share/zoneinfo/Asia/Tehran` -- 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 6

[Bug 53503] New: QuickBooks Pro 99 page faults with print preview or attempting to print
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53503 Bug ID: 53503 Summary: QuickBooks Pro 99 page faults with print preview or attempting to print Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nexusofbooths(a)gmail.com Distribution: --- Created attachment 72866 --> https://bugs.winehq.org/attachment.cgi?id=72866 dialog from wine 7.14 running Quickbooks Pro 99 attempting to print When attempting to print preview or print after dialog, wine enters debugger with "Unhandled exception: page fault on read access to 0x00000006 in 32-bit code (0x160abeca)" Program worked perfectly in wine 7.10, printing broke in 7.11, and now also 7.14. compiled wine 7.14 32bit from source. No mods. configure CC="ccache gcc" CROSSCC="ccache i686-w64-mingw32-gcc" make -j 5 -l 3 -- 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 53099] New: wineserver (gcc -O0) crash when exiting LiLi USB Creator
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53099 Bug ID: 53099 Summary: wineserver (gcc -O0) crash when exiting LiLi USB Creator Product: Wine Version: 7.10 Hardware: x86-64 URL: http://download.tuxfamily.org/lilicreator/stable/Linux Live%20USB%20Creator%202.9.4.exe OS: Linux Status: NEW Keywords: download, regression, source Severity: critical Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Regression SHA1: a61188bfa5bf20443b11f397d8ef6e7e5fd4bdf1 Distribution: Ubuntu Created attachment 72529 --> https://bugs.winehq.org/attachment.cgi?id=72529 Wine 7.10 (gcc -O0) console output When Wine is compiled with -O0 (no optimisation), wineserver crashes when exiting the LinuxLive USB Creator. -O1, -O2 or -O3 optimisation doesn't experience the crash.Tried with GCC 7 and 8. [334632.437161] wineserver[471477]: segfault at aaaaaace ip 00000000566503c3 sp 00000000ffb530a0 error 4 in wineserver[56634000+99000] [334632.437172] Code: 8d 90 38 6d fd ff 52 89 c3 e8 e9 ad fe ff 90 8b 5d fc c9 c3 55 89 e5 83 ec 08 e8 c7 cc fe ff 05 10 1a 08 00 8b 45 08 8b 40 28 <8b> 40 24 83 ec 08 ff 75 0c ff 75 08 ff d0 83 c4 10 90 c9 c3 55 89 gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 gcc-8 (Ubuntu 8.4.0-1ubuntu1~18.04) 8.4.0 Bisect shows this started happening at commit a61188bfa5bf20443b11f397d8ef6e7e5fd4bdf1 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Fri Nov 27 18:13:59 2020 +0100 server: Use separated fd ops for unbound console input. 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 8

[Bug 53756] New: configure fails in 32-bit gcc checking pthread_create using -Wl,--disable-stdcall-fixup
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53756 Bug ID: 53756 Summary: configure fails in 32-bit gcc checking pthread_create using -Wl,--disable-stdcall-fixup Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: zakarjor(a)yahoo.com Distribution: --- in 32-bit wine build, ./configure fails with the following message: checking for pthread_create in -lpthread... no configure: error: pthread 32-bit develment files not found. Wine cannot support threads without libpthread. Use the --without-pthread option if you really want this. Checking config.log, the problem seems to be related to a second test of -Wl,--disable-stdcall-fixup for cross-compiler, which sets CFLAGS with that argument, and pthread test uses gcc that doesn't have that flag. in case $host_cpu in *i[3456]86*), it checks -Wl,--disable-std-call-fixup and since gcc doesn't have it, CFLAGS is not changed, but further down, when it tests the same flag for cross-compiler, since 32-bit mingw gcc has that flag, CCFLAGS now appends that flag. Eventually when pthread_create is tested using gcc with CFLAGS containing the unknown flag for gcc, it fails to compile, and wrongly says it couldn't find pthread_create. This works for case x86_64 since no such flag test exists. This looks like a regression by changes in https://gitlab.winehq.org/wine/wine/-/commit/8b7baa1128d974b6b9e4fc49853242… -- 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 53550] New: Some Catalan locales not properly handled
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53550 Bug ID: 53550 Summary: Some Catalan locales not properly handled Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marc.ruiz+wine(a)live.com Distribution: --- My system has locale ca_AD.UTF-8 which is for Catalan. However Wine apparently does not recognize it as Catalan, it only recognizes ca_ES. How to reproduce: LANG=ca_AD.UTF-8 winecfg -> UI is shown in English (wrong). LANG=ca_ES.UTF-8 winecfg -> UI is shown in Catalan (right). LANG=ca_FR.UTF-8 winecfg -> UI is shown in English (wrong). LANG=ca_IT.UTF-8 winecfg -> UI is shown in English (wrong). I have actually discovered this while running YY-CHR (https://appdb.winehq.org/objectManager.php?sClass=version&iId=22701). Running this program with WINEDEBUG=nls I have discovered that ca_ES is mapped to locale CAT and ca_AD and the others to ZZZ. -- 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 53525] New: dinpu:hid - test_hid_multiple_tlc() sometimes fails with testsigning turned on
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53525 Bug ID: 53525 Summary: dinpu:hid - test_hid_multiple_tlc() sometimes fails with testsigning turned on Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinpu:hid - test_hid_multiple_tlc() sometimes fails with testsigning turned on: hid.c:3926: Test failed: Failed to find HID device matching L"\\\\?\\hid#vid_1209&pid_0001&col02" hid.c:3930: Test failed: got error 2 hid.c:3040: Test failed: HidD_GetPreparsedData failed with error 6 hid.c:3043: Test failed: got "\\\x00\\\x00?\x00\\\x00" expected "HidP KDR" https://test.winehq.org/data/patterns.html#dinput:hid These failures happened on both fgtb-w10pro64-tsign and w1064-tsign and only those. So they seem to be specific to Windows 10 with test signing turned on. -- 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 6

[Bug 52997] New: Integration of D3D12 support with a PE build of vkd3d causes a crash in Steam Overlay.
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52997 Bug ID: 52997 Summary: Integration of D3D12 support with a PE build of vkd3d causes a crash in Steam Overlay. Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: cmccarthy(a)codeweavers.com Distribution: --- Launching a D3D12 game with Steam Overlay enabled results in a null pointer dereference right after a call to D3D11On12CreateDevice(). Changing the returned values alters the crash location. This is a regression caused by integration of a vkd3d PE build in commit 5d62e5603. The call to D3D11On12CreateDevice() doesn't occur when using an ELF vkd3d build. -- 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

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 November 2022