autocrosser1

Yes--I design themes to "fit" a number of different uses, but always note that the individual will have to customize the theme to "taste". I have always thought that it is a good thing for people to learn how to do things for themselves. That is the main reason I don't conform to things like Conky Manager---I think that someone needs to know how to do things the manual way. - Dec 21 2019

Looking good!! Glad to see you've run with it a bit more. - Dec 21 2019

Good to hear it.....have fun with it. - Apr 18 2019

${alignr}${offset -6}updates < ${execi 360 aptitude search "~U" | wc -l | tail} > ─┘
try doing execi 360 rpm search instead.....not sure if that would work, I'm not good in low-level rpm commands. - Apr 17 2019

+Looks Good!! - Apr 17 2019

Looks Good---I must admit I do my Conkys on a 34" widescreen...It's the one I use most of the time--satisfies wanting a terminal look for my conky. The "own_window_argb_value" & "own_window_color" are needed for use with Gnome3 in debian distros....I don't know what the update request for RPM-based distros need...As it is coded--it uses a dpkg code that is Debian-specific. - Apr 17 2019

Well, yes--Conky will still use the old format, but will "complain" every time it starts that it had to convert to the new format. I doubt that there is anyone out there using 1.09 anymore, so I just do everything in the new format anymore. - Nov 21 2019

OK--take a look at Graph2 & tell me what you think.... I made sure we are both credited --the script header reflects that also. I did do the update to Conky 1.10 on the script & changed things up a bit :) - Nov 19 2019

Looks good---mind if I use the graphs/general idea & play with them a bit? - Nov 19 2019

10 the best - Oct 04 2019

Yes--that would be much easier. - Jul 25 2019

And yes, I am running Lua 5.3 also. - Jul 25 2019

Hmmm.. As this was written several years ago I included a way to define if conky was 1.10 or not.. The detection is towards the bottom of the script change the line:

if info.conkyversiondetection == "1.10" then
df=conky_ownpreexec("df -h | grep ^/dev/s | sort | grep -v 'efi' | grep -o 'sd[^ ]'")

To:

if info.conkyversiondetection > "1.10" then
df=conky_ownpreexec("df -h | grep ^/dev/s | sort | grep -v 'efi' | grep -o 'sd[^ ]'")

And see if that makes a difference. Also, I watched your presentation & saw that I forgot the RGB value for purple.... In the global variables section add:

themes.purple={148,0,211}

To fix that problem.

I will look in more detail this weekend....It is possible that the conky_ownpreexec may be needed to be rewritten--can you verify that this runs correctly?

df -h | grep ^/dev/s | sort |grep -o '[^ ]*$' | grep -v 'efi'
- Jul 25 2019

I will be able to take some time this weekend to look at the problem...Is it just the file display or is there a larger problem? - Jul 24 2019

Hello Erik....
With only 1 partition the output should be root (/)...Normally I would have 2 partitions ( / & home). Was developed for/on Debian. If this answers your question---great--if not I will be available this weekend to look into it more. - Jul 17 2019

OK--I played around with it.....This is the revised top segment:

-- user parameters, change them if you want.
use_theme = "blue" -- can be 'red','green','silver','gold','black','maroon','sienna', 'purple', 'white', 'blue' or 'default'
squash_cpu_cores = "no" -- display overall cpu speed, not per core
battery_low_alert = 10 -- low battery level alert, for laptops.
show_cpu = "yes" -- yes, detect CPU's presence and show CPU load
show_cpu_temp = "yes" -- yes, show cpu temp
show_gpu_temp = "yes" -- yes, show gpu temp
show_storage = "yes" -- yes, detect and show attached storage devices
show_memory = "yes" -- yes, show internal and swap memory
show_network = "yes" -- yes, detect and show network information
show_system = "yes" -- yes, show system info's such as cpu + gpu temp, fan speed cpu + chassis, uptime
show_processes = "no" -- yes, show running processes

