[Solved] - Tower's 1st [no, 3rd] Hard-Reset since clean-reinstall.

[kdemeoz]

Oh rats Pliny -- it took me ages to compose my previous reply, & once i'd posted it, i saw that you had added some stuff to the end of your original post -- haven't had time to look into any of that, but will later - thanks.

And might I say your previous reply was written with the mastery of a great Mozart symphony.
!st.... I was not suggesting that you make some of them changes permanent. Was only to see if there was any improvement over the next few days. You could back up your settings with Timeshift before doing any changes.
2nd....The history.log was only useful if you have a good idea when your problems started.
3rd....Did you at least try........

Code:

sudo apt-get install --reinstall xserver-xorg-input-all kwin

4th.... It is only advice, so you obviously must make the decision of whether it sounds right for you. I have found a lot of glitches can be remedied by elimination, at least that's how I stratagize.
5th.....Yeah I forgot those links the first post so I edited them in. Good luck

Hi Pliny

First, thanks for your poetic kindly words. Second, i love your animated avatar - that's very clever [not to mention boppy].

Yes i did certainly understand your advice was meant as temporary changes for troubleshooting purposes only, not permanent. I'm sorry i did a poor job of explaining. What i had tried to explain (i hope i do a better job this time] is that if, say, my current preferred Workspace Appearance settings "suite" of Breeze widgets, Plastik Window Decorations, Oxygen Desktop Theme, my much-customised system Colours, Oxygen Icons, Crux GTK2 Theme, Emacs GTK3 Theme, Hicolour Icon theme, & GNOME Fallback Icon theme, turned out to be THE root cause of these rare freezes, then i would simply have to accept that i will keep having said occasional freezes, given i am simply not willing to have to use [eg] the crappy Breeze GTK3 Theme, or Breeze Icons, or especially not the lousy Breeze Desktop Theme, as my permanent arrangement. 

Now, take all my [sincerely-meant] words just written, & combine with this: these freezes are RARE. If these were a daily or weekly occurrence, my attitude would be very different, & i would feel much more displeased with Maui. But they are not frequent at all. Sure, i am always upset/cranky when they do occur, but the reality is they hardly ever actually occur. So, on balance, my calculus is that even IF my settings WERE to be the root cause, i am prepared to have these unpleasant RARE freezes, but in-between enjoy a system with aesthetics & functionality i LOVE, rather than no more occasional freezes but all the time a system whose aesthetics & functionality i intensely dislike. 

Obviously, i hope the freeze root-cause is something else entirely, & that sooner or later i will discover & solve it. You might well disagree, & think me nuts, but at least i hope i explained a bit better this time.

Timeshift -- i discovered this several months ago, & back then read http://www.teejeetech.in/p/timeshift.html. In the end i did not try it, but thought it sounded potentially great. I chickened-out for two reasons; [1] does it really work, is it completely safe & reliable? [2] is it specifically compatible with Maui? The "latest" comments on his page are now pretty old, so how can i tell if it remains still viable for newer distros [like Maui]? Logically, the fact that you've now mentioned it to me must mean that you use it, know it works, & fully trust it...?

If i was to try...

Code:

sudo apt-get install --reinstall xserver-xorg-input-all kwin

...would it overwrite all my present personalisation settings in .local & .kde ? Is there any downside to me trying it, given i now have a nicely-customised & [mostly] well-running system?


I hope to have time later today to read those links you gave. 


Mad Speculation? --> I like to, & do, run my /tmp as a ram-disk via tmpfs in my fstab file:

Code:

tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

I do this partly for longterm privacy [given /tmp thus gets wiped at reboot], & partly for possible longer SSD life [less system & programs (eg, browsers) short-term file writing to SSD]. I'm aware that the default setting allocates 50% of available RAM to tmpfs /tmp tmpfs. As i have 32 GB RAM, nominally ~16 GB is allocated. In practice, every time i monitor /tmp it seems to sit at ~15.2 GB free [per Dolphin].

So here's my crazy "what-if" speculation... what if occasionally/rarely, "something" [what???] happens [goes wrong?] that suddenly eats up all the remaining free space in /tmp... wouldn't that then crash the system, possibly manifesting as one of those rare freezes? There's probably so many holes in this speculation that you can drive a truck through them, & i'm extremely reluctant to stop running /tmp in RAM "just in case" [given i have no proof, & it's doubtless a stupid thing to worry about as a potential root cause of the freezes]. Anyway, i do monitor /tmp in Dolphin very often, & have never yet seen any evidence of dangerously low free space in it.