After a succesfull emerge of Conky-1.6.2_pre01267, Starting Conky will result in a Segmentation fault. messages log shows this error: Nov 11 11:01:31 myservername conky[27113]: segfault at 7f538b6b ip b70b6330 sp bfa9b9d0 error 4 in libc-2.8.so[b7044000+13a000] Remerging back to Conky-1.6.1 and the problem is gone. Same USE flags, same default config file. Reproducible: Always Steps to Reproduce: 1.emerge Conky-1.6.2_pre01267 2.start conky 3. Actual Results: Segmentation fault Expected Results: conky should have started. conky -t 'test text' will load conky.
Created attachment 171402 [details] Conky errors in /var/log/messages
Created attachment 171404 [details] Conky strace info
Created attachment 171405 [details] emerge conky output
Please post your `emerge --info' too.
Created attachment 171521 [details] emerge --info
$Scroll seems to be the problem, it will crash with Segmentation fault. I noticed in 1.6.2_pre01267 scroll changed: 1.6.1: ${scroll length text} 1.6.2_pre01267: ${scroll length (step) text} Reproducible: Always Steps to Reproduce 1. conky -t '${scroll 20 some text}' Can anyone verify this result?
Confirmed! Conky will start after removing all scroll lines from conky.conf
Latest prerelease, do it.