4 ms·

They aren't. This is fanfic Their point is the project that wants Wayland will randomly make changes like this on their Wayland code in such a way that breaks

by __s 1y ago

They aren't. This is fanfic Their point is the project that wants Wayland will randomly make changes like this on their Wayland code in such a way that breaks on X11. They say QTK as a reference to Qt or GTK

doubled112 1y ago
GNOME wants Wayland. Meanwhile (just last week) GTK was broken on Wayland on some older Intel GPUs because of the Vulkan drivers. X11 was spared because the X11 backend still uses OpenGL. Exciting stuff.
- bsder 1y ago
  They also broke XWayland via a Mutter change that clearly wasn't tested at all given how quickly the bug reports started pouring in. https://gitlab.gnome.org/GNOME/mutter/-/issues/4133 https://gitlab.gnome.org/GNOME/mutter/-/issues/4133 So, they don't want you to use X11 AND they don't want to support XWayland properly, either. None of this will get solved until some programmer does something similar to what the Pipewire guy did and rips the whole system down. In this case, probably starting from the assumption of "Vulkan is the base" and building up from there.
- senko 1y ago
  So, a GPU driver broke and that’s Wayland’s fault?
  - doubled112 1y ago
    No, but this time it was only Wayland users who were affected, right? "My applications are empty boxes but only on Wayland."
    - c-hendricks 1y ago
      From what was said in the comment it seems like anything vulkan would have had issues, not just Wayland