Split: antiX-19.4 conky

[Member ModdIt]

Helpful

Up

0

::

#I was assuming that I can change the .conkyrc file in the live usb without persistence by removing the # in front

#That works for the current session only, if persistence isn’t being used. Next boot it goes back to original, in that case.

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 :-).

[Member calciumsodium]

Helpful

Up

0

::

Hi @Robin and @christophe,

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.

for 19.4 64-bit test OS

jakersfan@jakersfan:~
$ apt-cache policy conky
conky:
Installed: (none)
Candidate: 1.10.8-1
Version table:
1.10.8-1 500
500 http://ftp.us.debian.org/debian buster/main amd64 Packages
500 http://ftp.us.debian.org/debian buster/main i386 Packages
jakersfan@jakersfan:~
$ apt-cache search conky
antix-goodies – Various useful scripts for antiX.
conky-legacy – highly configurable system monitor (transitional package)
conky-legacy-all – highly configurable system monitor (all features enabled)
conky-legacy-all-dbgsym – Debug symbols for conky-legacy-all
conky-legacy-cli – highly configurable system monitor (basic version)
conky-legacy-cli-dbgsym – Debug symbols for conky-legacy-cli
conky-legacy-std – highly configurable system monitor (default version)
conky-legacy-std-dbgsym – Debug symbols for conky-legacy-std
conky – highly configurable system monitor (transitional package)
conky-all – highly configurable system monitor (all features enabled)
conky-all-dbg – highly configurable system monitor (all features enabled – debug)
conky-cli – highly configurable system monitor (basic version)
conky-cli-dbg – highly configurable system monitor (basic version – debug)
conky-std – highly configurable system monitor (default version)
conky-std-dbg – highly configurable system monitor (default version – debug)
jakersfan@jakersfan:~

for 19.4 64-bit official OS

demo@antix1:~
$ apt-cache policy conky
conky:
Installed: (none)
Candidate: (none)
Version table:
demo@antix1:~
$ apt-cache search conky
antix-goodies – Various useful scripts for antiX.
conky-legacy-all – highly configurable system monitor (all features enabled)
demo@antix1:~
$

I tried installing conky in the 19.4 64-bit official live USB OS by a simple sudo apt install conky. But it gave me an error. What is the best way to install conky?
I think we are getting closer to a solution?

demo@antix1:~
$ apt-cache search conky
antix-goodies – Various useful scripts for antiX.
conky-legacy-all – highly configurable system monitor (all features enabled)
demo@antix1:~
$ sudo apt install conky

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

[sudo] password for demo:
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package conky is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
conky-legacy-all

E: Package ‘conky’ has no installation candidate
demo@antix1:~
$

[Moderator christophe]

Helpful

Up

0

::

conky-legacy-all is the package name for the conky that comes with antiX.
Package names can be confusing…

confirmed antiX frugaler, since 2019

[Member Xecure]

Helpful

Up

0

::

calciumsodium, on your antiX 19.4 (final, doesn’t matter if it live) )please update all packages and after run (as normal user)
cp /etc/skel/.conkyrc $HOME/.conkyrc

Then, un-comment the last two lines of $HOME/.conkyrc and toggle conky off and then on.

If you still see no battery info in conky, we will explore other possibilities.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member calciumsodium]

Helpful

Up

0

::

Hi @Robin and @christophe,

for the 19.4 64-bit official, conky-legacy-all is already installed:

conky-legacy-all is already the newest version (1:1.9.0-6).

I checked the 19.4 64-bit test, it also has the 1.9.0-6 conky-legacy-all version. A question I have is when I use the command, apt-cache policy conky, why is there a difference between the 19.4 test and official versions?

Hi @Xecure,
I will try your suggestion this afternoon.

I am actually happy using the 19.4 test version, but I want to help solve the conky issue for other users that may want to use it if they have the 19.4 official version.

[Member Robin]

Helpful

Up

1

::

calciumsodium wrote:

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).

calciumsodium wrote:

for 19.4 64-bit test OS
jakersfan@jakersfan:~
$ apt-cache policy conky
conky:
Installed: (none)
Candidate: 1.10.8-1

