I've had problems with the update - if I minimise a window it closes. I first noticed it with Libre but same problem with terminal window. Nasty problem in Libre, because if you're writing something and this happens, Libre cannot recover the document. (I'm a writer) Also, bluetooth has stopped working - won't recognize devices at all; they just don't register.
It would be great if this could be fixed. This problem seems to be cropping up in other posts, I'd hate to have to change back to another distro, I REALLY like Solus, but I need the stability, particularly with docs. Any clues?

    redearthman Yeah I'm at a complete loss other than it's kernel related. I've been on Plasma since its release, and this is the first actual issue I've ran into that wasn't self-inflicted.

      I slowly have a suspicion it's kernel related as well, I'm pushing right now 5.23.2 to unstable and I gonna see if my system is more stable but sofar a bit annoying with amd CPU/GPU :/

        can confirm that the issue is both on plasma & budgie (tried both with the same effect), so its rather kernel related .

        hmm. In the past, when I was using the Kubuntu Distro, if I'm not mistaken, Plasma Shell suddenly stopped working (and displayed a black screen) for a while and then the Shell could be used again as before. Once, I added a Backport PPA to upgrade KDE Plasma 5 to the latest version. in the KDE Neon distribution, there are no bugs related to the shell until now (I've tried it before). Switched distros again some time to Ubuntu Budgie 21.04 there was a glitch on the Budgie desktop.
        First: When I open the "About" page in GNOME Settings it displays an error report, Error displays the message "gnome-control-center-print-renderer" Stopped Working.
        Second: sometimes also when HDD is busy up to 100% disk Budgie wm displays the error report Budgie Budgie wm Stop Working.

        October 18, 2021 The morning I have tried and Installed Solus OS 4.3 Until now November 2, 2021. There are no problems in the Budgie Desktop Environment especially related to Bugs until now. But some fonts such as Display Names in Telegram Messenger do not display well, such as Javanese script letters. unless it displays a checkered character. @JoshStrobl When do you want to add Unicode Fonts? Especially for Asian fonts such as: Korean, Chinese, Japanese and Javanese characters in the Solus OS repository?

        OwO You have a Nvidia graphic card, don't you? Perhaps that's the crux of the matter, this problem affects only computers with AMD graphic cards.

          zmaint I just created a bug report, it's my first one, I hope I did it right.

          https://dev.getsol.us/T10000

          I mentioned your computer, and your friend's computer.

          Let's hope it gets solved as soon as possible.

              @JoshStrobl Just updated with the new kernel released today, same issue. Takes forever to boot, asks for kde5 wallet pass, apps are unresponsive to the point of being unusable.

              Confirm booting with the 5.14.14-202.current kernel works fine.

                zmaint Thank you for letting us know! I didn't update my laptop yet, and after reading your post I don't know if I should. How did you manage to boot with kernel 5.14.14? Because once you update, you only have the last two kernels, 5.14.16 and 5.14.15.

                    joluveba Well I had rolled back all of the updates from last week, so I'd been booting from that kernel. So when I updated today, I had all three kernels to choose from.

                      zmaint Confirm booting with the 5.14.14-202.current kernel works fine.

                      it's good you found that fallback.

                        zmaint I just read this. if this was an AMD thing I wonder where the kwallet prompts come from? Maybe it's the way everything works together--seems the easiest answer at least.

                            brent I thought that was odd, which is why I made it a point to mention it here and in the bug report. It's definitely over my head stuff 🙂 They seemed to know right what it was, for me that works.

                            On a side note, can anyone even imagine trying to have a conversation with Microsoft about a bug... lol. Just another reason I'd never even consider going back.