Announcement

Collapse
No announcement yet.

KDE Plasma 5.24 Released With Wayland Support In Increasingly Great Shape

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

  • #41
    Great news about the improved Wayland monitor support. Ill have to re-evaluate Plasma Wayland now.

    Should 5.24 make it into Kubuntu 22.04?

    Comment


    • #42
      The narrative since KDE 5.21 has been "Wayland is now great". It's about thime that they (or Phoronix) found a new gimmick to boost for clicks.

      Comment


      • #43
        Does anyone know why the Titlebar application icons are hit and miss in Wayland... i.e. some applications display the generic wayland app icons, while others display their respective app icon correctly. One example is Firefox vs. Firefox nightly. On Fedora Fx using wayland, the app icon is correct - using Nightly, it's the generic wayland icon. Chome starts out using the chrome icon but then eventually switches over to the generic icon. Is this an app specific issue or is it something with Wayland?

        Comment


        • #44
          Originally posted by danboid View Post
          Should 5.24 make it into Kubuntu 22.04?
          OMGUbuntu says it will:-
          Using Kubuntu? You can look forward to trying KDE Plasma 5.24 (or a later revision) in Kubuntu 22.04 in April, though keep an eye on the Kubuntu backports PPA in the meantime as it may let you upgrade to Plasma 5.24 on Kubuntu 21.10.

          Comment


          • #45
            Originally posted by gbcox View Post
            Does anyone know why the Titlebar application icons are hit and miss in Wayland... i.e. some applications display the generic wayland app icons, while others display their respective app icon correctly. One example is Firefox vs. Firefox nightly. On Fedora Fx using wayland, the app icon is correct - using Nightly, it's the generic wayland icon. Chome starts out using the chrome icon but then eventually switches over to the generic icon. Is this an app specific issue or is it something with Wayland?
            This seems to be a general issue with setting desktop icons, up the .desktop file properly and setting a proper wmclass.
            For Mozilla the bug is there: https://bugzilla.mozilla.org/show_bug.cgi?id=1530052 (fixed January 28 2022, so should be fixed in firefox 98)

            Other applications suffer the same issue, KDE has porting guidelines for fixing that for KDE apps (https://community.kde.org/Guidelines...plication_Icon), but the applications will have to properly and consistently set that, quote from the HOWTO:

            On Wayland setWindowIcon() no longer works. This also means that currently is not possible to set a per-window icon (because the xdg-shell standard doesn't allow it). It is still possible to set the main application icon that will be shown in task managers and window decorations:
            • The name of the application icon will be fetched from the .desktop file of the application.
            • The name of the .desktop file must adhere to the reverse domain standard (e.g. org.kde.app.desktop).

            Most of the KDE applications are already working fine because KAboutData takes care of all the necessary steps. If for some reason your application is not using KAboutData, you need to manually call QGuiApplication::setDesktopFileName().
            So that's simply different from X11, and I guess some applications don't do that "properly" for Wayland (yet) and try to set the icon the X11 way.

            Comment


            • #46
              as long as kde devs close reports on huge breaking bugs with WONTFIX because the bug technically is in qt, even though kde maintains its own big patch set for qt, I ain't ever touching that again.

              Comment


              • #47
                I was hoping the Dolphin "Open With" being unreliable would be fixed by the final. It stopped working reliably when I updated to the 5.24 beta.

                Comment


                • #48
                  Originally posted by curfew View Post
                  The narrative since KDE 5.21 has been "Wayland is now great". It's about thime that they (or Phoronix) found a new gimmick to boost for clicks.
                  How about channeling your anger for doing something positive?

                  Comment


                  • #49
                    Originally posted by Klassic Six View Post

                    How about channeling your anger for doing something positive?
                    There is nothing angry about stating the obvious:
                    We get these news of Wayland fixes twice a week, and how everything works now.
                    And yet we got the same message last month, last year (and a couple of years before that...)
                    Could it be that it was not true last year? And maybe it is not true now?
                    And that people have work to do, and can't all be beta testers?
                    10% Wayland adoption seems to be in sync with this reality.
                    Nothing wrong with new projects, but don't push it when it is not ready, you are damaging its reputation, and people are less inclined to try it next time.

                    Comment


                    • #50
                      Originally posted by STiAT View Post
                      This seems to be a general issue with setting desktop icons, up the .desktop file properly and setting a proper wmclass.
                      For Mozilla the bug is there: https://bugzilla.mozilla.org/show_bug.cgi?id=1530052 (fixed January 28 2022, so should be fixed in firefox 98)
                      Yeah, doesn't appear to be fixed. It still occurs in Nightly, which today is at 99.0a1 :-(

                      Comment

                      Working...
                      X