You want to make a suggestion fine.
But, don’t you ever tell me what I “better do”, you have no authority over me.
Frankly, I have no issues running AIR on my machines, just as I have never in my life needed to use xrandr to correct a garbled screen.
Now, with that said, I’ve been running AIR on this machine for over an hour and no freeze, crash, or lockup, so far.
I’m going to keep it this way until tomorrow, or until I have an issue.
Let’s see what happens, shall we.
And yet, your the only one I’ve seen so far reporting this “issue”.
Your not overclocking, or doing anything else unconventional with your systems I hope?
The reason I ask, what your describing sounds more like a hardware failure than a theme issue.
I have seen what your describing before, but it had nothing to do with a theme, but was typically a driver setting and/or bug. In one case it was the opengl settings in the kwin compositor that were wrong, in another instance it was an x11 driver setting.
Just a thought, but could it not be possible that this theme may just be the trigger in your case, and that some other setting, and/or driver combination your trying to use, is not actually supported by your hardware, causing these issues?
PS. I’m running the same test on two of my other systems, and still no issues with them either.
It’s possible that not directly AIR is at fault but this is sort of tricky to narrow down for me.
Also, people kept telling me all my life that I am the only one person in the world who complains about a certain thing, it is the oldest trick in the book, like calling people antisemites for no reason. kinda lame.
with latest NRR 4.18 kernel etc. here is the bug report:
all themes work, except “Air”
an empty small grey notification window (or plasmoid or wtf) is shown
no keys or mousebuttons work except Alt-TAB and Alt-SPACE, so in krunner , ksysguard can be launched
so it feels as if the KBD + MOUSE focus is “away”
related KDE bugs are pretty chaotic to follow or to make sense of
load on one of the cpus is 100% on the plasmashell process constantly
when attaching nemiver to process “plasmashell” it coredumps of course
[*]ksyslog gives various output difficult to make sense of
here is a workaround that worked for me:
now the Air theme no longer freezes on occasion so far, so the root cause cannot be the “Air” theme itself, I guess.
but there seems to be a bug still hidden somewhere…
post scriptum : sorry, I found that the fix is worthless. e.g. “right click / unlock widgets” immediately silently freezes KDE (“daemon seems to steal focus”). I went back to a different theme. Cannot narrow down the problem.
Like I’ve said before, I could not reproduce this issue on any of my test bed systems.
With that said, If those tweeks work for you then great.
However, others need to keep in mind that such modifications are use at your own risk.
Any deviations in base system settings from what we ship, make virtually impossible to track down, and/or reproduce, any issues that may arise from that point forward.