Hi!

Seems 5.26 completely broke my Wayland desktop on my Surface Pro7. It now started with a completely blank screen, unable to launch any app (including control+alt+T for the console). After successfully logging to X11, seems that has fixed the login on Wayland, and I get a desktop and taskbar. But I get an old and odd behavior on firefox tabs, where the contents are not redrawn unless switching to another task. If I open new tabs or close them, this is not reflected on the window unless task switching. Additionally, the resolution scaling is busted now, being ignored by most windows. And some other apps seem to draw their windows completely blank. These and many other bugs seem to be popping for quite a bunch of people since 5.26 update, on reddit.com/r/kdeneon.

My question is...is there any guidelines on this? Any announcement or any quick fixes we can work through? KDE Neon is in a quite unworkable state as of right now. I was making it through awaiting for the fix of the messy wayland notifications and menu bar popping in the middle of the screen...but this is a whole new level of trouble.

When I tried to update to 5.26 with Discover it proposed the list of changing packages, in which two packages were proposed to be removed: libkwineffects13 and libkwinglutils13, and no newer versions of libkwineffects* and libkwinglutils* were proposed to be installed instead. This fact alarmed me, ind I decided to delay the update until this problem will be solved. It seems, that this could be possible reason of the trouble described by you.

Menak Vishap wrote:When I tried to update to 5.26 with Discover it proposed the list of changing packages, in which two packages were proposed to be removed: libkwineffects13 and libkwinglutils13, and no newer versions of libkwineffects* and libkwinglutils* were proposed to be installed instead. This fact alarmed me, ind I decided to delay the update until this problem will be solved. It seems, that this could be possible reason of the trouble described by you.

Both were replaced by *14 versions
This can be checked.
For example:

Code: Select all

$ apt search libkwinglutils
Sorting... Done
Full Text Search... Done
libkwinglutils13/jammy 4:5.25.5-0xneon+22.04+jammy+release+build14 amd64
  KDE window manager gl utils library

libkwinglutils13-dbgsym/jammy 4:5.25.5-0xneon+22.04+jammy+release+build14 amd64
  debug symbols for libkwinglutils13

libkwinglutils14/jammy,now 4:5.26.0-0xneon+22.04+jammy+release+build15 amd64 [installed,automatic]
  KDE window manager gl utils library

libkwinglutils14-dbgsym/jammy 4:5.26.0-0xneon+22.04+jammy+release+build15 amd64
  debug symbols for libkwinglutils14

and

Code: Select all

$ apt search libkwineffects
Sorting... Done
Full Text Search... Done
libkwineffects13/jammy 4:5.25.5-0xneon+22.04+jammy+release+build14 amd64
  KDE window manager effects library

libkwineffects13-dbgsym/jammy 4:5.25.5-0xneon+22.04+jammy+release+build14 amd64
  debug symbols for libkwineffects13

libkwineffects14/jammy,now 4:5.26.0-0xneon+22.04+jammy+release+build15 amd64 [installed,automatic]
  KDE window manager effects library

libkwineffects14-dbgsym/jammy 4:5.26.0-0xneon+22.04+jammy+release+build15 amd64
  debug symbols for libkwineffects14

yes, this is on a 22.04 system, I am not near my 20.04 system at the moment.

The terminal output and the logs do show what look like scary installations and dependency messes, but they are not.
Well, they *are* scary for sure. But there is nothing broken or failing in this case.

Plasma bugs might be another issue.

I am sorry for misinforming, actually libkwineffects14 and libkwinglutils14 are present, and all updates applied successfully on 20.04 system, everything works fine (almost ) with 5.26.