Robin
I think that conky was installed in the 19.4 64-bit test but not in the 19.4 64-bit official versions. Is this correct? Please see output below.
No, this only says the package named “conky” is not installed on either of the systems. Read carefully, both show Installed: (none).
for 19.4 64-bit test OS
jakersfan@jakersfan:~
$ apt-cache policy conky
conky:
Installed: (none)
Candidate: 1.10.8-1
for 19.4 64-bit official OS
demo@antix1:~
$ apt-cache policy conky
conky:
Installed: (none)
Candidate: (none)
But this doesn’t mean it isn’t installed. Admittingly, this is a bit confusing. Christophe set you on the correct trace already by heading you towards conky-legacy-all. It is due to the fact that a program is delivered by debian and other package maintainers (as also antiX) in more than one flavour.
To see all flavours you can use the command
$ apt-cache search conky
as you did already before. But be aware of a pitfall on antiX live systems: Apart from installed systems the cache apt uses is not stored between sessions. So you need to execute
sudo apt-get update
first, otherwise you will search in an empty cache, and you will not find anything with the commands from above.
Store in mind: If you ever happen to see something like:
E: Package ‘conky’ has no installation candidate
for any program you’d expect to be found by apt on a live system of antiX this means you can bet you did miss to apt-get update after reboot. This is true still when using persistence, since this (as most) overhead is excluded from getting stored in persistence.
I think doing a personal remaster should make that change permanent, I do that after all bigger upgrades and to preserve desktop
changes while keeping boot and shutdown times as fast as the system allows. Persistence is a fantastic feature but does have an
overhead in that files have to be integrated, compressed decompressed, costs time and computer power, makes me impatient :-).
If I’m not mistaken you need to have a persistent system in order to be able to collect all the changes and installations you apply to your system in succeeding sessions in order to create a remaster from it in the end. I never did it other than that, having persistence turned on. But this is a question to be discussed by people with knowledge about the depths of live circuitry of antiX. Sorry I can’t tell you anything detailed about that part. I just use it 🙂
But back to your conky thing.
From Christophes posting above you could have taken, the right choice from the apt-cache search results for antiX is
apt-cache policy conky-legacy-all
and from my writing here you do know by now that this will work on a live system only after having given
apt-get update
before, at least once after reboot. So please let us know the result.
I think we are getting closer to a solution?
Yes, if you’d post the output of
cat ~/.conkyrc
from both systems so we can look into it whether there is something inside keeping it from displaying the battery status correctly.
Alternatively just attach these two files to your posting.
Windows is like a submarine. Open a window and serious problems will start.