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

[Bug 57698] Reason's (DAW) dialog windows stopped registering mouse events and open at screen's right edge

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57698 --- Comment #2 from schroedingerscat(a)disroot.org --- Can confirm, thank you! -- 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.

Jan. 22, 2025

[Bug 57711] The 32-bit wpcap program has a stack leakage issue

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57711 mushu <csumushu(a)126.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from mushu <csumushu(a)126.com> --- (In reply to Hans Leidekker from comment #5) > (In reply to mushu from comment #4) > > (In reply to Hans Leidekker from comment #3) > > > (In reply to mushu from comment #2) > > > > (In reply to Hans Leidekker from comment #1) > > > > > Created attachment 77914 [details] > > > > > patch > > > > > > > > > > Can you try this patch? > > > > > > > > This patch resolves the issue. Could you explain how this problem came > > > > about? Why do 32-bit and 64-bit programs exhibit different behaviors? > > > > > > We used the wrong calling convention (CALLBACK maps to 32-bit only > > > __stdcall). It's ignored when building 64-bit, that's why it worked there. > > > > I understand the reason for the behavioral differences between x64 and x32: > > __stdcall is ignored in ARM and x64 architectures. However, why is __stdcall > > considered the wrong calling convention? I noticed that many parts of the > > Wine source code use it. > > The callback argument to pcap_loop() (pcap_handler) isn't defined as > __stdcall in pcap.h. I got it.Thank you. -- 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.

Jan. 22, 2025

[Bug 57711] The 32-bit wpcap program has a stack leakage issue

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57711 --- Comment #5 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to mushu from comment #4) > (In reply to Hans Leidekker from comment #3) > > (In reply to mushu from comment #2) > > > (In reply to Hans Leidekker from comment #1) > > > > Created attachment 77914 [details] > > > > patch > > > > > > > > Can you try this patch? > > > > > > This patch resolves the issue. Could you explain how this problem came > > > about? Why do 32-bit and 64-bit programs exhibit different behaviors? > > > > We used the wrong calling convention (CALLBACK maps to 32-bit only > > __stdcall). It's ignored when building 64-bit, that's why it worked there. > > I understand the reason for the behavioral differences between x64 and x32: > __stdcall is ignored in ARM and x64 architectures. However, why is __stdcall > considered the wrong calling convention? I noticed that many parts of the > Wine source code use it. The callback argument to pcap_loop() (pcap_handler) isn't defined as __stdcall in pcap.h. -- 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.

Jan. 22, 2025

[Bug 57712] Install of winehq-stable over winehq-staging doesn't remove all staging packages

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57712 Mitch Claborn <mitch(a)claborn.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mitch(a)claborn.net -- 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.

Jan. 22, 2025

[Bug 57712] New: Install of winehq-stable over winehq-staging doesn't remove all staging packages

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57712 Bug ID: 57712 Summary: Install of winehq-stable over winehq-staging doesn't remove all staging packages Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: mitch(a)claborn.net CC: dimesio(a)earthlink.net Distribution: --- Ubuntu 24.04 Wine 10 I installed winehq-stable over winehq-staing. The install removed the winehq-package but did not remove wine-staging wine-staging-amd64 wine-staging-i386:i386 -- 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.

Jan. 22, 2025

[Bug 57711] The 32-bit wpcap program has a stack leakage issue

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57711 --- Comment #4 from mushu <csumushu(a)126.com> --- (In reply to Hans Leidekker from comment #3) > (In reply to mushu from comment #2) > > (In reply to Hans Leidekker from comment #1) > > > Created attachment 77914 [details] > > > patch > > > > > > Can you try this patch? > > > > This patch resolves the issue. Could you explain how this problem came > > about? Why do 32-bit and 64-bit programs exhibit different behaviors? > > We used the wrong calling convention (CALLBACK maps to 32-bit only > __stdcall). It's ignored when building 64-bit, that's why it worked there. I understand the reason for the behavioral differences between x64 and x32: __stdcall is ignored in ARM and x64 architectures. However, why is __stdcall considered the wrong calling convention? I noticed that many parts of the Wine source code use it. -- 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.

Jan. 22, 2025

[Bug 57597] Rufus: Incorrect display of bitmap in buttons

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57597 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- 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.

Jan. 22, 2025

[Bug 57607] wineserver: crashes with ntdll:reg test with pre-existing HCU\WineTest\subkey

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57607 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- 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.

Jan. 22, 2025

[Bug 54752] RUN Moldex3D Viewer will Crash

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54752 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- 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.

Jan. 22, 2025

[Bug 37297] CreateEdit windows always fullscreen under wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=37297 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- 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.

Jan. 22, 2025