Plasma 5.24 was released a few days ago, and so far it’s been the smoothest release in memory. There have been a few regressions, but fewer than other recent releases. I’m sure all of you who have experienced new issues will speak up in the comments, of course. 🙂 But overall it has gone quite well!
15-Minute Bugs Resolved
Current number of bugs: 83, same as last week. Current list of bugs
In the Plasma Wayland session, panels no longer sometimes randomly freeze especially right after login (Vlad Zahorodnii, as soon as your distro updates their KDE Qt patch collection to include this patch)
Closing your laptop lid when an external monitor plugged in no longer causes the computer to inappropriately go to sleep when the setting to disable this has been used (Somebody awesome, Plasma 5.24)
New Features
Konsole now supports Sixel, allowing it to display .sixel images right inside the window (Matan Ziv-Av, Konsole 22.04)
Konsole now has a new plugin that stores saved commands and pieces of text for you (Tao Guo, Konsole 22.04)
Bugfixes & Performance Improvements
When using Kate’s feature to stash and restore unsaved changes to open files when closing the app, those changes are now actually saved as expected rather than being silently destroyed if you happen to quit the app using the “Quit” action or Ctrl+Q keyboard shortcut instead of clicking on the window’s close button (Waqar Ahmed, Kate 21.12.3)
Canceling an in-progress archive job now automatically deletes the temporary file that was being created (Méven Car, Ark 22.04)
Konsole’s text re-flow feature now works for lines of text that have no whitespace or newline characters at all (Luis Javier Merino Morán, Konsole 22.04)
System Settings no longer crashes when the active color scheme doesn’t exist on disk for some reason; now it falls back to Breeze Light (the default color scheme) and doesn’t crash (Nicolas Fella, Plasma 5.24.1)
In the Plasma Wayland session, Plasma no longer always crashes when you screencast in certain circumstances (David Edmundson, Plasma 5.24.1)
In the Plasma Wayland session, using custom splash screens once again works (Linus Dierheimer, Plasma 5.24.1)
The Scale effect is once again configurable (Alexander Lohnau, Plasma 5.24.1)
Links to System Settings pages added to the desktop using the “Add to Desktop” context menu item in Kickoff once again actually appear on the Desktop as expected (Alexander Lohnau, Plasma 5.24.1)
Certain types of large buttons with text no longer make their text half-invisible when they’re focused with the keyboard (Ingo Klöcker, Plasma 5.24.1)
Info Center’s “Devices” page once again works as expected if the command-line lspci program lives in /sbin/, /usr/sbin, or /usr/local/sbin on your computer (Fabian Vogt, Plasma 5.24.1)
Dragging desktop files over a Sticky Note applet no longer makes the files temporarily disappear (Severin von Wnuck, Plasma 5.24.1)
In the Plasma X11 session, the cursor no longer disappears while using the “Zoom” effect (Vlad Zahorodnii, Plasma 5.24.1)
The Fall Apart effect once again works and no longer interacts strangely with the Overview effect (Vlad Zahorodnii, Plasma 5.24.1)
In the Plasma Wayland session, fixed one way that tooltips could be mis-positioned (Vlad Zahorodnii, Plasma 5.24.1)
The Overview effect no longer inappropriately shows minimized windows in the desktop thumbnails for moment before immediately hiding them again (Vlad Zahorodnii, Plasma 5.24.1)
When using certain 3rd-party window decoration themes, quick-tiling a maximized window no longer unexpectedly de-maximizes the window instead of quick-tiling it (Vlad Zahorodnii, Plasma 5.24.1)
System Settings is now faster to launch, especially when using the legacy Icons View mode (Fushan Wen, Plasma 5.24.1)
Dolphin no longer crashes when you close its “Create New File” file dialog in a remote location (Nicolas Fella, Frameworks 5.92)
Fixed a memory leak when canceling in-process move/copy archive (etc) jobs (David Faure, Frameworks 5.92)
Scrollable views with text in QtQuick-based software no longer exhibit visual glitches with text being cut off or squished at the top or bottom when the view is scrolled very slowly a pixel at a time (Noah Davis, Frameworks 5.92)
Font changes now take effect instantly in QtQuick-based apps (Nicolas Fella, Frameworks 5.92)
Buttons in System Tray applets that open Info Center pages now work if you don’t happen to have Info Center installed; they instead open the requested page in a separate window (me: Nate Graham, Frameworks 5.92)
All QtQuick-based apps now use slightly fewer CPU resources (Aleix Pol Gonzalez, Frameworks 5.92)
User Interface Improvements
When an app is installed more than once from different sources (e.g. one version from distro repos, and another version from Flatpak), The context menu for that app in Kickoff no longer has multiple entries saying, “Uninstall or manage add-ons” (Alexander Lohnau, Plasma 5.24.1)
Searching for apps that are not yet installed no longer returns duplicate entries for matched apps that are available from multiple sources (Alexander Lohnau, Plasma 5.24.1)
In the Overview effect, apps’ selection highlight effects now disappear when you start to drag them (Vlad Zahorodnii, Plasma 5.24.1)
System Settings’ Quick Settings page has received some UI polish for the alignment and spacing of its elements and the clarity of its labels (me: Nate Graham, Plasma 5.25):
Kate, KDevelop, and other KTextEditor-based apps now do a much better job of differentiating files opened in tabs that have the same filename (Waqar Ahmed, Frameworks 5.92):
Dragging a file or folder over an item in the Places panel now causes that location to be opened and displayed in the main view so you can drag the thing into a folder inside it. And if the Places panel item you dragged over was an unmounted disk, it is now automatically mounted first! (Kai Uwe Broulik, Frameworks 5.92)
Errors in the open/save dialogs are now shown inline as in Dolphin, rather than with a separate dialog window (Kai Uwe Broulik, Frameworks 5.92)
…And everything else
Keep in mind that this blog only covers the tip of the iceberg! Tons of KDE apps whose development I don’t have time to follow aren’t represented here, and I also don’t mention backend refactoring, improved test coverage, and other changes that are generally not user-facing. If you’re hungry for more, check out https://planet.kde.org/, where you can find blog posts by other KDE contributors detailing the work they’re doing.
How You Can Help
If you’re a developer, check out our 15-Minute Bug Initiative. Working on these issues makes a big difference quickly!
Otherwise, have a look at https://community.kde.org/Get_Involved to discover ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!
Finally, consider making a tax-deductible donation to the KDE e.V. foundation.
Adventures in Linux and KDE 
>>all of you who have experienced new issues will speak up in the comments, of course
Dammit 😉
I was going to post a sarcastic commentary on Kwin’s Night Color plugin that prevents setting external monitor as a primary screen if proxy is enabled, but you disarmed me lol.
Indeed this release was very smooth, especially if compared to the previous one which was bugged to the extent that I had to rollback and defer updates until 5.23.2.
LikeLiked by 1 person
5.24 is buttery smooth, all the KDE devs should be proud of this release! 🎉
One thing I’m noticing right away is that my laptop connects to my WiFi much faster now; it used to time out and then connect with 5.23.
But damn, Nate, just when we get the brilliant gem that is 5.24, I’m starting to pine for future versions 😜
“Kate, KDevelop, and other KTextEditor-based apps now do a much better job of differentiating files opened in tabs that have the same filename”
This will be so welcome!
“Errors in the open/save dialogs are now shown inline as in Dolphin, rather than with a separate dialog window”
Love the detail work here.
LikeLiked by 2 people
Thanks so much for the kind words!
LikeLike
5.24 has been pretty good for me with Wayland. I was on x11 again seeing as my multi-monitor was just unstable and would loose my desktop session all the time, but not anymore!
I can turn my TV on or off and KDE now handles it like a champ. Sometimes the plasmashell still crashes, but it recovers gracefully so no big deal. I can now even turn off all my monitors and turn everything back on the next day and my session still lives!
Amazing release regarding Wayland. Looks like I can now use it permanently!
Gratz!
LikeLiked by 1 person
Yep. I’m hearing this more and more! The Plasma Wayland session is finally buggy but usable, as opposed to an unusable mess. Onward and upward!
LikeLike
Yeah that’s true. I caught myself thinking after several minutes of using Plasma Wayland “Cool, at this point I could switch without major compromises”.
LikeLiked by 1 person
For me it is unfortunately less smooth. Since the update, plasma(s)hell is crashing all the time (in X11 and in Wayland) 😦
LikeLike
Can you file bug reports? We’ll investigate and try our best to fix them. Quite a few crashes were just fixed this week.
LikeLike
I guess you asked for it 🙂
Let me start with a warm personal thanks to you for keeping us all up to date and to all KDE developers working so hard to provide us all with the best possible user experience.
I have been using KDE for the last 20 years (apart from a very bad period during the beginning of KDE 4)
and will certainly keep using it.
I tried again wayland with plasma 5.24, but moved back after 15 minutes.
My Wayland experience:
– Fonts are a bit crisper, for me this is the only reason to try it.
– Notifications are not shown when I connect via VPN through the command line (nordvpn client)
(works on X-windows)
– Clicking on a torrent link (I wanted to download arch linux to see if that works better) opens Deluge,
clicking on a button in Deluge causes it to freeze. deluge-gtk now uses 98% CPU. Had to kill it. (works on X-windows).
Sometimes the text on the Deluge application is displayed differently at this stage, as if the font smoothing is turned off. Also my cursor started flickering.
– The windows minimization shows a wrong visual clue. A Window no longer minimizes to its button on the task bar (as it should, that’s where it “is” if minimized) but always goes towards the lower-right corner. I had to switch off the minimization since it is confusing like this.
At this point I moved back to X-windows.
Other things I noticed (I think not Wayland or plasma related):
– I still notice a delay of about a second if I want to show a directory in Dolphin after not using it for a while.
After using it the first time it reacts fast again. As if something falls asleep when not used for a while?
This started somewhere in the last year.
– If there is a problem with my network connection, KDE will “crash and burn” .
the KIO slaves or whatever is used under water seem not robust enough.
More and more processes will appear with status disk-sleep and I have to hard-boot my PC using the
power button.
My main problem with KDE is still reliability, although this improved a lot the last year I I feel I cannot trust it (but I think we can get there) to be stable / keep working for let’s say a full day’s work without rebooting.
(I use KDE in an office-like environment, with files stored on a NAS but the OS on an SSD, mounting the remote shares via fstab. KDE seems not optimized for this use case)
Two other big things for KDE wayland (but of course you know this!):
– if an application crashes, it should not take down the complete environment with it.
– font scaling _must_ work
I made some bug reports but not yet for all of the above.
Thanks again!
LikeLiked by 2 people
> – If there is a problem with my network connection, KDE will “crash and burn” . the KIO slaves or whatever is used under water seem not robust enough. More and more processes will appear with status disk-sleep and I have to hard-boot my PC using the power button.
I’m willing to bet you have NFS mounts, no? If so, this is not something KDE can easily fix.
When the remote server cannot be contacted, NFS mounts will block any system call that so much as looks at the mount. This blocking has *infinite timeout* and happens inside a system call so processes can’t even be killed.
There is an arcane set of NFS mount options to make that timeout not infinite. It’s a janky workaround, but at least it gives you a way to recover without rebooting.
LikeLiked by 1 person
Yeah this is the problem that kio workers were meant to solve, and kio-fuse made even more progress on. I would strongly recommend never never ever ever manually mounting external network resources using autofs or fstab or whatever, and instead always access those resources using their nfs:// URLs using GUI software (or browse to them in Dolphin), which will handle connection lifetime issues transparently.
LikeLike
Hi Nate,
how do I use kio for a network share which I want to have indexed by Elisa (music) or Digicam (pictures etc.). Is than even possible? How do a kio-accessed network share to add attachments to a mail I compose in Thunderbird. If such things don’t work for me, am I doing something wrong?
Thank you so much!
Wolfgang
LikeLike
Unfortunately Elisa does not yet support this, sorry. There are various hacks you can try but none of them work particularly well.
LikeLike
Thanks for your insight! I do not use NFS. I would like to use it, since it would handle linux file properties transparently, but I cannot set it up reliably without fixed IP addresses. Also I read about too many NFS problems 🙂
LikeLike
None of those issues are regressions in 5.24 compared to 5.23, so I feel vindicated in my assessment. 🙂 Some are caused by 3rd-party apps, and this is unfortunately where Wayland is roughest. A lot of apps–especially older ones–really have not taken the steps needed to work properly on Wayland. Even big apps like VLC are still using XWayland, and LibreOffice’s improper scaling in its native Wayland mode makes it unusable.
Bug reports for the issues that seem KDE-related would be appreciated, of course.
Oh and making KWin not take all apps with it when it crashes is being actively worked on, with WIP patches for all major UI toolkits (Qt, GTK, Electron, and SDL). It may actually get done this year!
LikeLiked by 2 people
I cannot comment on the overall quality of 5.24, but I read it solves problems such as multi-monitors for people so that is all good. Kwin not killing all apps sounds very good! Still I wonder why the notifications of nordvpn (a command line utility) do not work in Wayland. I (perhaps naively) would have thought that this has nothing todo with Wayland. But I am no expert there. I raised a bug report (450086) for this one.
And thanks for the tip about not manually mounting networks, I did this in the past because the speed was higher like that, but perhaps I should indeed stop doing this. Will give it a try.
LikeLike
One more question w.r.t. my remarkts about the windows minimize animation: pls tell me this is not intentional? Thanks 🙂
LikeLike
Definitely not intentional, and I can’t reproduce it on my fairly simple setup of one monitor and one panel. However it’s possible that it got confused if you have multiple monitors or multiple panels. I’d recommend filing a bug report and describing your hardware setup.
LikeLike
I just wanted to say that I am enjoying the overview effect, and holy heck, Vlad, you are working a LOT!! I am looking forward to seeing how this progresses. Thanks to you, as well as all the devs.
LikeLiked by 2 people
Certainly 5.24 is the first release in years that I do not manage to crash in less than 20-30 mins, congratulations, the 15 min bug policy is producing results.
LikeLiked by 1 person
Last time I used Wayland, if you were using a package manager other than Discover, the password authorization window would appear next to the window of the package manager not centered over top of the package manager window,. I.E. Synaptic in Debian or Manjaro’s package manager or for that matter, the other KDE package manager besides Discover.
LikeLike
That should be more or less worked around in 5.24 by us changing the window placement to “Centered” by default.
LikeLike
I experience only one problem after upgrade regarding “hibernate some time after sleep” functionality. I already reported it https://bugs.kde.org/show_bug.cgi?id=450083
On Wayland session I’ve seen some glitches like black rectangles that need to be washed out with moving window around or maximizing it, like something couldn’t refresh on its own. I’ve seen that once after getting out of sleep (doesn’t happen every time and I’m not sure how to trigger it). Something similar happened on 4K screen scaled to 200% with context menu on the desktop. Inactive options was behind black stripes until I clicked on them. Looks like a Qt issue to me, as I saw similar glitches in Qt windows before, but never seen them in GTK/Firefox/Chromium/Xwayland etc.
LikeLike
Search: what would be awesome is, if you are anywhere in KDE or plasma and start typing, it would be awesome if the string was within the search so the focus was there.
I’m thinking of overview page, add widget, …
LikeLike
In fact the search fields in both places are already focused by default! 🙂 But new in Plasma 5.24 is that they get de-focused if you’re in tablet mode, so that the virtual keyboard does not immediately pop up in your face the moment you open the widget explorer or Overview.
LikeLiked by 1 person
5.24 is really amazing.
What a fantastic job all devs done in this release.
KDE is really on the right track! Whatever all you guys are doing, just keep doing it!!!
About our bug complain in the comments: it is either here or risk creating another bug report on the issue tracker that is not a bug but an interface problem (you know: a problem on that interface that connects the chair to the keyboard – getting it?! *Wink wink*)
Speaking of bugs…
See if you can replicate this (or if it’s a interface problem on my PC):
set a panel on the top of the screen. Set it to “Windows go bellow”. Now go to the overview effect.
Does your Overview gets bellow the panel??? If so, Is that how it suppose to work?
or should I fill a bug for that?
LikeLiked by 1 person
Can reproduce, will be fixed soon. There’s an open merge request for it.
LikeLike
Amazing release, can’t wait to try it!
One suggestion if I may:
For the last KDE releases, I’ve been experiencing a frustrating bug:
Copy text doesn’t work sometimes. KDE Neon user
This happens on my desktop as well as my laptop, both on X and Wayland.
Can KDE introduce a effect when a text has been copied? Could be a Kwin effect, like a water effect inward when copy and outward when paste or something.
This could indicate copy has been successfully .
Regards, Loren
LikeLike
I think we should fix the bug instead. 🙂 Can you file a report on https://bugs.kde.org?
LikeLike
The only Problem I’ve noticed with 5.24 is that opening the window decoration kcm Kills systemsettings. I’ve not Reported it yet. As I can’t Provider a proper backtrace. (Bloody artixlinux not having many many debug symbol packages)
LikeLike
So apparently it was a configuration fault, I had an old decoration installed based on the KDE2 one, and deleting it got rid of the crashes.
Considering it was the only crash I had, I love the new release. Keep up the good work
LikeLike
Great work, thanks to everyone involved! Just a couple minor things from the System Settings screenshot:
1. ‘Colours’ appears twice in the Most Used Pages section at the bottom, which is odd unless there are two Colours sections.
2. The Single-click/Double-click text seems written in a very round-about way. It is ambiguous because ‘Clicking’ on the left isn’t specified until you read the small print. In the video interview you posted up a few weeks ago, I’m pretty sure they asked you if you “Single or Double-clicked” – these terms are primarily what should be select-able & the text/explanations be the small print. i.e. it was closer to how I prefer it in Plasma 5.20.5.
Minor issues though & I’m aware System Settings are getting worked on, sorry I just pick up on little things like this. &:^D
LikeLike
1. Yeah I’m going to be working on that soon. It’s a pre-existing issue not introduced with the UI change though.
2. “Single-click” and “double-click” are kind of our internal dev jargon, like the word “KRunner”. These terms aren’t generally surfaced in the UI.
LikeLike
Plasma 5.24 on Wayland (without the NVIDIA driver) has buggy HDMI on my laptop (Arch Linux). With Plasma 5.23 there were no issues.
LikeLike
there is a fullscreen effect stutter bug that happens in wayland since 5.23.4 when putting mpv gwenview yacreader opencomic and some other applications in fullscreen mode where the app freezes for a little when fullscreen effect animation occurs btw there is another issue that also seems be related i noticed it in mpv around the same time the fullscreen effect issue started if i resize mpv while playing a 30 fps or or lower video the resizing animation follows the video playback fps instead of my display 60 fps making it look choppy but resizing is smooth when the video is paused which was not happening before so ya in these latest versions of plasma there’s a good bit of animation problems in the wayland session
LikeLike
>>all of you who have experienced new issues will speak up in the comments, of course.
Well, yeah. But first, congratulations on this release, it is indeed memorable, in X at least 😉
In Wayland, no so much. While Wayland support in Plasma has vastly improved in the last releases; Plasma doesn’t crash anymore when connecting an external monitor/display/screen, as well as other things. I refer to this particular issue mostly because it is the one stopping me from fully switching to it. So, I tried again, with 5.24 beta when it was out(KDE Neon) and now the stable one (Arch), and yes, Plasma didn’t crash like it used to, but I couldn’t switch back screens and/or deactivate the external one, nor via F4, which brings the “on screen menu”, neither via system settings by unchecking the screen/display entry. If I remove/unplug the external one, the system freezes and have to hit the power button. I didn’t get any error messages(drkonqi) and checked the logs, but not sure what I should be looking for, that being said, I did see a bunch of msgs with “kscreen_backend_launcher” and don’t know if related.
How can I get info when this happens?
LikeLike
By filing a bug report. 🙂 The developers can help you gather whatever logging would be required to debug the issue.
LikeLike
Thanks for replying. I had the idea that I needed more info in order to file a bug report, that’s what I asked how I can get that info.
LikeLike
I think I found a regression, but I’m not sure. I wanted to turn on Do Not Disturb mode, but there was no visible icon in the tray for the notifications applet (because I had no unseen notifications), so I clicked on the triangle to expand the applet drawer, clicked on the Notifications applet, but it doesn’t react. I thought I remember that 5.23 would at least allow me to see and interact with the Do Not Disturb setting.
LikeLike
That’s weird, works for me. When you say, “it doesn’t react”, does “it” refer to the whole applet itself, or the checkbox?
Regardless, can you file a bug report?
LikeLike
… it’s a nightmare. The worst release since years! I’m a 20+ KDE user. I use it on a professional basis, means ten plus hours a day and I guess I gained a bit of experience. This release brings KDE back to the beginning of the 4 versions that were also horrible. The thing that worries me is, that it seems not be a single bug or component that fails but the whole framework is unstable and crashes. These are the main problems I found so far:
* plasmashell crashes after returning from screen saver and sometimes closes all application windows (very annoying, since all konsole logs are gone)
* after PIM pops up a reminder window and pressing OK, the desktop fails to repaint and
flickers all background windows for several minutes
* screen saver does not scale the cursor and mouse pointer correctly (on 4k, X)
* mail notifications that usually appear on the right side are looking ugly and appear centered, but other notifications are correct
* compositing (usually opengl, but the setting is gone) gets disabled after some time and “Enable on startup” is reset
I guess PIM has never been one of the strengths of KDE but sometimes it is only childish. Look at this for example:
“`
deepsky:~> journalctl | grep -c “org.kde.pim.ews.client: Failed to process EWS request: Could not connect to host 1756333
“`
I know that sometimes the mail server is unreachable but I guess PIM doesn’t have to tell me this 1643 times per second.
Usually I do not reply to such blog entries, since I usually appreciate your work and honor the effort and am willing to live with glitches and things that are imperfect. But this one is, as I said a nightmare.
LikeLike
Can you please file bug reports for these individual issues so we can investigate and hopefully fix them?
Also note that if a crash closes all apps, that’s not plasma crashing, it’s either KWin (if you’re in a Wayland session) or the X server (if you’re in an X11 session). And an X server crash is almost never the fault of any KDE code.
PIM is not a part of Plasma so PIM issues would not generally be caused by a Plasma upgrade.
LikeLike
I kid you not Nate, KDE 5.24 makes my Kubuntu 21.10 feel like a new computer. Everything just runs so much better and animation is smooth. Great work has been done by KDE Community, thanks.
LikeLiked by 1 person
I’m so happy! What a pleasant contrast to the comment immediately above saying that it’s been a nightmare. 🙂
LikeLiked by 1 person
since 5.24 I’m missing context menus of gajim’s and pidgin’s systray icons
LikeLike
Known regression, already fixed, fix will be released tomorrow.
In the future please report bugs using https://bugs.kde.org. 🙂
LikeLike
… to come back on my previous post (February 14, 2022 at 8:08 am).
Updated today plasma 5.24.0 -> 5.24.1. And everything went back to normal! No more crashes when an external monitor gets disconnected or switched off (which I figured was the reason for plasma to go weird). I’m not quite sure if plasma actually was the culprit, but I downgraded kwin and other packages, since you supposed that will crash, with no improvement.
Thank you for fixing this in no time. I’m quite happy again with plasma. And just to state it again I really appreciate your work and effort.
LikeLiked by 1 person
Nate, regarding:
https://invent.kde.org/frameworks/kio/-/merge_requests/143
and
https://invent.kde.org/frameworks/kio/-/merge_requests/731
am i reading it correctly that Root Operations in Dolphin have not yet landed in Frameworks 5.91?
I was really waiting for this feature. It’s very handy!
LikeLike
Right, not yet.
LikeLike
Unlike many others, 5.24 felt more buggy and unstable. The past two releases were boringly uneventful, but this new one feels just problematic. I was able to resolve some issues myself, but there are still some weird things, that I don’t even know how to report.
Did you ever experience that the blur effect disappeared from some elements? This is an old bug that lasted over a year now, probably since the new, awesome blur was introduced. Restarting kwin never helped, restarting session did. Since this was a rare and random occurrence, it was not a big problem. The reason I’m writing this is that with the 5.24 update, a new this type of errors appeared, but now, they are more problematic.
1) Sometimes (usually after playing with settings) the new overlook looses its ability to focus on the search bar. If everything is OK, we can type and search bar is filled. If the bug appears, there is no blinking cursor and no way to focus on the search bar. I can click on it, try to tab to it. Nothing. The search bar becomes inactive permanently. System reboot fixes it.
2) Sometimes I can’t open the apps from launchers. Typically, it happens when the app was previously opened and closed. The next time I want to open it, nothing. I can click on my dock all day long without effect. I can open start menu and click on favorites – still nothing. I can search the app and click on it – still nothing. But… I can open it using exec command in the terminal. I can open it from desktop using the search tool. Rebooting the system fixes it.
Since those errors happen very rarely and randomly – it’s hard to debug or describe them. In a way, they behave similarly, as this old blur bug. I have no idea which component is responsible, I see no apparent error notices from the system – all is silently not working right.
Additionally, as you know, for the most part changing settings works fine, but when you play with them long enough, weird thing start to happening, kwin or plasmashell sometimes crashes, restarts automatically, but the new instance is bugged. When working on a system on a daily basis, we don’t mess with settings, so the bugs I described almost never show up (aside the blur one which showed up spontaneously now and then).
I haven’t updated to 5.24.1 yet, so maybe those are fixed already, but given their obscure nature, I don’t have high hopes. I won’t report those bugs right now, but keep observing, and possibly I notice something that will allow me to find some common denominator, some regularity, some trigger, etc.
So before 5.24 there was only the blur issue, now there are already two new ones, with one that is seriously disturbing the workflow (apps cannot open from the usual launchers).
Also, I got sometimes freezes I didn’t before, and those freezes live between reboots. For example, I click on clipboard icon and… everything becomes unresponsive and clipboard info is not loading correctly. I reboot the system, all is fine, till I don’t click clipboard icon. So I reboot again, the issue repeats. So this time I wait, maybe 5 minutes, clipboard shows up finally correctly and…. NEVER TO SHOW THIS BEHAVIOR AGAIN. How can I report that if I have no data and can’t replicate the bug myself? Aside the clipboard, I had many of similar issues with various parts of the system right after the upgrade, then they disappeared permanently after time.
This all gave me the feel of uneasiness about this release. Luckily, the freezes seemed to end, and other bugs happen less and less frequent on their own, so once again Plasma starts to feel smooth, but the initial experience was horrible. Now I begin to enjoy it again.
LikeLike
Several of those are in fact fixed in 5.24.1.
LikeLiked by 1 person
Really? That’s great to hear! I’ll update right away. Thanks 🙂
LikeLike
Warning: I installed Plasma 5.24 backports on Kubuntu 21.10 and now it boots a blank black screen with just a mouse pointer.
LikeLike
Is that 5.24.2?
LikeLike
5.24 was a great release, 5.24.2 not so much, Wayland multi-screen now seems very broken. Is there a problem that not enough of the plasma Devs has multiple screens?
LikeLike