conky segmentation fault in Intrepid

Looks similar to bug 279493.
What messages you get if you launch conky from a terminal?
Could you perhaps obtain a backtrace (https://wiki.ubuntu.com/DebuggingProgramCrash)?

Also, can you try to remove this line from .conkyrc and see what happens:

${execi 30 tail -n3 /var/log/messages | fold -w50}

I just removed that line, and it seems like it has done the trick. Conky no longer crashes on my startup of Openbox.

Why would displaying the log make it crash? Is there anyway to fix my script so that the log can be displayed?

Also, thanks for the advice.

>Why would displaying the log make it crash?

No idea yet, if you could attach to this bug report your /var/log/messages file this could give me some clues.
If you have edited your conky.conf file, or created a new one, attaching these should also be helpful.
Can you also tell me which command line options you use when calling conky?

Thanks for any help you can give.

I'm uploading a new version that should solve this problem, please test and reopen this bug if it still fails. Note that you may have to add a text_buffer_size greater that the default of 256 if you want to see all your log messages (640 should do).

This bug was fixed in the package conky - 1.6.1-0ubuntu3

---------------
conky (1.6.1-0ubuntu3) intrepid; urgency=low

  * debian/patches:
    - fix_exec_buffer_size.patch (LP: #279493, LP: #279791):
      fix SIGSEGV due to wrong buffer size being used in all exec* calls.

 -- Cesare Tirabassi <email address hidden> Fri, 10 Oct 2008 22:40:09 +0200