<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Wayland backend depends on ordering of globals in the display server" href="https://bugzilla.gnome.org/show_bug.cgi?id=719819#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Wayland backend depends on ordering of globals in the display server" href="https://bugzilla.gnome.org/show_bug.cgi?id=719819">bug 719819</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>Created <a href="attachment.cgi?id=303512&action=diff" name="attach_303512" title="libwayland-server patch shuffling globals order">attachment 303512</a> <a href="attachment.cgi?id=303512&action=edit" title="libwayland-server patch shuffling globals order">[details]</a> <a href='review?bug=719819&attachment=303512'>[review]</a> libwayland-server patch shuffling globals order Attaching a patch that can be applied to the upstream wayland repository. It'll cause globals to be sent in a random order every time a wl_registry is retrieved by the client. With these patches GTK+ seems to be able to start without a problem even with this patch applied. The question though is what globals should be required for GTK+ to succeed. Now it'll just continue even if it didn't receive any globals (even wl_shm), instead probably failing in other places. While wl_compositor, wl_subcompositor, wl_shm, wl_seat, wl_data_device and xdg_shell are more or less required, wl_output may not be there during startup due to hot plugging or other reasons. So, what globals should be required for initialization to succeed?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>