Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU
You need to download and install the fonts. dafonts.com may have most of them.
Code:#### ## 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)
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...
Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU
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...
Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU
Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU
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.
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
Last edited by mrpeachy; January 2nd, 2011 at 12:08 AM.
)
Bookmarks