Linux Mint Forums

I did a little searching. It seems like hddtemp isn't going to be the right tool for that?

various articles are talking about using smartctl.

This user is doing something with an nvme tool: https://askubuntu.com/questions/1038701 ... 11#1038711

Keep us posted.

If you have 2 drives, then you would want to address the area where it has SDA and SDB(and just remove the stuff for SDC and D from the next line.. same with dual GPU). A single section of each drive has this format in the area: ${goto 140}SDA:${goto 180}${hddtemp /dev/sda} °C if your case has your ...

just for the information value... The current conky wiki is here: https://github.com/brndnmtthws/conky/wiki and as the developer mentions, the ${hwmon} option is the preferred method, as opposed to exec and using sensors and grep and cut, etc. Today I discovered{hwmon 0 temp 2} shows the actual cha...

just for the information value...

The current conky wiki is here: https://github.com/brndnmtthws/conky/wiki

and as the developer mentions, the ${hwmon} option is the preferred method, as opposed to exec and using sensors and grep and cut, etc.

if conky is autostart with no parameters it will run the default configuration: /etc/conky/conky.conf UNLESS you have a file called: ~/.conkyrc -in which case it uses that instead. If you are using conky-manager: 1. in the main window, put a checkbox beside one or more configs that you want to start...

... there is also a "conky-manager" desktop gui front-end for this. also note, there is an updated version of conky-manager that honors the newer version of conky with it's newer lua-based config files. So conky-manager2 will load/edit/save the 1.10 configs also(which the original does not). Right ...

mwshook, What is the sidebar on the right in that image?

trytip , teejee didn't provide packages for Artful or Bionic since they weren't out at the time, and he's stopped development of that program. I don't think that ppa will pull against Mint 19. However tomtomtom did take that same package and add build recipes for Artful and Bionic: https://launchpa...

Ha! Great! Very nice! It would be nice to see you get rid of the duplicate call(the same curl call in the second and third line). It's not as efficient like that, but also, what about in the instances when an activity change happens between the 2nd and 3rd call? :twisted: Maybe you can get rid of th...

Is there some kind of xml parser you can get involved with? just eliminate almost the whole line and get predictable data no problem..

Just curious here...why use ${exec sensors ... } instead of using ${hwmon} or ${platform} for cpu temp? I've always used hwmon, as that's how I first saw it, and exec seemed like something for advanced things. I would think hwmon would be a more efficient approach, although the data is potentially ...

${color1}CPU 0 ${offset 9}${color9}${cpu cpu0}% (${execi 8 sensors | grep -A 1 'temp1' | cut -c16-19 | sed '/^$/d'}°C) so in grep -A 1 gives an extra line after it finds the 'temp1' line, then cut brings the right data from the correct line, but then sed removes the rest and the extra line? Is that...

Flemur wrote: ⤴

Fri May 11, 2018 9:26 am

Code: Select all

CTMP: ${exec sensors -f | grep 'Core 0' | cut -c15-21 } ${exec sensors -f | grep 'Core 1' | cut -c15-21 }F

lol..

sensors -f. Who'da thunk it. And why not just cut the temp right out of it since it's always predictable output.

good stuff.

I would use °F for sure. :D It's just text, so you just observe the typical scheming there depending on which color or whatever. If you want a different color go to the end of the line and encapsulate it in some color markers. Or you could use the exising color and keep it inside the existing markers.

the interested line is: ${color6}Cpu Temp ${alignr}${color6}${execi 10 sensors | grep 'Core 0' | awk {'print $3'}}${color} strip the conky markup and in a terminal we can run directly: sensors | grep 'Core 0' | awk {'print $3'} But, that output isn't too useful alone to be able to make a conversion....

You did it all anyway..

Good job!

https://github.com/JPvRiel/conky-seamod/blob/master/conkyrc.lua check line 116 so that is the network section? find each eth0 reference and replace it with your wired network device name all in that first section. mine is called enp4s0 and you can find it, -click the network manager icon at lower ri...

Check your last 3 lines in the log there... DEBUG(1) [/build/conky-bbQ61s/conky-1.10.1/src/core.cc:577]: Adding $cpu for CPU 3 conky: obj->data.i 3 info.cpu_count 2 conky: attempting to use more CPUs than you have! and if you dig in the seamod_rings.lua file you see this 'JPvRiel' version is setup f...

This might be a bummer of a suggestion, but of course installing MATE 18.3 might eliminate the issue entirely.

Otherwise someone might have to go digging around and figure out how to cross-combine and mix the two systems.

You can start the Seamod config on the terminal and use the -D or -DD flags to see more debug info. for example: conky -DD -c /home/sardus/.conky/whatever/seamod/something ...and it might show you what is wrong. If you only installed the 'conky' package and not the 'conky-all' package then you will ...