conky on old macpro/Stretch/legacy nvidia

brontosaurusrex · 2017-06-07 20:17:45

Will:

- show small black dot or with various window_type parameters a slightly bigger dot.
- be unkillable (killall conky is not working...) edit: pkill -9 -f conky < did the trick.

Any hints?

inxi -G
Graphics:  Card: NVIDIA G96 [GeForce 9500 GT]
           Display Server: X.Org 1.19.2 driver: nvidia
           Resolution: 1920x1080@60.00hz, 1920x1200@59.95hz
           GLX Renderer: GeForce GT 120/PCIe/SSE2
           GLX Version: 3.3.0 NVIDIA 340.102

Last edited by brontosaurusrex (2017-06-07 20:28:49)

Sector11 · 2017-06-07 20:46:23

What command "shows a small black dot" ??

Are you trying to get nvidia info into conky?

if 'yes', please show: inxi -s

Did you install "lm-sensors" ? (answer yes to everything)

if 'yes' please show the results of: sensors

For nvidia graphics cards these are available in conky:
Nvidia:
${nvidia threshold} - The thresholdtemperature at which the gpu slows down
${nvidia temp} - Gives the gpu current temperature
${nvidia ambient} - Gives current air temperature near GPU case
${nvidia gpufreq} - Gives the current gpu frequency
${nvidia memfreq} - Gives the current mem frequency
${nvidia imagequality} - Which imagequality should be chosen by OpenGL applications

My board doesn't get the ambient one though.

Sector11 · 2017-06-07 20:55:04

If starting the 'default' conky at ~/.conkyrc with:

conky

this will work:

pkill -xf "conky" &

in another location say:

/media/5/Conky/test.conky

and you start it like this:

conky -c /media/5/Conky/test.conky

this will kill just that one conky:

pkill -xf "conky -c /media/5/Conky/test.conky" &

leaving any others you have running - running.

ohnonot · 2017-06-07 20:55:54

i'm seeing the black dot when conky is started, but has to wait until some script finishes before it can display anything.
that's all i can say.
you don't use a desktop manager?

obviously: try conky without daemonizing (background no) from a terminal, see if somethinginteresting pops up.

brontosaurusrex · 2017-06-07 21:40:36

Sector11 wrote:

What command "shows a small black dot" ??

Any.
The rest of the answers is no.

@ohnonot: nothing interesting pops up, perhaps that xinerama thing...

conky -D
DEBUG(0) [/build/conky-H8e3VB/conky-1.10.6/src/conky.cc:2698]: reading contents from config file '/home/b/.conkyrc'
conky: Syntax error (/home/b/.conkyrc:2: '=' expected near 'yes') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
DEBUG(0) [/build/conky-H8e3VB/conky-1.10.6/src/x11.cc:497]: Fixed xinerama area to: 0 0 1920 1200
DEBUG(0) [/build/conky-H8e3VB/conky-1.10.6/src/x11.cc:497]: Fixed xinerama area to: 0 0 1920 1200
conky: desktop window (274) is root window
conky: window type - normal
conky: drawing to created window (0x1800001)

I haven't bothered with config conversion yet, but any config will only display black dot.

p.s. Latest greatest conky compile from git master is behaving the same.

Screenshot

Last edited by brontosaurusrex (2017-06-07 21:48:11)

Sector11 · 2017-06-07 21:52:07

I'd try converting at least one conky from the v1.9 format to the v1.10 format and try that.

PackRat · 2017-06-07 22:50:28

^ This

I've gotten syntax errors like this:

conky: Syntax error (/home/b/.conkyrc:2: '=' expected near 'yes') while reading config file.

and no conky dispaly - even though it appears to finish reading the config file in a terminal. Once I converted the older config files, they worked fine.

I haven't bothered with config conversion yet, but any config will only display black dot.

Do they all show a syntax error?

Also, is that a tint2 panel at the top and on the right? Try placing a conky at the lower right; maybe you have some sort of window placement conflict. I've seen that before when the conky window and tint2 panel overlap.

