Announcement

Collapse
No announcement yet.

KDE Plasma 5.13 Is Making Great Improvements On Its Wayland Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by cfeck View Post

    This myth was being discussed everywhere. What Martin said he won't add features to X11 unless the feature also works on Wayland. He did it for two reasons:
    - to have more time to close the feature-gap between X11 and Wayland
    - to not _enlarge_ this gap intentionally

    If you think about it, it makes 100% sense.
    He closed a bug of regarding modifiers, a new feature in Xorg-server 1.20, which will also be used in Wayland, because the Xorg side of Kwin is going to receive no more features

    Comment


    • #32
      Originally posted by starshipeleven View Post
      this is nonsense, qtwayland is a library to build lightweight wayland compositors and to make applications that run as wayland clients, xwayland is a wrapper to run x11/xorg applications on wayland compositors.
      the sense is that xwayland is not necessary for qt.

      Comment


      • #33
        I've tested some games like Tomb Raider and Rise of the Tomb Raider on Plasma-Wayland and the input got much worse, not sure if this is because of a recent Plasma 5.12.x update or maybe libinput 1.10.x. There always was the bug, that you have to press for 3 seconds the ESC key. But now it is nearly impossible to play, the mouse is inaccurate, you cannot move the view freely around in all directions and sometimes the view jumps 180 degree. Before I could play most of the games on Plasma-Wayland at least by pressing the ESC key for 3 seconds or going back to the desktop and then to the game again. So something regressed, did anybody else experience this? Hope that at least some input bugs will be addressed for Plasma-Wayland. Anyway, the desktop works great already on Plasma-Wayland and if there was a bug I could mostly work around them.

        Comment


        • #34
          Originally posted by theriddick View Post
          Had to stop using KDE because of how unfriendly kwin is to nvidia cards, had games unable to detect screen resolution, mouse not obeying designated screen in games, the list kept going on. It wasn't just related to multi-monitor configurations, I even had some games unable to detect 4k with just 1 screen enabled. Tragic!
          My experience is the exact opposite.
          Been using kwin + nVidia on Fedora and RedHat (RH9) since, err, 2000 (?).
          In the last couple of years, beyond a some issue with konsole, I can't remember any issues.
          I've got machines with 4K displays (w/ 1070 and 1080 GTX cards), dual head and even triple head (with older GPUs). Everything simply works.
          Steam / older games work out of the box.

          - Gilboa
          Last edited by gilboa; 04-25-2018, 05:54 AM.
          Devel: Intel S2600C0, 2xE5-2658V2, 32GB, 6x2TB, 1x256GB-SSD, GTX1080, F32, Dell UP3216Q 4K.
          oVirt: Intel S2400GP2, 2xE5-2448L, 96GB, 10x2TB, GTX550, CentOS8.1.
          Win10: Gigabyte B85M-HD3, E3-1245V3, 32GB, 5x1TB, GTX980, Win10Pro.
          Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F32, Dell U2711.
          Laptop: ASUS Strix GL502V, i7-6700HQ, 32GB, 1TB+256GB, 1070M, F32.

          Comment


          • #35
            Originally posted by schmidtbag View Post

            Hmm that's pretty weird. There are a lot of potential factors I can think of that may be causing this issue:
            1. Is Mesa working properly when you use Wayland? I wonder if everything is falling back to CPU rendering.
            2. Maybe your distro doesn't have Wayland properly configured? I personally am using Arch - it might help to reference Arch's wiki, regardless of what distro you use.
            3. Your display manager might be causing problems. I personally use SDDM, since you only have to tweak 1 line in the config file to start a Wayland session.
            4. To my knowledge, Wayland doesn't reference the xorg.conf, but I wonder if maybe having one conflicts with the way it behaves? From my recollection, my KDE setup still has an xorg.conf, but it might be worth deleting yours and see if that helps.
            5. Part of me wonders if maybe you have everything (including Plasma) running in Xwayland?
            6. Maybe you just need to do a fresh clean install. I didn't have to (I was already using my KDE setup for years before I switched to Wayland) but for such a complex system, you're bound to encounter something holding you back.
            Which line do I tweak for Wayland sessions using SDDM? I'm also using SDDM and I have a fresh install.

            Comment


            • #36
              Originally posted by dsreyes1014 View Post
              Which line do I tweak for Wayland sessions using SDDM? I'm also using SDDM and I have a fresh install.
              I don't have my KDE setup in front of me, but from what I recall, you want to edit the "Session" variable in /etc/sddm.conf to use "plasmawayland.desktop". You may have to specify "SessionDir" to use wherever your Wayland sessions are stored (/usr/share/wayland-sessions seems to be the default for most distros). Definitely check that this directory exists first, because some distros have a separate package for it (like Arch).
              To my recollection, SDDM's login screen allows you to manually select if you want to run kwin_wayland, so it may be worth checking that out first, just to test if Wayland is working at all, or at least recognized by SDDM.

              Comment


              • #37
                Originally posted by schmidtbag View Post
                I don't have my KDE setup in front of me, but from what I recall, you want to edit the "Session" variable in /etc/sddm.conf to use "plasmawayland.desktop". You may have to specify "SessionDir" to use wherever your Wayland sessions are stored (/usr/share/wayland-sessions seems to be the default for most distros). Definitely check that this directory exists first, because some distros have a separate package for it (like Arch).
                To my recollection, SDDM's login screen allows you to manually select if you want to run kwin_wayland, so it may be worth checking that out first, just to test if Wayland is working at all, or at least recognized by SDDM.

                So I can use a Wayland session and kwin_wayland is being used but I still cant close a window without it crashing on any of my PCs. Wonder if it's the window theme.

                EDIT: Turns out it's the breezemite theme that crashes.
                Last edited by dsreyes1014; 04-25-2018, 06:10 PM.

                Comment


                • #38
                  Originally posted by starshipeleven View Post
                  Windows isn't using Wayland though.
                  You think i do not know that? Point is that windows does compositing fast and linux (be it wayland or x11 or whatever) does not. Why not? This is not acceptable.

                  Originally posted by schmidtbag View Post
                  What hardware are you using and with what drivers? My Haswell-based laptop runs KDE+Wayland very smoothly.
                  I've heard how setting the rendering backend to OpenGL 2.0 (instead of 3.1) can help improve performance.
                  kaby lake cpu here, rx 580 + amdgpu. Will try OpenGL 2.0, thanks for the tip.

                  By the way it is not unusably slow. It is perfectly usable. Thing is windows+compositing is exactly as fast as linux+no-compositing.

                  Comment


                  • #39
                    Originally posted by bitman View Post
                    kaby lake cpu here, rx 580 + amdgpu. Will try OpenGL 2.0, thanks for the tip.

                    By the way it is not unusably slow. It is perfectly usable. Thing is windows+compositing is exactly as fast as linux+no-compositing.
                    It wouldn't surprise me if you're doing CPU rendering. I've found KDE+xrender compositing is modestly fast, even on slow single-core CPUs, but it is strictly CPU rendering. I don't know of a good way to prove if you're getting GPU-accelerated Wayland, but you may want to look into that too.

                    Comment

                    Working...
                    X