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

[Bug 49371] New: Incorrect output buffer length check in WSAIoctl with SIO_GET_INTERFACE_LIST
by WineHQ Bugzilla 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49371 Bug ID: 49371 Summary: Incorrect output buffer length check in WSAIoctl with SIO_GET_INTERFACE_LIST Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: j.g.rennison(a)gmail.com Distribution: --- The output buffer length check in the implementation of the SIO_GET_INTERFACE_LIST ioctl in WSAIoctl is not correct. In the event that there are more interfaces than the supplied buffer is sized for, this can result in output data being written beyond the end of the supplied buffer and no error returned. This can cause undefined behaviour such as crashes, etc. With reference to line 4796 in dlls/ws2_32/socket.c https://github.com/wine-mirror/wine/blob/343043153b44fa46a2081fa8a2c171eac7… if ((numInt + 1)*sizeof(INTERFACE_INFO)/sizeof(IP_ADAPTER_INFO) > out_size) should instead be if ((numInt + 1)*sizeof(INTERFACE_INFO) > out_size) This because the output buffer write pointer intArray is of type INTERFACE_INFO*, and numInt is the index relative to the start of the output buffer, not the size returned from GetAdaptersInfo. The bug appears to have been introduced in commit a239e8ed. https://github.com/wine-mirror/wine/commit/a239e8ed27b1c3cde6bc568c3d7b9996… -- 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 47328] New: Steam crashes when loading the Store tab ( Assertion Failed: killing unresponsive browser for URL)
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47328 Bug ID: 47328 Summary: Steam crashes when loading the Store tab (Assertion Failed: killing unresponsive browser for URL) Product: Wine Version: 4.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeffersoncarpenter2(a)gmail.com Distribution: --- Created attachment 64652 --> https://bugs.winehq.org/attachment.cgi?id=64652 Console output running Steam.exe under wine Steps to reproduce: Install Steam. Run and visit store tab. Expected behavior: Steam loads store tab Actual behavior: Steam hangs for 40 seconds, then crashes. Attached is the console output. Samba is installed, as well as allfonts via winetricks. This should not be a duplicate of 30202 or 29230 since the first is closed as fixed (and I installed allfonts), and the second has a different error in the console output. -- 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 7

[Bug 55078] New: Powerpoint 2007: "Print to file" broken
by WineHQ Bugzilla 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55078 Bug ID: 55078 Summary: Powerpoint 2007: "Print to file" broken Product: Wine Version: 8.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Printing a large document in Powerpoint 2007 does not work when "Print to file" is selected in the print dialog. Printing to the printer works. When failing the printing to file goes very quick and after a long pause after the end of printing a exception is raised and wine terminates. The crash dump seems to be not helpful, it points inside a Powerpoint library. A Bisect shows the following commit (which does not help really): commit 7034fc297bf730427c6c808cb3f574b56f50b60f Author: Piotr Caban <piotr(a)codeweavers.com> Date: Mon May 1 13:11:42 2023 +0200 winspool: Change CUPS printers print processor to wineps. dlls/winspool.drv/info.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) I created a new prefix before each test. In previous versions of wine printing to file worked. -- 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 23

[Bug 35701] New: League of Legends: Right click contextual menu on friends list is invisible
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=35701 Bug ID: 35701 Summary: League of Legends: Right click contextual menu on friends list is invisible Product: Wine Version: 1.7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: echo(a)cyphernaut.org When I open League of Legends, and I open the friends list, you can right click on a friend to do things such as remove, spectate, message, etc, however in Wine (as of 1.7.13) this contextual menu is invisible. Items in the menu are still clickable, if you know where to click them. No crash or anything occurs, just an invisible menu. This occurs both with and without compositing enabled, and I've seen it occurring on both Nvidia proprietary drivers as well as RadeonSI Mesa drivers. No output is given to the console when I right-click on the friends list. -- 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 28

[Bug 46888] New: Office 2007 word does not export to PDF/A
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=46888 Bug ID: 46888 Summary: Office 2007 word does not export to PDF/A Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Created attachment 63964 --> https://bugs.winehq.org/attachment.cgi?id=63964 Wine log with +t2embed,+fontsub Office 2007 Word failes when exporting to PDF/A. To reproduce: - Start Office 2007 Word - Select "Save As" (in the MS Logo in the upper left corner) - Select "PDF or XPS" - Select "Options" and mark "ISO ... (PDF/A)" - Select Publish The eror message "This file could not be found" appears and nothing is exported. There is an old forum thread https://forum.winehq.org/viewtopic.php?f=8&t=19850. In this thread the dlls t2embed and fontsub are seen as problematic for font embedding. Maybe this is a helpful link. -- 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 2

