Post your .conkyrc files w/ screenshots

[VinDSL]

New error[...]

Looks like a hardware error to me, BOOMM.

I would check the video card, the display drivers, your xorg config, et cetera.

[BoredOutOfMyMind]

Need little help witn this conky please.I make new conkyrc and make draw_bg.lua and got this. How to fix?

You need to download and install the fonts. dafonts.com may have most of them.

####
## Installed fonts (required).
#
# ConkyWeather (Stanko Metodiev)
# ConkyWindNESW (Stanko Metodiev)
# Cut Outs for 3D FX (Fonts & Things)
# Liberation Mono (Ascender Corp)
# Liberation Sans (Ascender Corp)
# Moon Phases (Curtis Clark)
# OpenLogos (Icoma)
# PizzaDude Bullets (Jakob Fischer)
# Radio Space (Iconian Fonts)
# StyleBats (Vinterstille)
# Ubuntu (Canonical Ltd)
# Ubuntu Title Bold (Paulo Silva)
# Weather (Jonathan Macagba)
# WenQuanYi Micro Hei (Google Corp)

[BoredOutOfMyMind]

Looks like a hardware error to me, BOOMM.

I would check the video card, the display drivers, your xorg config, et cetera.

The wunnerful NVIDIA?

Not a slam at you VinDSL, appreciate your work.

Thanks for the reply.

[VinDSL]

Need little help witn this conky please.I make new conkyrc and make draw_bg.lua and got this. How to fix?

The large '2' on the calendar indicates that you are (either) missing the "Cut Outs for 3D FX" font, or the font hasn't been cached yet.

Personally, after I install a font, I reboot, just to make sure everything is kosher. You can cache fonts on-the-fly from CLI, but that's been a hit or miss experience for me.

The blank data points indicate that your Weather.com XOAP feed isn't setup correctly...

[urosg3]

The large '2' on the calendar indicates that you are (either) missing the "Cut Outs for 3D FX" font, or the font hasn't been cached yet.

Personally, after I install a font, I reboot, just to make sure everything is kosher. You can cache fonts on-the-fly from CLI, but that's been a hit or miss experience for me.

The blank data points indicate that your Weather.com XOAP feed isn't setup correctly...

Fixed font from CLI, no more #2, and weather fixed too.Still one error:

Conky: llua_do_call: function conky_draw_bg execution failed: attempt to call a nil value

[VinDSL]

BOOMM:~$ conky .conkyrc
Conky: desktop window (12000b5) is subwindow of root window (1ad)
Conky: window type - override
Conky: drawing to created window (0x4600001)
Conky: drawing to double buffer
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 718 requests (702 known processed) with 0 events remaining.

The wunnerful NVIDIA?

Not a slam at you VinDSL, appreciate your work.

Thanks for the reply.

Well...

Error messages are indicative!

Whenever I see 'IO' in an error message, I start thinking 'hardware'.

'X server' indicates a display problem.

'XIO' means you have an 'X server' 'IO' problem.

':0.0' indicates your primary display monitor.

Q: What supplies the 'X server' with 'IO'?

A: Graphic card, display drivers, xorg config.

That's where I would start.

Maybe it's the calendar code, but I *think* you're looking at the wrong end of the horse...

[VinDSL]

Still one error:

Conky: llua_do_call: function conky_draw_bg execution failed: attempt to call a nil value

Did you try a reboot?

Also, kill the conkyForecast cache in /tmp. Then, killall conky & restart.

You can do all of this from CLI, but... like I said... it's hit or miss.

Personally, I'd kill the conkyForecast cache file and reboot.

Gotta run (for a few hours)! BBL

[BoredOutOfMyMind]

Maybe it's the calendar code, but I *think* you're looking at the wrong end of the horse...

I *thought* I had clarified I *know* it is not your work.

This will be a bugger of a solution. So far today I have spent 3 1/2 hrs on solving Conky.

It was running great and I had copied some things from my .conkyrc to the new version and hit the wrong button reloading the old file and overwriting 1 hr of "fixing". Then the errors.....

Ain't it grand! No time now have to head out.

[mrpeachy]

I don't think there should have to reboot to fix any conky/lua problems

for lua errors, read the console... it will tell you on which line the error occurs, then look at the script and see whats on that line
(for those pesky nil value errors the line number will be right at the very start where conky was started)

if conky is playing up then killall conky in a terminal and a restart should be all that is required (although, for some reason, sometimes this doesn't work and I need to run the system monitor and kill conky from there... I'm using LMDE, never had this problem with Ubuntu)

if you really need to, ctr+alt+backspace to restart X

after caching fonts (sudo fc-cache -f -v) in the console you will also have to kill and restart conky before it starts using the new fonts

[stanca]

)