On Thu Nov 30 15:33:34 2023 +0000, Yona-TYT wrote:
> I did a little test with the Jagex Launcher to play oldrunescape, but in
> wayland the window is completely black.
> Even so, I was able to execute by guessing where the "Play" button was.
> [JagexLauncherInstaller.exe](https://cdn.jagex.com/Jagex%20Launcher%20Instal…
> x11:
> wayland
From a quick look, the launcher uses CEF (Chromium Embedded Framework). CEF typically uses cross-process rendering which is not supported in the upstream Wayland driver yet.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3909#note_54400
I did a little test with the Jagex Launcher to play oldrunescape, but in wayland the window is completely black.
Even so, I was able to execute by guessing where the "Play" button was.
[JagexLauncherInstaller.exe](https://cdn.jagex.com/Jagex%20Launcher%20Instal…
x11:
wayland
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3909#note_54398
On Thu Nov 30 11:03:15 2023 +0000, Zebediah Figura wrote:
> If you remove the line "_putenv("cat=")" from the test, it fails the
> same way on Windows. This implies that native is detecting when the
> environment has been modified *back* to its initial state and undoing
> the reallocation in that case. That strikes me as a little insane; do we
> care about implementing that behaviour?
I don't see such behavior. Could you please describe in more detail what have you tested (preferably attaching tests diff)? It's unlikely that native restores to initial environment in such case.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4552#note_54383