This seems to be a genuine KDE problem.
https://bugs.kde.org/show_bug.cgi?id=439332
Another bug concerning ghost windows has been recently fixed.
https://bugs.kde.org/show_bug.cgi?id=438552
Other Manjaro users mention possible workarounds for a similar behavior here
that something crashes is always possible, but iâm concerned because even a crashed instance should have a pid and there is no if i search vor with âps -axâ. thatâs a serious problem in my mind. every instance should have a pid nevertheless if itâs working or stuck.
Not sure, how you define âcrashâ. For me, if an app crashes, it aborts and stops. In that case, there is no process anymore and hence no pid. There still might be some graphical remnants displayed on the screen/desktop, but this is only due to a bug in the window manager and does not imply, that the app, or parts of it are still running.
There are other situations where an app encounters a (serious) error, which is somehow handled by the app. In that case the app is still running, i.e. itâs NOT crashed. It might, however, be unresponsive, but you will be able to find a pid for it.
If set âIcon Viewâ in System Settings, then there are two âGlobal Themeâ in Appearance:
I can confirm this. 
Current info:
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.10-1-MANJARO (64-bit)
Graphics Platform: X11
Sometimes if a couple users sees that, it is not means that all does: it is the case 
Operating System: Manjaro Linux
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.15.0-1-MANJARO (64-bit)
Graphics Platform: X11
I even restarted a system setting window after change to icon view.
Global theme: Breeze Dark.
winnie you are so advanced and you are not in the unstable branch? unstable got 5.23.1 a long time ago.
Could be some 5.22-specific issue though⊠Let me check
UPD: I can confirm this as well. Not sure if itâs our or KDE bugâŠ
Do I need still? Itâs upstream bug thatâs fixed in 5.23.
Latte dock 0.10.3 is released. Can we have that one in the stable branch soon ?
Thanks.
Iâm pretty sure youâve been around long enough to know how things work. 
Well, I see that Latte dock 0.13.3 is in the testing branch. No problem, I will waiting that it be available in the next stable branch.
After update soundcard is not detected. Bluetooth audio works fine but no onboard devices, neither speaker nor mic.
I tried to switch to pipe wire but this made no difference.
Installing sof-firmware brought audio back but audio control keys are not working; speaker mute, mic mute, volume up, volume down.
I suspect this is kde related but I donât know which package(s) to downgrade.
EDIT: So above was all done late last night, or rather early this morning. Testing now after after a few hour of sleep it is all working. The solution is to install sof-firmware
I am using gnome 40 Wayland sesion and a spanish keyboard with Spanish layout (Spain) 3 weeks ago, before the update the symbols < and > use to work just fine but after the update there changed to the âsmallerâ versions used for quotes âč and âș
Havenât been able to fix this. Any suggestions?
I have errors like these at logout, that werenât there before. Typically âICE defaultâ, âsddm-helper crashedâ, then optionally some more services âfailed with exit-codeâ, then âQProcess destroyed while sddm-helper still runningâ. Donât seem to affect anything on practice (for now?), but still something to take note of.
Nov 08 11:53:43 hostname org.kde.LogoutPrompt[1591]: Xlib: extension "NV-GLX" missing on display ":0".
Nov 08 11:53:54 hostname org.kde.kdeconnect[1602]: ICE default IO error handler doing an exit(), pid = 1602, errno = 11
Nov 08 11:53:54 hostname sddm[699]: Authentication error: "Process crashed"
Nov 08 11:53:54 hostname sddm[699]: Auth: sddm-helper crashed (exit code 15)
Nov 08 11:53:54 hostname sddm[699]: Authentication error: "Process crashed"
Nov 08 11:53:54 hostname sddm[699]: Auth: sddm-helper exited with 15
Nov 08 11:53:54 hostname systemd[1024]: openrazer-daemon.service: Failed with result 'exit-code'.
Nov 08 11:53:54 hostname systemd[1024]: obex.service: Failed with result 'exit-code'.
Nov 08 11:53:55 hostname sddm[699]: Signal received: SIGTERM
Nov 08 11:53:56 hostname sddm[699]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Might be worthwhile to check upstream (KDE and SDDM) and report?
I pushed more packages to the staging branch: [Stable-Staging Update] 2021-11-11 - Kernels, Haskell, Nvidia, Maui, Python, FireFox, Thunderbird, KDE Gear, LibreOffice
Just adding, I installed Olive flatpak from Flathub via pamac GUI. I open it but nothing shows up so I right click the icon on the dock and my whole laptop freezes, only way to save it is if I hard restart. Does this happen to anyone else?
Manjaro Gnome
Was it once under some complicated circumstances or you saw it once again after you made the restart?
May be to save all your data before to try again (if you did not) and on some free time have a look into [HowTo] reboot / turn off your frozen computer: REISUB/REISUO
Also, what journalctl -p 3 reports on that first time you saw it (if it was the previous boot up, then add -b -1 argument)?