[Bug 42867] New: steam store doesnt work
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42867 Bug ID: 42867 Summary: steam store doesnt work Product: Wine Version: 2.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bronsonmathews(a)gmail.com Distribution: --- trying to access the steam store through steam itself doesnt work at all. -- 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 7

[Bug 53446] New: Total War Shogun 2 crashes on Intel Iris Plus Graphics G4
by WineHQ Bugzilla 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53446 Bug ID: 53446 Summary: Total War Shogun 2 crashes on Intel Iris Plus Graphics G4 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: hibbsncc1701(a)gmail.com Distribution: --- Created attachment 72820 --> https://bugs.winehq.org/attachment.cgi?id=72820 Console log on wine-7.14 with WINEDEBUG=+seh. Total War Shogun 2 crashes during startup on Intel Iris Plus Graphics G4 hardware with an EXCEPTION_ACCESS_VIOLATION. Under Nvidia hardware the game boots normally. -- 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 51383] New: S.T.A.L.K.E.R.: Call of Pripyat rendering is messed up with Enhanced full dynamic lighting (DX10)
by WineHQ Bugzilla 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51383 Bug ID: 51383 Summary: S.T.A.L.K.E.R.: Call of Pripyat rendering is messed up with Enhanced full dynamic lighting (DX10) Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 70239 --> https://bugs.winehq.org/attachment.cgi?id=70239 screenshot After bug 50209 wine-6.11-319-g52ba1b498a9 -- 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 51950] New: Iperf 2.0.8 hangs in parallel dual mode on localhost
by WineHQ Bugzilla 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51950 Bug ID: 51950 Summary: Iperf 2.0.8 hangs in parallel dual mode on localhost Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- I found a problem in Wine winsock that may also be related to bug 51442 but I'm opening a new bug report since this is not a regression. On Windows, it is possible to run iperf 2.0.8 in dual mode on localhost in parallel mode, so the following command works: iperf -c 127.0.0.1 -d -t 1 -P 5 However, the same command freezes iperf completely on Wine, few messages "connect failed: Connection refused" appear and Ctrl+C for terminating iperf does not work. This behavior is valid for all Wine versions (tested on 6.0.2, 6.11 and 6.20). -- 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 51982] New: When installing Kobo for Desktop, user data meant for AppData\Local\Kobo is instead placed inside an arbitrary folder of the program's installation.
by WineHQ Bugzilla 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51982 Bug ID: 51982 Summary: When installing Kobo for Desktop, user data meant for AppData\Local\Kobo is instead placed inside an arbitrary folder of the program's installation. Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vorxborx(a)gmail.com Distribution: --- Created attachment 70967 --> https://bugs.winehq.org/attachment.cgi?id=70967 Wine user registry Disclaimer: This is more of a curiosity than an issue, but I believe it may be linked to issues with other software. Summary: After installing Kobo Desktop (https://appdb.winehq.org/objectManager.php?sClass=version&iId=34526 see latest test result for information on how to download the installer correctly) everything worked correctly, and the program is fully functional (fantastic job!). When inspecting the program's files, attempting to find the user data, I expected to find it at: "~/.wine/drive_c/users/alex/AppData/Local/Kobo/Kobo Desktop Edition" which is where it is on a native Windows installation. However, this folder may exist, but is empty (no hidden files either). Upon inspection, the contents of this folder instead ended up inside: "~/.wine/drive_c/Program Files (x86)/Kobo/fonts/" along with the font files expected there. Steps to reproduce: - download the installer. - install the program. - inspect the folder it was installed to. The program works fine and manages to find and write to the folder where the user data now is. I assume something went slightly wrong during installation, so I have included terminal logs on that process. I tested this on Manjaro (Wine 6.16) and KDE Neon Unstable (Wine 6.0.2) with identical results. The program in question is proprietary, so there isn't an option to inspect the way it loads the location of these files, or determines the path in the first place. I have included the user.reg, and the two installation logs, though I couldn't find anything particularly noteworthy myself. Thank you, Alex -- 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