https://bugs.winehq.org/show_bug.cgi?id=48376
Bug ID: 48376 Summary: wineserver crash with wine-staging 5.0-rc3 + vsyscall32 patch in League of Legends. Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs@winehq.org Reporter: atbjyk@protonmail.com CC: dimesio@earthlink.net, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
Created attachment 66129 --> https://bugs.winehq.org/attachment.cgi?id=66129 WINEDEBUG=+event,+cursor,+dinput,+rawinput,+message,+x11drv,+synchronous,+winediag
I have saw "wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart."
I have tested staging 5.0-rc3 commit c6758042044b391eccc930027197766b8bfbd80b + lol patch from (https://bugs.winehq.org/show_bug.cgi?id=47198 required rebuild glibc or disable vsyscall32) I used vsyscall32 one.
and revert few commit from staging makes does not crash. (please see my repo https://github.com/yuiiio/wine/commits/staging-lol)
https://bugs.winehq.org/show_bug.cgi?id=48376
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|wine-packages |-unknown CC| |leslie_alistair@hotmail.com | |, z.figura12@gmail.com Product|Packaging |Wine-staging Version|unspecified |5.0-rc3
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net --- Obviously not a packaging bug, since you say you patched it yourself. Plus, the rc3 staging packages aren't even in the WineHQ repository yet.
https://bugs.winehq.org/show_bug.cgi?id=48376
--- Comment #2 from atbjyk atbjyk@protonmail.com --- Sorry misstate
https://bugs.winehq.org/show_bug.cgi?id=48376
atbjyk atbjyk@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Wine Component|-unknown |-unknown Version|5.0-rc3 |unspecified
https://bugs.winehq.org/show_bug.cgi?id=48376
atbjyk atbjyk@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|wineserver crash with |wineserver crash with |wine-staging 5.0-rc3 + |wine-staging + vsyscall32 |vsyscall32 patch in League |patch in League of Legends. |of Legends. |
https://bugs.winehq.org/show_bug.cgi?id=48376
--- Comment #3 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Can you confirm, this issue occurs with plain wine-staging? The repo links to proton and not wine-staging. These two projects have different patchsets applied.
https://bugs.winehq.org/show_bug.cgi?id=48376
--- Comment #4 from atbjyk atbjyk@protonmail.com --- my staging-lol branch is wine-5.0rc3(fa97cbdf14883fb301dcc0a5264369f8ed184182) + all staging patch (commit id is above comment. I only changed commit comment because github makes reference to each issue page and this ``` --- a/patches/ntdll-ThreadHideFromDebugger/0001-ntdll-Stub-NtQueryInformationThread-ThreadHideFromDe.patch +++ b/patches/ntdll-ThreadHideFromDebugger/0001-ntdll-Stub-NtQueryInformationThread-ThreadHideFromDe.patch @@ -16,13 +16,12 @@ index b913326f796..840b8ffd0b1 100644 } return status; + case ThreadHideFromDebugger: -+ if (length != sizeof(char)) return STATUS_INFO_LENGTH_MISMATCH; ++ if (length != sizeof(BOOLEAN)) return STATUS_INFO_LENGTH_MISMATCH; + *(BOOLEAN *)data = TRUE; + if (ret_len) *ret_len = sizeof(BOOLEAN); + return STATUS_SUCCESS; case ThreadPriority: case ThreadBasePriority: case ThreadImpersonationToken: ``` )
I have crash at "add leagueoflolfix.patch" commit and not crash at Revert "winex11.drv: Listen to RawMotion and RawButton* events in the desktop thread." commit
https://bugs.winehq.org/show_bug.cgi?id=48376
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- If you're encountering bugs only with a patch that's not part of Wine or Wine-Staging, that's outside the scope of this bug tracker. You'll have to contact the patch author or debug it yourself.
https://bugs.winehq.org/show_bug.cgi?id=48376
atbjyk atbjyk@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #6 from atbjyk atbjyk@protonmail.com --- I had to care vsyscall patch affect this. and understand vsyscall patch isn't staging or wine code. If I can reproduce it other than lol, I report again in another bug report. so delete this. sorry for losing your time.
https://bugs.winehq.org/show_bug.cgi?id=48376
--- Comment #7 from atbjyk atbjyk@protonmail.com ---
more note I think vsyscall32 patch resolve "crash after champion select" so I have to test "nomal" wine-staging. If crash "before" champion select , then bug is in staging.
https://bugs.winehq.org/show_bug.cgi?id=48376
--- Comment #8 from atbjyk atbjyk@protonmail.com --- but this bug is happen when exit game-client. so need vsyscallpatch to reproduce this wineserver crash.
lol launch launcher-client window -> select champ -> open game-client window -> close game-client window -> close launcher-client window.
https://bugs.winehq.org/show_bug.cgi?id=48376
--- Comment #9 from atbjyk atbjyk@protonmail.com ---
After pressing the close window button and forcing alt-tab to focus on a window that is not yet closed, a crash occurs.
There is a time lag between pressing the window close button and the window actually closing.
in this case window is client-window
https://bugs.winehq.org/show_bug.cgi?id=48376
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv@dawncrow.de
--- Comment #10 from André H. nerv@dawncrow.de --- closing invalid
https://bugs.winehq.org/show_bug.cgi?id=48376
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |5.0-rc3 CC| |focht@gmx.net