kwin_x11[11453]: Could not get Interfaces. "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
I did have several tabs open with SSH connections just before i rebooted the system after the update this afternoon so i suppose it is possible that its something to do with the network, but iv closed all the tabs on it now. Iv deleted all the ~/.cache/yakuake but it didnt help. Im just guessing, really.
If i could save all my yakuake setting/profiles/skins etc i would try uninstalling but i cant be sure how.
I have tried rolling it back to yesterdays version but still does that same.
Its not just open/close of the main yakuake window, it also freezes the system for 20 seconds ish when i try to change the settings in the GUI.
Ok so i have uninstalled it and deleted everything i could find to do with yakuake (settings and cache). Rebooted and reinstalled. It has not helped.
It definitely has something to do with the size of the window. If its at 100% by 100% then it will freeze often when opening/closing but not if its only at 90% width/height.
Trying to slide these size sliders in the GUI also makes it freeze almost every time i touch them.
Ok, after 24 hours of searching and very nearly reinstalling i found a couple of posts which i have linked below.
The remedy was simple when you know. It was the ~/.config/kwinrc file that was causing the problem. It seems that after system updates it has been known to do this, causing all sorts of problems. I renamed it, rebooted, sorted out the settings that had now been set back to default, and it was all working again! Phew, that was close ^^.
Yeah that one was a doozy, the errors themselves were from different applications and they didn’t mention kwin anywhere directly. I was stuck with it for 2+ months, glad the “fix” worked for you! Though, it would be nice for the root cause to found and handled to prevent this from happening again.
Yea that was quite something ^^. It is the randomness of the problems that become visible to the user that makes it so hard to deal with. I was sure that the journalctl log was a red-herring, but in the end it was the path i needed to walk down. Just glad it did turn out to be a single file, as i had my USB stick in hand but really couldn’t face it.
Chers for saving me a whole load of work, and a big thx /s to Manjaro for this still being a thing, lol.