------------------------------------------------------------------------
-- nothing exciting beyond here, trust me.. (see notes for moding use)
------------------------------------------------------------------------

require 'cairo'

-- global variables
themes={}
themes.red={.65,0,0}
themes.white={256,256,256}
themes.green={0,.65,0}
themes.silver={.752,.752,.752}
themes.gold={.831,.686,.215}
themes.black={.031,.031,.031}
themes.maroon={.501,0,0}
themes.sienna={.627,.321,.176}
themes.blue={0,0,256}
themes.tred=0
themes.tgreen=0
themes.tblue=0

And the lower area:
if conky_window == nil then return end
local cs = cairo_xlib_surface_create(conky_window.display, conky_window.drawable, conky_window.visual, conky_window.width, conky_window.height)
cr = cairo_create(cs)

-- detect hardware
conky_detect_hardware()

updates=tonumber(conky_parse('${updates}'))

-- default theme colors
themes.tred=.61
themes.tgreen=.81
themes.tblue=1

-- theme colors
if string.lower(use_theme) == "red" then
themes.tred=themes.red[1]
themes.tgreen=themes.red[2]
themes.tblue=themes.red[3]
end
if string.lower(use_theme) == "green" then
themes.tred=themes.green[1]
themes.tgreen=themes.green[2]
themes.tblue=themes.green[3]
end
if string.lower(use_theme) == "silver" then
themes.tred=themes.silver[1]
themes.tgreen=themes.silver[2]
themes.tblue=themes.silver[3]
end
if string.lower(use_theme) == "gold" then
themes.tred=themes.gold[1]
themes.tgreen=themes.gold[2]
themes.tblue=themes.gold[3]
end
if string.lower(use_theme) == "black" then
themes.tred=themes.black[1]
themes.tgreen=themes.black[2]
themes.tblue=themes.black[3]
end
if string.lower(use_theme) == "maroon" then
themes.tred=themes.maroon[1]
themes.tgreen=themes.maroon[2]
themes.tblue=themes.maroon[3]
end
if string.lower(use_theme) == "sienna" then
themes.tred=themes.sienna[1]
themes.tgreen=themes.sienna[2]
themes.tblue=themes.sienna[3]
end
if string.lower(use_theme) == "purple" then
themes.tred=themes.purple[1]
themes.tgreen=themes.purple[2]
themes.tblue=themes.purple[3]
end
if string.lower(use_theme) == "blue" then
themes.tred=themes.blue[1]
themes.tgreen=themes.blue[2]
themes.tblue=themes.blue[3]
end

Report back with the results..change the 3rd number to change the intensity of the blue. - May 24 2019

Make VERY sure to follow format: each section is an if---end group. - May 23 2019

Forgot..there is a lower section that needs mod also....look for the line:

updates=tonumber(conky_parse('${updates}'))

-- default theme colors
themes.tred=.61
themes.tgreen=.81
themes.tblue=1

-- theme colors

And add:
if string.lower(use_theme) == "blue" then
themes.tred=themes.blue[1]
themes.tgreen=themes.blue[2]
themes.tblue=themes.blue[3]
- May 23 2019

Just so you know--my email is debianmainuser@gmail.com I do beta testing for Debian. - May 23 2019

OK--its a bit more complex as we never included a blue variant. Goto the System_Bar.lua--read thru the top section & just below it you will see a user parameters section....first line is user theme color....keep that in mind & goto "nothing exciting beyond here, trust me" --just below that is the --global variables line. Find what exact color of blue you want in an RGB format, then add it into the "themes" group---format as--"themes.blue={ R,G,B}--look at the way other colors are formatted for example (make sure to add the . before the value). Make sure to leave the "themes.tblue as it is. After you have created your blue theme, go back to the user area & add "blue" as a useable theme color--lastly, modify the use_theme = "blue" & save the lua. You should then be able to reload the Conky & have it in Blue. As you can see, we were thinking about automating the lua....look at the options & change to your liking. - May 23 2019

