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

[Bug 58765] New: Wine Internet explorer: Flash plugin not working

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58765 Bug ID: 58765 Summary: Wine Internet explorer: Flash plugin not working Product: Wine Version: unspecified Hardware: x86-64 OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tomislav.budor(a)lovatoelectric.hr Created attachment 79409 --> http://bugs.winehq.org/attachment.cgi?id=79409 screenshot Flash plugin not working -- 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.

Oct. 8, 2025

[Bug 57866] Missing pages tree in Wine internet explorer, not show tree menu in the some interactive animation

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57866 tmslv32 <tomislav.budor(a)lovatoelectric.hr> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Missing pages tree |Missing pages tree in Wine | |internet explorer, not show | |tree menu in the some | |interactive animation -- 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.

Oct. 8, 2025

[Bug 57866] Missing pages tree

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57866 --- Comment #2 from tmslv32 <tomislav.budor(a)lovatoelectric.hr> --- Created attachment 79408 --> http://bugs.winehq.org/attachment.cgi?id=79408 screenshot -- 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.

Oct. 8, 2025

[Bug 57866] Missing pages tree

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57866 --- Comment #1 from tmslv32 <tomislav.budor(a)lovatoelectric.hr> --- Created attachment 79407 --> http://bugs.winehq.org/attachment.cgi?id=79407 screenshot -- 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.

Oct. 8, 2025

[Bug 58764] Missing pages tree in .chm HTML help viewer

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58764 --- Comment #1 from tmslv32 <tomislav.budor(a)lovatoelectric.hr> --- Created attachment 79406 --> http://bugs.winehq.org/attachment.cgi?id=79406 screenshot of helper -- 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.

Oct. 8, 2025

[Bug 58764] New: Missing pages tree in .chm HTML help viewer

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58764 Bug ID: 58764 Summary: Missing pages tree in .chm HTML help viewer Product: Wine Version: unspecified Hardware: x86-64 OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tomislav.budor(a)lovatoelectric.hr Created attachment 79405 --> http://bugs.winehq.org/attachment.cgi?id=79405 screenshot of .chm helper Missing pages tree in .chm HTML help viewer i ReactOS. -- 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.

Oct. 8, 2025

[Bug 58755] 16-bit applications crash under new wow64 on some processors

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58755 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|16 bit SkiFree does not |16-bit applications crash |work under wow64 |under new wow64 on some | |processors -- 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.

Oct. 8, 2025

[Bug 58755] 16 bit SkiFree does not work under wow64

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58755 --- Comment #10 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Zeb Figura from comment #9) > * 94447cee61 is supposed to catch broadly this. It doesn't catch the unix > call case (or the syscall case) because it tries to read the faulting > instruction with virtual_handle_fault(), but here the faulting instruction > isn't in a PE module. We can special-case those safely, I think. I've submitted 9122 for this. > * 94447cee61 *does*, as one might predict, catch the case I mentioned where > we fault in wow64cpu.dll. However the game still doesn't launch, and I'm not > sure why. I see a subsequent SEGV from the game doing an int21, but for some > reason that exception doesn't seem to even reach the PE side of ntdll. Scratch this, I was somehow on an old branch despite what I thought. This part works fine with upstream 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.

Oct. 7, 2025

[Bug 58755] 16 bit SkiFree does not work under wow64

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58755 --- Comment #9 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Zeb Figura from comment #8) > I actually ended up partially debugging this. The problem is that Wine > sometimes does WCB16_REGS calls with a zeroed context, so it sets zero %fs > and %gs. Some CPUs crash when %gs is zero even in 64-bit mode, mine included. Okay, it's more complicated than that. It turns out: * the kernel lies to us: FS_sig and GS_sig are always zero in an exception, but that's not their real values. This threw me off. * %gs being zero is fine actually; in fact it seems to be zero to start out with. The problem is that clearing %gs, in some processors, also seems to clear gsbase. This is observed in the ntdll:exception tests. * %gs is cleared when calling into 16-bit code. Its previous value is restored when calling back into 32-bit code, which we do before doing any syscalls or unix calls, but this doesn't help, because this either doesn't affect gsbase, or clears it again. [Plus, the previous value was zero for me.] * 94447cee61 is supposed to catch broadly this. It doesn't catch the unix call case (or the syscall case) because it tries to read the faulting instruction with virtual_handle_fault(), but here the faulting instruction isn't in a PE module. We can special-case those safely, I think. * 94447cee61 *does*, as one might predict, catch the case I mentioned where we fault in wow64cpu.dll. However the game still doesn't launch, and I'm not sure why. I see a subsequent SEGV from the game doing an int21, but for some reason that exception doesn't seem to even reach the PE side of ntdll. -- 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.

Oct. 7, 2025

[Bug 58755] 16 bit SkiFree does not work under wow64

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58755 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #8 from Zeb Figura <z.figura12(a)gmail.com> --- I actually ended up partially debugging this. The problem is that Wine sometimes does WCB16_REGS calls with a zeroed context, so it sets zero %fs and %gs. Some CPUs crash when %gs is zero even in 64-bit mode, mine included. With debugging, this happens at the second instruction of the unix call dispatcher, which loads from %gs. Without debugging, it still crashes, this time in the process of trying to call NtSetLdtEntries() called from InitTask(). On my machine it doesn't actually crash in the syscall dispatcher, but rather when loading the TEB in free_temp_data() called from Wow64SystemServiceEx(), which my compiler for some reason decides to do before calling wow64_syscall(). The effect is the same. What's confusing is that we shouldn't have a cleared %gs in 32-bit code, because we save and restore the 32-bit %gs when calling into and out of 16-bit code. I'm not sure what's going wrong with that mechanism. -- 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.

Oct. 7, 2025