I own AMD Ryzen 7 2700X and Gigabyte AMD RTX 5700XT. My old GPU was NVIDIA GeForce GTX 1660.
Conky shows that, when I open an app or a browser, the RAM memory rectange gets full one second with “-580MB” and returns to the normal more one second, and gets full again with the same negative memory, and the same… At sometimes, it takes more or less than 10 seconds to load an app or a browser.
Not sure if it will help - but what the results from: conky -v and lua -v
and I would not mind knowing what conky statement is showing these results? Is it a graph - or a gauge - or something else?
I’m assuming this system is used for gaming (mine is set up the other way around - 3700x and rx-580) so some research is needed at my end…
1.11.5 shouldn’t be causing that kind of output that I can see - it only had troubles with ${execi} timings… 1.11.7 though, anything is possible!
If you aren’t seeing problems with the cairo built-in, lua 5.4 should be OK too. Hope someone with more gaming experience comes by, I’m off to do some research on the other stuff you’ve got loaded…
I use the conky-cairo package, which defaults to 1.11.3 - but allows you to specify which version you want. this includes the git version, which displays as 1.11.7. The PKGBUILD is set up to choose dependencies/bindings you wish to use (such as nVidia and Audacious). Having the nVidia bindings does not hurt its operation that I can detect on my AMD system - but I do leave it out given the choice! I have different builds on different distros (1.11.5 + lua 5.4 on EnOS, 1.11.7 + lua 5.4 on Arch, 1.11.3 + lua 5.3.5 on Arcolinux, 1.11.6 + lua 5.4 on Garuda). Conky cairo also pops a cou-ple of patches on the ‘newer’ versions - but I think they are only to fix the ${execi} problem…
Which ‘ghost’ problem is that? - doubled displays of some things? Double buffer not behaving? There some settings that interact unconventionally, especially with transparency enabled.
If I can just add, the thread you linked to that I posted was split off from another, and, in the other, I posted the solution, which in my case was unticking drivers in the ‘base and other packages’ which my system didn’t need, so I could install Endeavour. It looks from your list that you already did that on installing, and are far more tech-able than myself; I wouldn’t know if there were leaks, so well spotted! Could be the AMD drivers not fully finished yet? … or is that a dumb thing to say? I’m running 8gig swap, and I think your printout shows no swap? I’m running the LTS kernel. Have never tried linux-amd; didn’t even know it existed, lol. Just noticing differences, incase anything gives a clue.
It’s what I thought. When I noticed something wrong with the RAM memory, I have searched, I saw I am in the same boat that the AMD RX 5700XT of Linux who had the same bug.
But @freebird54 indicated Conky as guilty of the bug.
I used still linux. But the linux-amd is installed. I tested with the mirror mesagit, no bugs, but if the bug appears, I’ll report.
Yes, it easily could be conky, or a combination of things e.g. the amd kernel with conky, or something unique to a certain hardware combination, where actually the lts kernel would help.
Probably a big thing to do, but have you run a system without conky and with just the linux-lts? If the error is still happening then, on a vanilla system, we’ll be able to home in on what it could be (I say ‘we’, but I’m not very tech-able, whereas plenty of great people here are). Sometimes these adapted kernels can throw some errors, or may bring in changes that alter things e.g. I was using linux-zen until recently, but more intel patches have been included, and I changed to the LTS and am seeing no difference; system runs fine.
If at all possible, I’d suggest running a vanilla system … linux-lts, no conky, normal mesa (I run wine-staging now too, instead of tkg wine, and, again, seeing no difference and things run fine). Then, if it’s the kernel or conky that were the issue, that’ll come clear, and, if not, it’s easier to home in on what could be the issue e.g. test ram etc. Could even just be a loose connector or something. I hesitate to recommend changing bios, as that can introduce issues as much as it can fix them, but possibly worth a look into that. It could even be a desktop environment or browser bug.
Best testing I’ve ever seen anybody do; well done!
To my untrained eye, and from what you’ve posted, It looks like only bug fixes will sort conky, and sddm/lock screen. Running the LTS and mesa-git, without conky and with a different desktop environment, at the moment, looks to be the ticket to as trouble-free a time while waiting for fixes, which is bad, but at least you can get on with using your computer. I don’t run KDE or conky (am on Mate/Lightdm, plus LTS/mesa/wine-staging), so unfortunately can’t compare, but, with particularly the SDDM bug being so bad, fixes could come through quickly.
I ran the errands to investigate the bugs, errors and failures in Sway. I found that it was Redshift and wayland-egl. Sway does not recognise that wayland-egl, even if egl-wayland is installed. I replaced it with xwayland. But Redshift did n’t recognise wayland-egl or xwayland, I decided to simplify redshift-gtk -m xwayland to just redshift.
I’m running 8gig swap, and I think your printout shows no swap? I’m running the LTS kernel. Have never tried linux-amd; didn’t even know it existed, lol. Just noticing differences, incase anything gives a clue.