I understand the Nvidia vs AMD card thing--I've only used Nvidia for the last 10 years or so & have not explored the temp checking for AMD....That being said, I only create manual config Conkys----I believe that people need to "get under the hood" of the code to see how it works...gives a better understanding of what you are using. Glad you like what you see & good that you have delved into the code to see what you don't need. As you can tell, this Conky type was a collaboration between Moob, Soundrolf & myself......took a couple of months to iron out the bugs to the point it is...I tend to code a few times a month & create whatever I'm "liking" at that time.....feel free to try some of the others--I have a varied collection. - May 23 2019

8 great - Jul 13 2019

Moob!!!! Good to hear from you. How are you doing? - May 25 2019

Yes--I had talked about ifconfig with Moob--not supported anymore...the net//carrier makes me ask..are you using a regular desktop? Do me a favor & try this Conky: https://www.pling.com/p/1006484/ It's one of mine from about the time when Moob & I were collaborating. It uses some of the same scripts in the lua file, but the problems you are having are not in it. - May 23 2019

I don't know if Moob is active anymore....could you report what the errors are? - May 22 2019

+ - Apr 22 2019

+Looks Good!! - Mar 23 2019

Thank You. - Mar 11 2019

Well--I reported too soon...The first line (cpu 1 to 4) reports load, but the lines after do not (5 to 8 & 9 to 12) Those lines all report load @ 93%. I'll mess with it over the next couple of days & try to see what is going on...... - Sep 11 2018

Just downloaded it & it works---Only thing I need to do is enlarge the main box-showing 12 cpu graphs tends to mess up the look :) - Sep 11 2018

Hmmm--line 1073 is about Cpu names.....Why would it refer to network interface info? - Sep 04 2018

Hmmm-Strange, I uncommented line 418 & changed cpu detection from "no" to "yes"---And get this error:

conky: llua_do_call: function conky_check_network_interfaces execution failed: /home/dean/.conky/lines/lines.lua:1073: attempt to perform arithmetic on local 's' (a nil value)

Not sure why a cpu test function would cause this line error.
- Sep 04 2018

For some reason it's shorting lines, so:
All the term output looks good:

dean@debian:~$ sensors | grep -iw core
Core 0: +53.0°C (high = +84.0°C, crit = +94.0°C)
Core 1: +51.0°C (high = +84.0°C, crit = +94.0°C)
Core 2: +47.0°C (high = +84.0°C, crit = +94.0°C)
Core 3: +58.0°C (high = +84.0°C, crit = +94.0°C)
Core 4: +51.0°C (high = +84.0°C, crit = +94.0°C)
Core 5: +45.0°C (high = +84.0°C, crit = +94.0°C)
dean@debian:~$ sensors | grep -iwE 'core.*high'
Core 0: +44.0°C (high = +84.0°C, crit = +94.0°C)
Core 1: +43.0°C (high = +84.0°C, crit = +94.0°C)
Core 2: +50.0°C (high = +84.0°C, crit = +94.0°C)
Core 3: +44.0°C (high = +84.0°C, crit = +94.0°C)
Core 4: +61.0°C (high = +84.0°C, crit = +94.0°C)
Core 5: +40.0°C (high = +84.0°C, crit = +94.0°C)
dean@debian:~$ cat /proc/cpuinfo | grep 'model name'
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
dean@debian:~$ cat /proc/cpuinfo | grep 'processor'
processor : 0
processor : 1
processor : 2
processor : 3
processor : 4
processor : 5
processor : 6
processor : 7
processor : 8
processor : 9
processor : 10
processor : 11

Also changed the "connections" box by 20px to accommodate long addresses: conky_wired_tab_connections(tabwidth+40,starty+tabheight/2+190,300,200,"Arial",10,themes.tred,themes.tgreen,themes.tblue)
- Sep 03 2018

