Going all-in on a Wayland future
blogs.kde.org
Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.

cross-posted from: https://lemmy.world/post/39342270

Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.

  • yaslam0x1@lemmy.world
    1·
    2 hours ago

    I do like Wayland but it still has some issues that are annoying:

    • When using remote input solutions (e.g InputLeap) you have to approve the input capture, and you need a mouse and keyboard connected to the PC to do that, making it kind of pointless.

    • Remote desktop also requires the same thing, like, what if I don’t have a mouse & keyboard attached? What if it is a PC you are accessing from another country? You can’t just fly back to approve the remote desktop request.

    This needs to get fixed ASAP in my opinion, since people do need these tools and sometimes you can’t connect a mouse & kb to the PC to just approve the request.

    • ApertureUA@lemmy.today
      3·
      1 hour ago

      If your user is in the input group (set up in pretty much every distro), you can use uinput over netcat for forwrading devices (display server agnostic) without extra privileges. Same with the video group. No idea if anyone used this in an actual software suite tho.