https://bugs.kde.org/show_bug.cgi?id=461358
--- Comment #11 from Oded Arbel <o...@geek.co.il> --- (In reply to Nate Graham from comment #10) > This means you're not using Neon Unstable, but rather it's Neon Testing. > You're using the unstable version of the 5.26 package, not the unstable > version of the 5.27 package. But the fix is only in 5.27. I definitely have the repo set to "unstable": $ apt policy kwin-wayland kwin-wayland: Installed: 4:5.26.3+p22.04+tunstable+git20221124.0014-0 Candidate: 4:5.26.4+p22.04+tunstable+git20221129.1426-0 Version table: 4:5.26.4+p22.04+tunstable+git20221129.1426-0 500 500 http://archive.neon.kde.org/unstable jammy/main amd64 Packages 4:5.26.3+p22.04+tunstable+git20221129.1204-0 500 500 http://archive.neon.kde.org/unstable jammy/main amd64 Packages *** 4:5.26.3+p22.04+tunstable+git20221124.0014-0 500 500 http://archive.neon.kde.org/unstable jammy/main amd64 Packages 100 /var/lib/dpkg/status Where the current most up to date kwin-wayland package is 4:5.26.4+p22.04+tunstable+git20221129.1426-0 - which I verified against http://archive.neon.kde.org/unstable/pool/main/k/kwin/ (I do need to update again today). I wasn't really aware of "testing", but looking at it (I'm assuming, at http://archive.neon.kde.org/testing/pool/main/k/kwin/) I can also see just 5.26.4. I also saw "experimental", which is currently at 5.26.3, and at the CI server - no where could I find a 5.27 build... -- You are receiving this mail because: You are watching all bug changes.