brontosaurusrex · 2017-06-07 23:07:07

It is not a config problem, this

conky -C > testcon
conky -c testcon

will give me same silly dot. (Also my config is working fine on another machine with same OS).

Last edited by brontosaurusrex (2017-06-07 23:07:56)

Sector11 · 2017-06-07 23:14:51

PackRat wrote:

Also, is that a tint2 panel at the top and on the right? Try placing a conky at the lower right; maybe you have some sort of window placement conflict. I've seen that before when the conky window and tint2 panel overlap.

That's the reason I stopped using tint2. Even if I set it to x pixels or 50% width it would interfere with a conky in the corner.

The new "lua" conky (v1.10) has one annoying feature that I do not like, well more than one, but, the conky "window" doesn't allow one to right|centre|left click to get at menus.

Head_on_a_Stick · 2017-06-08 06:50:39

brontosaurusrex wrote:

pkill -9 -f conky

Did you try plain old `pkill conky` first?

SIGKILL should *never* need to be issued.

http://porkmail.org/era/unix/award.html#uuk9letter

tl;dr: http://turnoff.us/geek/dont-sigkill/

Can you reproduce this with the nouveau drivers? 8o

brontosaurusrex · 2017-06-08 08:29:19

Head_on_a_Stick wrote:

Can you reproduce this with the nouveau drivers? 8o

I'll try that next.

unklar · 2017-06-08 14:20:29

I've always said: conky 1.10 is sensitive.
It expected behind '=' a 'false' or 'true' and no 'yes'

To the "black dot" or "quadrangle".
My experience with both syntax versions says that it is always a problem of interplay between the display manager and the variables

own_window yes
own_window_type normal
own_window_transparent yes
own_window_hints undecorated,below,skip_taskbar,skip_pager,sticky
own_window_colour 000000
own_window_class Conky
own_window_title Bunsen Labs Default Conky
#own_window_argb_visual yes
#own_window_argb_value 50

is.
The crux of the story is, the user has to log off and change the settings again and again, or restart the computer for the changes to be visible in the conky.

brontosaurusrex · 2017-06-08 20:30:40

Right, now I have this

inxi -G
Graphics:  Card: NVIDIA G96 [GeForce 9500 GT]
           Display Server: X.Org 1.19.2 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.00hz, 1920x1200@59.95hz
           GLX Renderer: Gallium 0.4 on NV96 GLX Version: 3.0 Mesa 13.0.6

Which seems to fix some problems with consoles, so its a keeper. It does seem to negatively effect my slither.io chrome session thought. Oh and conky is still a black-dot

Any possible dpi settings someplace? https://bbs.archlinux.org/viewtopic.php?id=173200

Last edited by brontosaurusrex (2017-06-09 09:16:32)

#1 2017-06-07 20:17:45

conky on old macpro/Stretch/legacy nvidia

#2 2017-06-07 20:46:23

Re: conky on old macpro/Stretch/legacy nvidia

#3 2017-06-07 20:55:04

Re: conky on old macpro/Stretch/legacy nvidia

#4 2017-06-07 20:55:54

Re: conky on old macpro/Stretch/legacy nvidia

#5 2017-06-07 21:40:36

Re: conky on old macpro/Stretch/legacy nvidia

#6 2017-06-07 21:52:07

Re: conky on old macpro/Stretch/legacy nvidia

#7 2017-06-07 22:50:28

Re: conky on old macpro/Stretch/legacy nvidia

#8 2017-06-07 23:07:07

Re: conky on old macpro/Stretch/legacy nvidia

#9 2017-06-07 23:14:51

Re: conky on old macpro/Stretch/legacy nvidia

#10 2017-06-08 06:50:39

Re: conky on old macpro/Stretch/legacy nvidia

#11 2017-06-08 08:29:19

Re: conky on old macpro/Stretch/legacy nvidia

#12 2017-06-08 14:20:29

Re: conky on old macpro/Stretch/legacy nvidia

#13 2017-06-08 20:30:40

Re: conky on old macpro/Stretch/legacy nvidia

Board footer