Post your .conkyrc files w/ screenshots

[Friqenstein]

Try this instead:

${if_match ${fs_free /media/raid1} < 26}${color green}${fs_bar /raid1}${else}${if_match ${fs_free /media/raid1} < 51}${color yellow}${fs_bar /raid1}${else}${if_match ${fs_free /media/raid1} < 76}${color orange}${fs_bar /raid1}${else}${color red}${fs_bar /media/raid1}${else}N/C${endif}${endif}${endif}

Open that partition in a file manager and see if that is where it's mounted. You need to put the full mount point in there.

Also... putting slashes in after the else will always result in a slash in these cases. It's better to just have a straight nested if statement, with a final "Else" with "Not Connected" in it.

Well, I know the path is correct because I'm constantly writing data to that partition. So that cannot be the issue.
I've tried the edited version and it still complains with the same errors... no line numbers though which would make things tremendously easier to troubleshoot.

Here is the output error message:

Conky: unknown variable if_match
Conky: $else: no matching $if_*
Conky: unknown variable if_match
Conky: $else: no matching $if_*
Conky: unknown variable if_match
Conky: $else: no matching $if_*
Conky: $else: no matching $if_*
Conky: $endif: no matching $if_*
Conky: $endif: no matching $if_*
Conky: $endif: no matching $if_*
Conky: desktop window (80006c) is subwindow of root window (44)
Conky: window type - override
Conky: drawing to created window (0x1900001)
Conky: drawing to double buffer
Conky: too many special things in text

[RichardCain]

I don't know either. For now though, try this in place of that particular execi call:

${execpi 600 sed -n '2p' $HOME/.conky/Accuweather_Conky_Int_ConkyWeatherFont/curr_cond | cut -c 1}

For now anyways. Until you can have Teo look into it further.

Thanks 42dorian. It certainly looks better with just 1 icon, but I can't be sure it's the right one - earlier today it would have been showing snow with a minimum temperature of 23C!

I'll have to get registered on the Arch forum & pick Teo's brains.

[arclance]

Try this instead:

${if_match ${fs_free /media/raid1} < 26}${color green}${fs_bar /raid1}${else}${if_match ${fs_free /media/raid1} < 51}${color yellow}${fs_bar /raid1}${else}${if_match ${fs_free /media/raid1} < 76}${color orange}${fs_bar /raid1}${else}${color red}${fs_bar /media/raid1}${else}N/C${endif}${endif}${endif}

Open that partition in a file manager and see if that is where it's mounted. You need to put the full mount point in there.

Well, I know the path is correct because I'm constantly writing data to that partition. So that cannot be the issue.
I've tried the edited version and it still complains with the same errors... no line numbers though which would make things tremendously easier to troubleshoot.

Here is the output error message:

Conky: unknown variable if_match
Conky: $else: no matching $if_*
Conky: unknown variable if_match
Conky: $else: no matching $if_*
Conky: unknown variable if_match
Conky: $else: no matching $if_*
Conky: $else: no matching $if_*
Conky: $endif: no matching $if_*
Conky: $endif: no matching $if_*
Conky: $endif: no matching $if_*
Conky: desktop window (80006c) is subwindow of root window (44)
Conky: window type - override
Conky: drawing to created window (0x1900001)
Conky: drawing to double buffer
Conky: too many special things in text

You have two ${else} matched with the final ${if_match } that may be causing the "no matching X" error messages you are getting.

[Friqenstein]

You have two ${else} matched with the final ${if_match } that may be causing the "no matching X" error messages you are getting.

Well, I've tried multiple renditions of the code and cannot get it to function properly.

Even if I remove all but the first ${if_match} statement, it still complains that if_match is an invalid variable.
Are you sure I don't need some other extra bit of conky or scripting to get the if_match/else statements to work?

[Friqenstein]

Well, I seem to have found the 'problem'...
In this post: http://ubuntuforums.org/showthread.php?t=1173838

It states the following: "It seems if_match has been added in conky v. 1.6.2...."

So it would appear that I am up a creek w/out a paddle. I'm using v1.6.1.
Now I will have to search for some alternative way to do this with the 1.1.6 version.

What I don't get is... the CPU graph allows you to specify 2 different colors for a spanning effect when the CPU state changes. Why doesn't conky automatically do this for all types of variables?

