[deleted]
On a second thougt, if I feel fit for it later, I'll try "Users who are still experiencing issue with Budgie and are using Intel graphics, does sudo eopkg it mesalib --reinstall help at all?" suggestion (can't quote well) or will see if can bring details regarding journal which at this point I can't.
The issue is I can't see the instructions from TTY so it will have to be by chrooting again so it's not "natural" for me.
EbonJaeger
Regarding method of getting (existing) logs. I had a way. It's not a recommendation, it's for those who may install anyway unless one else who fits to recommend, recommends it.
I think I could copy some logs while using a USB live with storage and also decided to take some logs to storage on the session while I was chrooting. Maybe such could be done from an OS on other disk as well, regardless of chrooting maybe too. Somehow. I don't know regarding permissions.
But it was easier for me and maybe it is easier than remembering the command but I did that only as a last resort since I'm going to install something else on the system soon anyway.
(my backup is OS agnostic as far as I know, so I am not afraid, though it takes some work and apps etc are not backed up in the way I chose, it can still bring back an OS like solus of any flavour/mint/mx, maybe zorin maybe even spiral etc, to function nicely in not so long time after an installation.)
Since the latest update Unicode input does not work anymore. I am using a keyboard that sends unicode with special characters and till last update it worked perfect for years. Also direct Unicode input by Ctrl+Shift+u prints u but after entering unicode hex and pressing enter no characer shows, all gets deleted. So I guess there is a problem in IBUS or IBUS configuration. IBUS daemon and related stuff are up and running as far as I could check. Could it be also a GTK problem? I don't know too much about the workings. Help would be appreciated.
I think we've been able to narrow down the issue to the keyboard layout applet and IBus. Still doing further investigating to find a fix.
For now, you can work around this by resetting the panel settings back to defaults, thus removing the applet from the panel. Run this command from a TTY:
dconf reset -f /com/solus-project/budgie-panel/
See the post by Reilly below.
EbonJaeger
I have my OS back (didn't try restart yet...)
Just installing element (and other software...) takes time so saying.
While I thought it didn't work, it did.
It took times, the command (or the other) from chroot took place after a while on login to desktop and solved it.
I don't know will exit from keyboard applet just in case.
P.S.
As EbonJaeger says, remove the language indicator from the panel itself on this stage 
Worked (done that next restart)
It may take time/be a bit quirky (sound temp issue?), but it helped me and other one and I hope for others too! You said it's a workaround, so thank you very much, and good luck I have sound working too, yes.
Thank you very much, EbonJaeger and rest of the team - the workaround is indeed working for me.
Just want to note that the dconf command didn't really reset my panel untill I added a trailing slash at the end of it ( .../budgie-panel/).
So if anyone's panel is still acting up after entering the command in tty the same way as mine did, feel free to try this one with the trailing slash at the end:
dconf reset -f /com/solus-project/budgie-panel/
RegularJogger Thanks for the note about the trailing /. Added it to the post above.
synth-ruiner can we get some info on what your system is? Specs, DE, etc?
<post deleted>
There was a micro-sync just now. gnome-mahjongg should be working now. I added a couple of ibus patches, hopefully that resolves the issues reported there.
dassuan Can you update again and see if this issue is still present?
synth-ruiner This one might also have been fixed by the ibus patches I just pushed to stable. Can you update again and test it?
An Acer Swift with 4GB memory, working flawlessly on Solus Budgie for years, is now k.o. after the last upgrade.
"Out of memory: Killed process 5180 (budgie-panel) total-vm:3929520kB, anon-rss:2865420kB, file-rss 0kB, shmem-rss:0kB, UID:1000 pgtables:5848kB oom_score_adj:0"
Only a white screen is left with the hint (analogously): "Sorry, there's a problem. Log tf off and try again"
Whenever I hear the word "OOM-killer" I get mad. It's driving me crazy on Sailfish, and it's bricking my laptop now. How can I debug this from CLI?
I did try some thing, and recommend the TTY (with the / as noted by RegularJoger. Thanks.) not the chroot solution
If you can remember it or having it in the shortcut or written etc. No worries, it's fine again for me in that regard.
The iBus update wasn't fixing the issue, but as I recovered the OS, the keyboard indicator and caps lock indicator were not in panel and also not in budgie, as I think should. So this time, using the solution with the added / on the TTY, I didn't need to remove those after unlike previous one (which was with 2 chroot commands, with waiting after login, and without the added / and before patch)
Robotmike The issue is being worked on. The Keyboard Layout applet doesn't seem to be playing nice with the new IBus update. The current workaround is to reset the Budgie panel settings from a TTY so the applet is removed: dconf reset -f /com/solus-project/budgie-panel/
EbonJaeger got the new ibus and psutils just now. I am rebooting. drum roll please
Alright, just did another sync to include reverting ibus to the previous version. I was able to reproduce the Budgie issue in a VM and this fixed it for me so hopefully this fixes it for everyone else.
️