Re: [PATCH 0/1] MR6438: winewayland: Delay setting user driver functions.

[Rémi Bernon (＠rbernon)]

Rémi Bernon (@rbernon) commented about dlls/winewayland.drv/wayland.c:
>  /* We need two roundtrips. One to get and bind globals, one to handle all
>   * initial events produced from registering the globals. */
>  wl_display_roundtrip_queue(process_wayland.wl_display, process_wayland.wl_event_queue);
>  wl_display_roundtrip_queue(process_wayland.wl_display, process_wayland.wl_event_queue);

The issue, is that as far as I understand (which may not be correct), this will trigger the display device initialization, which eventually calls the `output_done` handler which calls back into win32u through `wayland_output_done` > `maybe_init_display_devices`.

It may look, or actually be, harmless for now, but I think it's asking for trouble later, and drivers shouldn't do anything without their callbacks in place. You will need to better describe how and why this segfaults, and try to find a different solution.