[Sector11]

So it would appear that I am up a creek w/out a paddle.

No sir, your paddle in this case is called: colorize.sh

Crinos512 wrote that bash script to do exactly what you want before conky had ${if_match}. It can be used for "anything" that outputs a NUMBER.

Let us know how it works for you.

IE:

  13:20:11 ~
         $ nvidia-settings -q gpucoretemp

  Attribute 'GPUCoreTemp' (sector11:0.0): 40.
    'GPUCoreTemp' is an integer attribute.
    'GPUCoreTemp' is a read-only attribute.
    'GPUCoreTemp' can use the following target types: X Screen, GPU.


  13:20:14 ~
         $ nvidia-settings -q gpucoretemp | grep Attribute | cut --characters 41-42
: 

  13:22:11 ~
         $ nvidia-settings -q gpucoretemp | grep Attribute | cut --characters 41-45
: 40.

  13:22:27 ~
         $ nvidia-settings -q gpucoretemp | grep Attribute | cut --characters 44-45
0.

  13:22:34 ~
         $ nvidia-settings -q gpucoretemp | grep Attribute | cut --characters 43-44
40

  13:22:49 ~
         $

${execpi 8 sh -c "DISPLAY=:0.0 nvidia-settings -q gpucoretemp | grep Attribute | cut --characters 43-44" | xargs ~/Conky/scripts/<span style="color: #800000;">ColorTempGPU.sh</span>}°

[Friqenstein]

Hi Sector,

Mind reader!
I was actually already looking at making a version of the colorize.sh script. Just haven't decided how exactly I want to cut it up yet.

But thanks for the reply!

[Sector11]

Hi Sector,

Mind reader!
I was actually already looking at making a version of the colorize.sh script. Just haven't decided how exactly I want to cut it up yet.

But thanks for the reply!

Why not try an updated conky? Maybe v1.8.0 will work with Ubuntu 9.10
You flyin an i386 or 64 bit version?

I have:
conky-all_1.8.0-1+squeeze1_i386.deb
conky-all_1.8.0-1_amd64.deb
or
conky_1.7.1.1-1_amd64.deb

     $ conky -v
Conky 1.7.1.1 compiled Mon Jul 6 16:16:06 ART 2009 for Linux 2.6.27-14-generic (x86_64)

Compiled in features:

System config file: /usr/local/etc/conky/conky.conf

X11:
* Xdamage extension
* XDBE (double buffer extension)
* Xft

Music detection:
* MPD
* MOC

General:
* math
* hddtemp
* portmon
* RSS
* Lua
* nvidia
* config-output
* Imlib2
* apcupsd
     ~$

You could try.

[Friqenstein]

Why not try an updated conky? Maybe v1.8.0 will work with Ubuntu 9.10
You flyin an i386 or 64 bit version?

I have:
conky-all_1.8.0-1+squeeze1_i386.deb
conky-all_1.8.0-1_amd64.deb
or
conky_1.7.1.1-1_amd64.deb

     $ conky -v
Conky 1.7.1.1 compiled Mon Jul 6 16:16:06 ART 2009 for Linux 2.6.27-14-generic (x86_64)

Compiled in features:

System config file: /usr/local/etc/conky/conky.conf

X11:
* Xdamage extension
* XDBE (double buffer extension)
* Xft

Music detection:
* MPD
* MOC

General:
* math
* hddtemp
* portmon
* RSS
* Lua
* nvidia
* config-output
* Imlib2
* apcupsd
     ~$

You could try.

Unfortunately I cannot. I'm running a specific version of Red Hat EL 5.5. And it was a hell of a task just finding conky in rpm format. I was able to find 2 different versions but only 1.6.1 would install properly due to the other version having tremendous broken dependencies.

Believe me, I'd upgrade the package if I could, but alas I cannot.
I'll just see what I can do with the script.

[42dorian]

Thanks 42dorian. It certainly looks better with just 1 icon, but I can't be sure it's the right one - earlier today it would have been showing snow with a minimum temperature of 23C!

I'll have to get registered on the Arch forum & pick Teo's brains.

Do me a favour? Hold off on that. I've been meaning to have a talk with Teo on my own. He and I have a few things to cover. There's something going on and I need to talk to him. Just, hold off jumping to Arch Forums for a little while.