Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ubuntu 18.04 LTS Will Default To The X.Org Stack, Not Wayland (phoronix.com)

Posted by msmash on from the tough-calls dept.

An anonymous reader writes: Five years after their original goal to ship Ubuntu with Wayland, Ubuntu 17.10 transitioned to using the Wayland display system by default as part of their transition to GNOME Shell as the default desktop. But with the upcoming Ubuntu 18.04 LTS release, Canonical has decided to transition back to the X.Org Server. Their reasoning for moving to an X.Org Server by default is better support for screen sharing, remote desktop, and better recovery from crashes. But for those interested the Wayland session will still be available as a log-in option.

7 of 194 comments (clear)

  1. See Saw Cycles of Adoption and Abandonment by CRB9000 · · Score: 2, Interesting

    Really, these things swing back and forth and really is a non-news item. The headline should be changed to read: Defaults to X.org Allows Choice of Wayland. Which is not really newsworthy.

    In other words, "Meh."

    1. Re:See Saw Cycles of Adoption and Abandonment by chill · · Score: 3, Interesting

      This is called the Tyranny of the Default, and is a real thing.

      --
      Learning HOW to think is more important than learning WHAT to think.
    2. Re:See Saw Cycles of Adoption and Abandonment by Fly+Swatter · · Score: 4, Interesting

      A vendor in it for money chooses to backtrack and default away from the new and shiny. I don't think that is about choice and a hell of a lot more about what they think of the current state of Wayland.

  2. Why switch to Wayland in the first place? by halivar · · Score: 3, Interesting

    Despite it's touted simplicity, Wayland lags behind X functionality in both network awareness and driver support, as well as still a slight lag in performance despite its purported closeness to the hardware compared to X. Am I misunderstanding something?

  3. gnome-shell wayland disaster by Anonymous Coward · · Score: 3, Interesting

    The shit is a total clusterfuck with Wayland. Something happens to gnome-shell--REBOOT. Some random gnome-shell plugin acts bad, no way to unload it--REBOOT. Mouse stops working--REBOOT. Come back from screen lock and clicks don't work--REBOOT.

    All of this shit is possible to completely fix non-destructively when gnome-shell runs under X by Alt-F2 'r', or lacking input, Ctrl-Alt-F1 'killall -HUP gnome-shell'.

    Now Alt-F2 'r' is disabled, and every other previously working solution causes EVERYTHING to be killed, because now gnome-shell is the parent of the entire session. The gnome-shell developers have basically said tough, this is intended operation, and you shouldn't need to restart the shell ever. Fuck them. I leave my workstation powered up for months on end, yet I have to restart gnome-shell it seems every week or two sometimes.

  4. Re:But but .... by jbernardo · · Score: 3, Interesting

    I know of that workaround, but it is all it is, a workaround. The fact that you need it in Wayland is a consequence of its lack of support for running GUI apps as root. And it won't work for native apps,only for X apps.

  5. Re:But but .... by serviscope_minor · · Score: 3, Interesting

    x host si:localuser:root

    was all I meeded

    So all you needed to get Wayland to work properly was... X.

    --
    SJW n. One who posts facts.