First--noticed that connections box is a bit short--changed by 20px to accommodate long addresses: conky_wired_tab_connections(tabwidth+40,starty+tabheight/2+190,300,200,"Arial",10,themes.tred,themes.tgreen,themes.tblue)

Term output:

dean@debian:~$ sensors | grep -iw core
Core 0: +53.0°C (high = +84.0°C, crit = +94.0°C)
Core 1: +51.0°C (high = +84.0°C, crit = +94.0°C)
Core 2: +47.0°C (high = +84.0°C, crit = +94.0°C)
Core 3: +58.0°C (high = +84.0°C, crit = +94.0°C)
Core 4: +51.0°C (high = +84.0°C, crit = +94.0°C)
Core 5: +45.0°C (high = +84.0°C, crit = +94.0°C)
dean@debian:~$ sensors | grep -iwE 'core.*high'
Core 0: +44.0°C (high = +84.0°C, crit = +94.0°C)
Core 1: +43.0°C (high = +84.0°C, crit = +94.0°C)
Core 2: +50.0°C (high = +84.0°C, crit = +94.0°C)
Core 3: +44.0°C (high = +84.0°C, crit = +94.0°C)
Core 4: +61.0°C (high = +84.0°C, crit = +94.0°C)
Core 5: +40.0°C (high = +84.0°C, crit = +94.0°C)
dean@debian:~$ cat /proc/cpuinfo | grep 'model name'
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
model name : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
dean@debian:~$ cat /proc/cpuinfo | grep 'processor'
processor : 0
processor : 1
processor : 2
processor : 3
processor : 4
processor : 5
processor : 6
processor : 7
processor : 8
processor : 9
processor : 10
processor : 11


- Sep 03 2018

And:

dean@debian:~$ sensors | grep -iw core
Core 0: +51.0°C (high = +84.0°C, crit = +94.0°C)
Core 1: +60.0°C (high = +84.0°C, crit = +94.0°C)
Core 2: +54.0°C (high = +84.0°C, crit = +94.0°C)
Core 3: +58.0°C (high = +84.0°C, crit = +94.0°C)
Core 4: +58.0°C (high = +84.0°C, crit = +94.0°C)
Core 5: +49.0°C (high = +84.0°C, crit = +94.0°C)
- Sep 03 2018

Sensors looks like:

dean@debian:~$ sensors
it8792-isa-0a60
Adapter: ISA adapter
in0: +1.89 V (min = +0.00 V, max = +2.78 V)
in1: +1.49 V (min = +0.00 V, max = +2.78 V)
in2: +2.78 V (min = +0.00 V, max = +2.78 V) ALARM
+3.3V: +1.68 V (min = +0.00 V, max = +2.78 V)
in4: +1.21 V (min = +0.00 V, max = +2.78 V)
in5: +1.21 V (min = +0.00 V, max = +2.78 V)
in6: +2.78 V (min = +0.00 V, max = +2.78 V) ALARM
3VSB: +1.67 V (min = +0.00 V, max = +2.78 V)
Vbat: +1.60 V
fan1: 3835 RPM (min = 10 RPM)
fan2: 3571 RPM (min = 10 RPM)
fan3: 0 RPM (min = 0 RPM)
temp1: +48.0°C (low = +0.0°C, high = +70.0°C) sensor = Intel PECI
temp2: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp3: +43.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
intrusion0: ALARM

coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +46.0°C (high = +84.0°C, crit = +94.0°C)
Core 0: +38.0°C (high = +84.0°C, crit = +94.0°C)
Core 1: +42.0°C (high = +84.0°C, crit = +94.0°C)
Core 2: +39.0°C (high = +84.0°C, crit = +94.0°C)
Core 3: +41.0°C (high = +84.0°C, crit = +94.0°C)
Core 4: +40.0°C (high = +84.0°C, crit = +94.0°C)
Core 5: +38.0°C (high = +84.0°C, crit = +94.0°C)

