On Sunday July 03 2022 05:41:59 Duncan wrote: >My CPU is I think even older, AMD fx6100 so around a decade old now. But >I do have 16 gig of RAM and upgraded to all SSDs (on paired Samsung EVO >SSDs in btrfs raid1 mode), which made quite a difference compared to the >old spinning-rust drives.
This is interesting. I wasn't going to chime in because I thought this had to be an issue with too-new hardware. But if Qt and/or Linux now start to cause CPU or GPU burning in hardware they should have perfect support for by now ... something is fishy. Some thoughts for the OP: - does the issue persist if you log in under a non-Qt DE - xfce would be a good, lightweight choice? - see if you can identify a "pure Qt" application, ideally one that come with Qt (ideally the Assistant, Linguist, etc) which shows the issue. Then, install the same Qt version from Qt's own binaries, and as long as the issue reproduces with install older versions. In short, try to identify if this is some kind of regression in Qt. Qt's Creator would be a good candidate for testing except they only ship a build that uses the latest Qt version. - the Intel driver (or at least the i915 one) has a number of parameters you can set at boot or, presumably, before launching the graphic environment. There is a lot of information out there on what parameter settings to use in case of specific performance or stability problems. Have you looked into those? - a bit of a long shot: have you tried different kernels? Newer (or older!!) ones, or a home-build with, say, the ConKolivas patches, or a Liquorix kernel? NB: Qt does seem to be the culprit here; if I had to point fingers I'd look at the WebEngine and QML components which both have their own graphic engines. R.
