There is a bug report about what exactly sounds like your problem.
It’s marked fixed but missed the Beta 1 release by a day.
2 Likes
Yes, that’s my bug. I looked at the reverted change; when you change something from KeyboardInteractivity=Exclusive to KeyboardInteractivity=None, I would expect that there’s not much happening with the keyboard after the change.
Hopefully, the change makes it to the repo real quick.
1 Like
3 Likes
Largish unstable and testing update today. Seems that may have caused Konsole to disappear.
Yakuake won’t work: "Yakuake can't find the component Konsole"
CTRL-T looks like it’s at least starting Konsole (bouncy mouse cursor), but Konsole does not appear.
Anyone else seeing something similar?
No Konsole, no cli (to check error messages that may appear when starting up Konsole), no way to run yay or pacman… 
I’ll head over to my Plasma 5 setup and see if things are still working there.
you always have a console on Linux with Ctrl+Alt+F - Keys (Ctrl+Alt+F2 for example)
Ah, of course! Thanks. Silly me 
Swichted to TTY, refreshed mirrors, ran yay.
More updates amongst which Konsole.
And: all’s well again.
(With Konsole not working, I did have some hope that Plasma 6 would finally stop being boringly solid and stable; no such luck though. Running yay from TTY was all it took to get back to boringly stable.) 
Which basically resulted because of a partial update (ie you only got part of what you needed to make a coherent base).
I hear you…it’s been mostly ittsy bitsy boring problems. Though I’m not sure how much I’d appreciated having an extended scene like you thought you had.
True.
My enthusiasm about “finally, a problem waiting to be solved!” may well be explained by a lack of knowledge at my end - I have no idea what I would have needed to do if there had been no TTY (thanks @BS86 ). I suspect something with chroot, but the last time I remember doing that must have been with Ubuntu 6.06…
the issues didn’t even originate from Plasma6 - there is an icu update coming which causes many rebuilds - you seem to have updated while the rebuild was still going on.
Basically everything in the “Required By” - section needs to be rebuild.
Thank you!
Did not know what ICU is (not Intensive Care unit, I trust ), so looked it up:
ICU is a mature, widely used set of C/C++ and Java libraries providing Unicode and Globalization support for software applications.[1]
I can see why that would need lots of rebuilds.
Some people blame icu updates for lots of breakage, but it is being pointed out to them that, as in my case, partial updates are mostly to blame[2].
[1] https://icu.unicode.org/
[2] https://bbs.archlinux.org/viewtopic.php?id=271584
198 packages! 
Thank you. Very informative.
They say:
I don’t mention fixes for bugs that were never released to users
Can someone give an example of what kind of things they mean? Or are these bugs that have been caught before the app where they were caused were released?
1 Like
I guess the SDDM example from above falls in that category. In a normal development cycle someone updates SDDM (or whatever it was), the keyboard input fails, it gets fixed before release.
If you don’t participate in the testing releases/dev-snapshots you will never experience that bug. It was never exposed to the public in production and so there’s little public interest.
Thanks for the clarification. Makes sense.
If all goes according to plan, beta 2 wil be released tomorrow:
4 Likes
2023-12-20 - Don’t run updates at the moment!
kde-unstable currently serves qt 6.7 beta which breaks the plasma Beta 1 here.
2 Likes
Thanks for the warning. 
yeah, it needs to roll out the complete update before users can update.
The KDE Maintainer (arojas) announced it here:
https://bbs.archlinux.org/viewtopic.php?pid=2138290#p2138290
4 Likes
Good to know…I was planning on updating once the beta was out in the wild.
Maybe I’ll wait till tomorrow.
Still on old machine, new motherboard being RMA’d to NewEgg. Hopefully I’ll be back in new machine by New Years lol.