it8620-isa-0a40
Adapter: ISA adapter
in0: +1.08 V (min = +0.00 V, max = +3.06 V)
in1: +2.51 V (min = +0.00 V, max = +3.06 V)
in2: +2.02 V (min = +0.00 V, max = +3.06 V)
in3: +2.03 V (min = +0.00 V, max = +3.06 V)
in4: +1.06 V (min = +0.00 V, max = +3.06 V)
in5: +1.06 V (min = +0.00 V, max = +3.06 V)
in6: +2.50 V (min = +0.00 V, max = +3.06 V)
3VSB: +3.38 V (min = +0.00 V, max = +6.12 V)
Vbat: +3.02 V
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
temp1: +34.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp2: +42.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp3: +127.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp4: +51.0°C
temp5: +46.0°C
temp6: +46.0°C
intrusion0: ALARM
- Sep 03 2018

So it all works, but the graphs for memory, swap & harddrives are about 300px lower than the box they "should" be in...I would guess the remove of the CPU graphs changed the spacing? - Sep 03 2018

Yes--I'm shaking my head...it is the CPU area. I'm now running an X99 board with a i7-5820K. As soon as I removed the CPU graphs & speed the conky works.... - Sep 03 2018

OK-dug into it a bit & get this from terminal output:

conky: llua_do_call: function conky_check_network_interfaces execution failed: /home/dean/.conky/lines/lines.lua:1067: attempt to perform arithmetic on local 's' (a nil value)

So, it looks like the same problem still..... - Sep 03 2018

Hmmmm--I'm still seeing the main execution error....I've got work to do, so I'll revisit this in a couple of hours.....As for bonding--I use SystemD to create the bond. After figuring out how to do it--it works very well.. - Sep 03 2018

I guess that I should have noted that I got the output after removing the "-q" after the startline--wanted to see terminal output. It just prints that line for as long as the terminal is open. - Sep 03 2018

Hmmm--Not getting the same error, but I get this:

conky: llua_do_call: function conky_main execution failed: attempt to call a nil value
- Sep 03 2018

Is there a way to just bypass the config testing & define the interface straight? - Sep 02 2018

ip addr output (scrubbed the addresses):

dean@debian:~$ ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp7s0: mtu 1500 qdisc pfifo_fast master bond0 state UP group default qlen 1000
link/ether 00:e0:4c:68:0f:bf brd ff:ff:ff:ff:ff:ff
3: eno1: mtu 1500 qdisc pfifo_fast master bond0 state UP group default qlen 1000
link/ether 42:be:e4:df:ca:38 brd ff:ff:ff:ff:ff:ff
4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 42:be:e4:df:ca:38 brd ff:ff:ff:ff:ff:ff
- Sep 02 2018

Well---maybe my bonded interface is the problem? Using 2 NIC cards as bond0. did the above mod & here is the output:

conky: llua_do_call: function conky_check_network_interfaces execution failed: /home/dean/.conky/lines/lines.lua:1062: attempt to perform arithmetic on local 's' (a nil value)
grep: invalid argument ‘0’ for ‘--directories’
Valid arguments are:
- ‘read’
- ‘recurse’
- ‘skip’
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
- Sep 02 2018

Yes--that is correct--but even after installing it, can't be used without root. - Sep 02 2018

Hi Moob...
Just tried to use your new version...Have not used the old version in quite a while & it looks like Debian Testing will not work with ifconfig anymore....Since my config is purely a desktop--I don't need to do a lot with interfaces--could you head me in the right direction to just hardwire the network interface? - Sep 01 2018

+Nice - Aug 25 2018

I don't use Conky Manager---This is a MANUAL install. It requires you to look at the scripts & your user folder & make the proper adjustments to make it work. - Jun 24 2018

+ - Jun 15 2018