calciumsodium wrote:

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:

calciumsodium wrote:

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.

ModdIt wrote:

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.

calciumsodium wrote:

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.

[Member Xecure]

Helpful

Up

0

::

Robin wrote:

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.

Better yet
cat ~/.conkyrc | tail -3
so we can avoid non relevant conky text

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member calciumsodium]

Helpful

Up

0

::

For the 19.4 64-bit test system where the battery status is displayed, this is what I get

jakersfan@jakersfan:~
$ cat ~/.conkyrc | tail -10
${color3}${alignc}${execi 1000 persist-enabled}
${execi 1000 acpi 2>/dev/null | grep -q . && echo "Battery: "}${execi 10 acpi -b 2>/dev/null | cut -d" " -f3,4 | sed 's/,$//'}

jakersfan@jakersfan:~
$ apt-cache policy conky-legacy-all
conky-legacy-all:
  Installed: 1:1.9.0-6
  Candidate: 1:1.9.0-6
  Version table:
 *** 1:1.9.0-6 500
        500 https://mirror.freedif.org/MXLinux/repo/antix/buster buster/main amd64 Packages
        100 /var/lib/dpkg/status
jakersfan@jakersfan:~
$ 

[Member calciumsodium]

Helpful

Up

0

::

For the 19.4 64-bit final/official system (live usb without persistence) where the battery status is not displayed, this is what I get

demo@antix1:~
$ cat ~/.conkyrc | tail -3
${alignc}${execi 1000 persist-enabled}
#Battery: ${battery_percent BAT0}% ${alignr}${color8}${battery_bar 8,70 BAT0} # You may need to change BAT0 to BAT1 or add the same line again if you have more then one battery. 
${execi 1000 acpi 2>/dev/null | grep -q . && echo "Battery: "}${execi 10 acpi -b 2>/dev/null | cut -d" " -f3,4 | sed 's/,$//'}
demo@antix1:~
$ apt-cache policy conky-legacy-all
conky-legacy-all:
  Installed: 1:1.9.0-6
  Candidate: 1:1.9.0-6
  Version table:
 *** 1:1.9.0-6 500
        500 http://la.mxrepo.com/antix/buster buster/main amd64 Packages
        100 /var/lib/dpkg/status
demo@antix1:~
$ 

• This reply was modified 1 year, 11 months ago by calciumsodium.
• This reply was modified 1 year, 11 months ago by calciumsodium.

[Member calciumsodium]

Helpful

Up

0

::

Xecure wrote:

calciumsodium, on your antiX 19.4 (final, doesn’t matter if it live) )please update all packages and after run (as normal user)
cp /etc/skel/.conkyrc $HOME/.conkyrc

Then, un-comment the last two lines of $HOME/.conkyrc and toggle conky off and then on.

If you still see no battery info in conky, we will explore other possibilities.

Using @Xecure ‘s suggestion above works!!!

I used sudo cli-aptiX to update all packages and copied the /etc/skel/.conkyrc file to the home directory.

I then uncommented the last line in that .conkyrc file:

demo@antix1:~
$ cat ~/.conkyrc | tail -3
${alignc}${execi 1000 persist-enabled}
#Battery: ${battery_percent BAT0}% ${alignr}${color8}${battery_bar 8,70 BAT0} # You may need to change BAT0 to BAT1 or add the same line again if you have more then one battery. 
${execi 1000 acpi 2>/dev/null | grep -q . && echo "Battery: "}${execi 10 acpi -b 2>/dev/null | cut -d" " -f3,4 | sed 's/,$//'}
demo@antix1:~
$ 

Please see attached screenshot:

Thank you to @christophe, @Robin, @Xecure.
I am learning a lot from you.

Attachments:

1. 

   screenshot.jpg
   

[Member Xecure]

Helpful

Up

0

::

@calciumsodium. Great new. I suspect there was a small typo somewhere, but sometimes it is impossible to find. Good work persisting through it and thanks for all the testing you do.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Author]

Posts