How to fix Conky's Ram and Storage Reading :(
- Thread starter archiman.ch5
- Start date
-
- Tags
- arch linux conky
Without seeing your conky config, it would be difficult to tell!
OP
archiman.ch5
Member
OK, taking a more detailed look at the image you’ve posted - The storage part looks OK to me.
The disk usage on the drive is only 31.8Gb.
The total storage space is just over 900Gb.
A quick bit of mental arithmetic puts the total disk usage to be between approximately 3% and 4%. So that bar looks correct to me.
The swap usage again is only roughly ~1%. So that looks good.
The only thing that looks off is the RAM reading..... -3.5Gb. I’m not sure what is causing this. The bar is wrong because the reading for the amount of memory used is wrong.
And the conky config itself looks ok. Maybe it’s a bug with conky itself?!
You’re running arch, so you’re on the bleeding edge. So perhaps this will be fixed the next time conky is updated?!
The disk usage on the drive is only 31.8Gb.
The total storage space is just over 900Gb.
A quick bit of mental arithmetic puts the total disk usage to be between approximately 3% and 4%. So that bar looks correct to me.
The swap usage again is only roughly ~1%. So that looks good.
The only thing that looks off is the RAM reading..... -3.5Gb. I’m not sure what is causing this. The bar is wrong because the reading for the amount of memory used is wrong.
And the conky config itself looks ok. Maybe it’s a bug with conky itself?!
You’re running arch, so you’re on the bleeding edge. So perhaps this will be fixed the next time conky is updated?!
OP
archiman.ch5
Member
i face this problem only in arch... i use garuda linux which is based on arch and its working fine
I have seen this "negative RAM" bug in Conky, sometimes in a distro, sometimes in other distros, for more than 1 year, now.
First time, I have seen this bug in PCLinuxOS, August 2019 ─ but its team worked and corrected it.
Then, it happened in openSUSE Tumbleweed, at least in December 2019.
I cannot discard other cases, last year, because I didn't use a standard "label" to it in my screenshots, back then, and it is hard to find out now.
This year, I have found many cases ─ and the RAM usage at startup, when Conky turned back from "negative" to positive amount of RAM:
Code:
2019-08-16 - PCLinuxOS
2019-08-16 - PCLinuxOS
2019-08-16 - PCLinuxOS
2019-08-16 - PCLinuxOS
2019-08-29 - openSUSE
2019-12-19 - openSUSE 486 MiB
2019-12-19 - openSUSE 486 MiB
2020-01-07 - openSUSE 482 MiB
2020-07-16 - Fedora 607 MiB
2020-07-16 - Arch 531 MiB
2020-07-16 - Void 478 MiB
2020-07-16 - Void 478 MiB
2020-07-19 - Mageia 601 MiB
2020-07-23 - Mageia 597 MiB
2020-07-23 - Fedora
2020-07-23 - Arch 516 MiB
2020-07-23 - Arch 519 MiB
2020-07-29 - Arch 518 MiB
2020-08-01 - Void 491 MiB
2020-08-01 - Mageia 613 MiB
2020-08-01 - Fedora 673 MiB
2020-08-01 - Fedora 673 MiB
2020-08-01 - Arch 531 MiB
2020-08-02 - Fedora 662 MiB
2020-08-02 - Fedora 660 MiB
2020-08-02 - Arch 533 MiB
2020-08-19 - Arch 535 MiB
2020-08-19 - Arch 536 MiB
2020-08-22 - Arch 546 MiB
2020-09-02 - Arch 535 MiB
2020-09-04 - Arch 546 MiB
2020-09-19 - Arch 556 MiB
2020-09-19 - Arch 562 MiB
2020-09-24 - Arch 553 MiB
2020-10-04 - Arch 554 MiB
2020-10-05 - Arch 556 MiB
2020-10-05 - Arch 559 MiBBack in July-August 2020, it stopped in Fedora, openSUSE, Mageia. ─ Now, Conky says they all use 900+ MiB RAM at startup ─ and that Void uses 700+ MiB RAM at startup.
I have never seen "negative" RAM usage in Debian ─ but now Conky says Debian is using 900+ MiB RAM at startup (and I don't believe it).
Just in Arch Conky keeps showing "negative" RAM usage ─ but at least, it doesn't show 900+ MiB in Arch.
EDIT
Negative RAM usage - Bug # 877 - August 2019
https://github.com/brndnmtthws/conky/issues/877
High CPU usage with conky (...) - Bug #876 - August 2019
https://github.com/brndnmtthws/conky/issues/876
Fix for #877 #878 - Aug 2019
https://github.com/brndnmtthws/conky/pull/878
Negative / too low memory reading - Bug #886 - September 2019
https://github.com/brndnmtthws/conky/issues/886
Last edited:
