Curious from people who follow its development closely.

  • What protocol are about to be finally implemented?
  • Which ones are still a struggle?
  • How many serious protocols are there missing?

https://arewewaylandyet.com/

  • interdimensionalmeme
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    My first experience in wayland, us discovering I couldn’t control monitor sleep/standby function. I found how to reinstall X and managed to escape it since.

    • azvasKvklenko@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      ·
      7 months ago

      That sounds like problem with specific software configuration, like missing packages in some distro or something being badly built. There’s nothing about Wayland that would prevent it from working.

      • interdimensionalmeme
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        Tried xset, not compatible. Tried searching equivalent command, there was none. That was in 2022.

        • azvasKvklenko@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          7 months ago

          Wayland is not a standalone server like Xorg and it doesn’t have standard utilities to control stuff like DPMS. That functionality goes to compositors that are effectively individual Wayland server implementations. Compositors can provide utilities to control display, and they usually do. For example, on KDE Wayland you can call kscreen-doctor --dpms off, wlroots compositors (Sway, Wayfire, Hyprland,…) have inter-compatible tools, like swaymsg output DP-1 dpms off. If that’s what you meant anyway.

          • interdimensionalmeme
            link
            fedilink
            arrow-up
            1
            ·
            7 months ago

            There really should be a front end script that has uniform command line parameters, finds what your compositor is, translate the command line arguments and send them.

    • boredsquirrel@slrpnk.net
      link
      fedilink
      arrow-up
      4
      ·
      7 months ago

      I dont know what that means. Normally the monitor turns off when the PC stops sending a signal. In KDE i can easily configure when to dim, turn off, lock etc. the screen.

      • interdimensionalmeme
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        I needed to do that from the console, xset didn’t work. As far as I could tell there was no other command.

            • boredsquirrel@slrpnk.net
              link
              fedilink
              arrow-up
              1
              ·
              7 months ago

              What does this mean? Like unplugging without unplugging? Keeping one screen active and only turning off the other one?

              I mean in the KDE monitor options I can choose [mirror,extend to left,extend to right,only external,only internal] so this is 100% possible.

                • boredsquirrel@slrpnk.net
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  edit-2
                  7 months ago

                  This will be possible and likely available as a command for your specific compositor. What are you using?

                  • interdimensionalmeme
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    edit-2
                    7 months ago

                    It was the one that came default with ubuntu 22.10 But as I have stated in my initial post, the feature had been restored by reinstalling Xwindow Also, I feel that the commands equivalent to

                    xset dpms force off
                    xset dpms force standby
                    xset dpms force suspend
                    

                    Should be the same regardless which wayland variant you are using.