Comment 8 for bug 1003727

Great, glad to hear that conky 1.9 fixes the problem. I'll leave this bug as "Confirmed" so that precise users can find out about this bug, and avoid filing duplicates.

I'm unsure of whether this bug is enough to qualify for a SRU, rather than just a backport. This bug will reliably cause a segfault in conky 1.8.1-6 as long as 2 conditions hold:
1) execi/execpi is used in the user's conkyrc file
2) execi/execpi's interval is less than current system uptime (which is why conky crashes at startup)

I've linked the upstream bug report (http://sourceforge.net/support/tracker.php?aid=3432429); the fix for this, aside from upgrading to conky 1.9.0-2 (which is out of the scope of a SRU), should be to apply the following patch (already committed to upstream git repository):

http://git.omp.am/?p=conky.git;a=commitdiff;h=742dbbffaa38627195ca69e41d3d30def1ff9da5

Either way, I don't have time to persue a SRU at the moment anyways. For anyone who thinks this bug justifies a SRU, the process is outlined here: https://wiki.ubuntu.com/StableReleaseUpdates

(As an aside, n1c0la5, the binary "conky" package is only a transitional package (upgrading it won't do anything); you need to install one of conky-cli, conky-std, or conky-all.)