January 2022 - Wine-Bugs - list.winehq.org

[Bug 45042] New: Steam doesn't uninstall applications, gets stuck saying " deleting %app" until next popup isn't very visible
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

https://bugs.winehq.org/show_bug.cgi?id=45042 Bug ID: 45042 Summary: Steam doesn't uninstall applications, gets stuck saying "deleting %app" until next popup isn't very visible Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: romulasry(a)gmail.com Distribution: --- Created attachment 61171 --> https://bugs.winehq.org/attachment.cgi?id=61171 wine log It is nearly impossible to delete steam applications when you right click then select uninstall. -- 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 10

[Bug 41466] New: Steam: Tray icon menu sometimes flickers
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

https://bugs.winehq.org/show_bug.cgi?id=41466 Bug ID: 41466 Summary: Steam: Tray icon menu sometimes flickers Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- Created attachment 55847 --> https://bugs.winehq.org/attachment.cgi?id=55847 Terminal output On starting Steam, making a right click on the tray icon and clicking on "Setings" instead of vanishing most times the tray icon menu gets black and begins to flicker. This behavior disappears as soon as the mouse cursor is moved. In the attachments is the terminal output where this issues happened. -- 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 5

[Bug 44529] New: [Steam] Process remaining after exiting
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

https://bugs.winehq.org/show_bug.cgi?id=44529 Bug ID: 44529 Summary: [Steam] Process remaining after exiting Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxi.cass11(a)gmail.com Distribution: --- Created attachment 60483 --> https://bugs.winehq.org/attachment.cgi?id=60483 wine 3.1 terminal output When I close steam with the tray icon, a steam process is still her and use 14% of the CPU. I have attached the console output when I leave steam, I don't know how can I give more relevant information. -- 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 24614] New: Medieval Total War crashes on startup
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

http://bugs.winehq.org/show_bug.cgi?id=24614 Summary: Medieval Total War crashes on startup Product: Wine Version: 1.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: th.seltsam(a)gmail.com CC: wine-bugs(a)winehq.org Running the game just shows a black window, no crash dialog, and an infinite console output err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed Using d3dx9-36 did not solve the problem. -- 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 27

[Bug 49371] New: Incorrect output buffer length check in WSAIoctl with SIO_GET_INTERFACE_LIST
by WineHQ Bugzilla July 21, 2023

July 21, 2023

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 45564] New: Kolab E14 Client installation fails with "Copy failed"
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

https://bugs.winehq.org/show_bug.cgi?id=45564 Bug ID: 45564 Summary: Kolab E14 Client installation fails with "Copy failed" Product: Wine Version: 3.13 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 61987 --> https://bugs.winehq.org/attachment.cgi?id=61987 Install log with WINEDEBUG=+ntdll,+commctl The installation of the Kolab E14 Client (Groupware based on KDE) fails with "Copy failed" and aborts. The install log including the generation of the Message "Copy failed" is attached. Wine is self-compiled with the patch from bug #45552 created by Fabian Maurer. -- 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 44223] New: FrameMaker 7.2: Console window minimized and not (re) drawn
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

https://bugs.winehq.org/show_bug.cgi?id=44223 Bug ID: 44223 Summary: FrameMaker 7.2: Console window minimized and not (re)drawn Product: Wine Version: 3.0-rc3 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: --- When opening a file in FrameMaker 7.2 which has errors (i.e. missing font, missing cross references), a message window ("Framemaker console", text window with its own window manager decoration) is opened and a message box is created. When this happens the message window is drawn with the least possible size (to allow only the window manager icons to appear) and when enlarging it, its content is not drawn (the content pane shows the content of the underlying window). The message windows content is therefor not readable. Sometimes (not always) the dialog box and the message window are only shown in the panel and are not shown at all (which may be a window manager problem, cannot judge). Any hint to give more helpful details is welcome. -- 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 6

[Bug 47328] New: Steam crashes when loading the Store tab ( Assertion Failed: killing unresponsive browser for URL)
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

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 35701] New: League of Legends: Right click contextual menu on friends list is invisible
by wine-bugs＠winehq.org July 21, 2023

July 21, 2023

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 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 July 21, 2023

July 21, 2023

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