For me AutoKey is absolutely essential to my workflow. I have tons of text expansions and shortcuts to “remap” keys. E.g., respectively, typing dAt expands into 2025-05-08, 13:47:40 CEST, and pressing alt + k simulates the arrow down key.

Secondly there’s XScreenSaver which has so many wonderful (mathematical) visualizations that it would be a damn shame if these eventually get lost as Wayland gets more adoption.

None of these have Wayland alternatives as far as I know. For text expansion there’s Espanso, but it doesn’t support keyboard shortcuts yet.

  • ᕙ(⇀‸↼‶)ᕗ
    link
    fedilink
    21 month ago

    x11

    i am not gonna go with any of the idiotchanges. lost me at systemd, flatpaks and so on

    moronic people like lennard poettering and everyone at red hat are a desease.

    i will start downgrading Iinux PCs to Windows10 just to not have any of the broken linux promises.

    do ONE thing but do it right.

      • @[email protected]
        link
        fedilink
        21 month ago

        RHEL10 is probably a month away from being the first distro to ship without even the option of using Xorg. It is not even going to be in the repos.

        Other distros will follow their lead.

        If you are a fan of x11, not liking Red Hat makes sense.

  • @[email protected]
    link
    fedilink
    81 month ago

    The inability to roll windows up into just the title bar, or to get Firefox to place each of its windows on the same virtual desktop as before, are major annoyances. Otherwise, Wayland runs better than I expected.

  • Gamma
    link
    fedilink
    English
    5
    edit-2
    1 month ago

    autokey

    I accomplish the same thing with compose sequences, and by binding a keyboard shortcut in my desktop to call a script with wtype. It’s not a cross-compositor solution though, as you’d have to manually setup binds in each of them.

    I don’t see much hope for this one-to-one unfortunately.

      • @[email protected]
        link
        fedilink
        11 month ago

        Only new version default wayland, my version not. And not update. Until shell restart on wayland, not use wayland.

  • @[email protected]
    link
    fedilink
    31 month ago

    Couldn’t use xset to manually set some monitors to standby So I searched how to change it back to X.

    Also you couldn’t set display variable to another computer’s ip address (a windows one running xming)

    • @[email protected]
      link
      fedilink
      41 month ago

      There are still some quirks but it’s been generally fine for me with Nvidia, almost a year now.

      • beleza pura
        link
        fedilink
        21 month ago

        i heard about that. sadly my gpu is so old the latest driver that supports it is the 470 driver

        • @[email protected]
          link
          fedilink
          31 month ago

          Hey, I’m in the same boat. Gigabyte GTX 670. Wayland was a sluggish mess, and same goes for nouveau with X11.

          I bit the bullet after eight months of running Arch like this, and experimenting around with newer iGPUs in laptops, and bought a new radeon finally. Time to retire this ancient piece of tech.

          • @[email protected]
            link
            fedilink
            21 month ago

            670 is still better than nothing.

            Hopefully it can find its way to someone else’s home on the cheap and still give them plenty of years of fun.

        • @[email protected]
          link
          fedilink
          21 month ago

          Well, you can hold onto that GPU for a little longer with X11. But it seems you’ll need an upgrade some time later. Though if you don’t game (aside from FOSS ones), Nouveau driver should do the job for your daily needs. However, it still needs time for Wayland.

          • beleza pura
            link
            fedilink
            1
            edit-2
            1 month ago

            the nouveau driver works fine except when it crashes for no clear reason after some hours of usage

            • @[email protected]
              link
              fedilink
              11 month ago

              Even on X11? I tried it on Wayland months ago to see its state and it was generally fine except gaming. Though the results still might depend on the card in use I guess.

              • beleza pura
                link
                fedilink
                11 month ago

                Even on X11?

                yup. i think it had something to do with video calls or screen sharing, which are essential at work

                • @[email protected]
                  link
                  fedilink
                  11 month ago

                  That makes sense. Nouveau isn’t mature for some use cases yet, even though they made a huge jump with NVK. Hardware upgrade might be closer than you think then.

  • Jerkface (any/all)
    link
    fedilink
    English
    31 month ago

    Every time I build a new box or do an upgrade, I try selecting Plasma on Wayland from the login screen. Every time it doesn’t work, I select X11, and never think of it again for another six months to two years.

  • @[email protected]
    link
    fedilink
    1
    edit-2
    1 month ago

    I’m using Wayland right now, but tentatively.

    Right now there’s an issue in WoW where sometimes when I move my mouse and left-click, the camera jumps to a different position, usually trying to look up.

    Only happens on Wayland and it’s fixed temporarily by switching between windowed and fullscreen mode. The problem comes back sometimes when alt-tabbing and refocusing the game.

    There was a bug in KDE recently where some menus weren’t properly appearing on Wayland, but that seems to have been fixed after my latest update.