March 2023 - Wine-Bugs - list.winehq.org

[Bug 54755] App jamming: Clicking on the zoom email meeting button causes the app to jam

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54755 --- Comment #1 from 399989567(a)qq.com --- Created attachment 74252 --> https://bugs.winehq.org/attachment.cgi?id=74252 Figure 2 -- 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.

March 30, 2023

[Bug 54755] App jamming: Clicking on the zoom email meeting button causes the app to jam

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54755 399989567(a)qq.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |blocker Priority|P2 |P1 -- 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.

March 30, 2023

[Bug 54755] New: App jamming: Clicking on the zoom email meeting button causes the app to jam

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54755 Bug ID: 54755 Summary: App jamming: Clicking on the zoom email meeting button causes the app to jam Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- Created attachment 74251 --> https://bugs.winehq.org/attachment.cgi?id=74251 Figure 1 Join the zoom meeting( how to apply and join the zoom meeting can refer to: # Bug 54754 ) According to "Figure 1" and "Figure 2" can trigger the bug, resulting in the whole application stuck, the following is an err log > 0024:err:virtual:virtual_setup_exception stack overflow 1220 bytes in thread 0024 addr 0x7bc24170 stack 0x120b3c (0x120000-0x121000-0x220000) -- 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.

March 30, 2023

[Bug 54754] zoom history meeting window 90% chance of not popping up properly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54754 --- Comment #1 from 399989567(a)qq.com --- # Bug 54754 -- 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.

March 30, 2023

[Bug 54754] zoom history meeting window 90% chance of not popping up properly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54754 399989567(a)qq.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major -- 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.

March 30, 2023

[Bug 54754] New: zoom history meeting window 90% chance of not popping up properly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54754 Bug ID: 54754 Summary: zoom history meeting window 90% chance of not popping up properly Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- Created attachment 74250 --> https://bugs.winehq.org/attachment.cgi?id=74250 Image 1 The window circled by the red box in "Image 1" does not pop up properly. Steps to reproduce: 1. Because this is a historical meeting window, you need to have joined a zoom meeting in advance. zoom meetings can be applied for free on their website. 2. After joining the meeting and leaving the meeting, an arrow will appear where you enter the meeting number, click the arrow to bring up the window and trigger the bug. Download zoom at: https://zoom.us/DOWNLOAD Some of my research, when the problem pop-up window received the message clientmessage, but the window style is 86000000, not the problem is 96000000, I think this can be used as an entry point to fix the bug. You can look at this function: handle_wm_protocols -- 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.

March 30, 2023

[Bug 54753] stdout/cout do not respect console code page in apps compiled with mingw-w64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54753 --- Comment #2 from Robert T <rjtulloh(a)gmail.com> --- Created attachment 74249 --> https://bugs.winehq.org/attachment.cgi?id=74249 Program output in Wine. -- 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.

March 30, 2023

[Bug 54753] stdout/cout do not respect console code page in apps compiled with mingw-w64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54753 --- Comment #1 from Robert T <rjtulloh(a)gmail.com> --- Created attachment 74248 --> https://bugs.winehq.org/attachment.cgi?id=74248 Program output in Windows cmd. -- 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.

March 30, 2023

[Bug 54753] New: stdout/cout do not respect console code page in apps compiled with mingw-w64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54753 Bug ID: 54753 Summary: stdout/cout do not respect console code page in apps compiled with mingw-w64 Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: rjtulloh(a)gmail.com Distribution: --- Created attachment 74247 --> https://bugs.winehq.org/attachment.cgi?id=74247 Test program which outputs to the console in different ways. I noticed some cases recently where Wine seemed to ignore the console code page when apps were writing to stdout. Upon further investigation, I found it seems to be specific to apps compiled via mingw64. I've attached a simple test program which demonstrated the issue. It switching the code page to UTF8 and then outputs some Japanese glyphs in different ways. On Windows, this program behaves as expected - the same string is printed for times.The output does not differ based on the compiler used. In Wine, if the program is compiled with mingw-w64, it will output gibberish 3 times, and the correct string is only produced by calling the WriteConsoleA function. This seems to be specific to the way mingw implements stdout, as if the application is compiled with clang in MSVC compatibility mode, there is no issue with the output. It does not seem to be a mingw bug, since the output is correct on Windows. -- 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.

March 30, 2023

[Bug 54752] RUN Moldex3D Viewer will Crash, Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54752 alarmchang <alarmchang(a)moldex3d.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alarmchang(a)moldex3d.com -- 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.

March 30, 2023