Package: conky Version: 1.5.1-1 Tag: Important
When I type, `conky' I get a segfault immediately. I rebuilt from source. GDB gives a backtrace thus: (gdb) bt #0 0x000000000040cfdb in extract_variable_text_internal ( const_p=<value optimized out>) at conky.c:2626 #1 0x0000000000411ce7 in extract_variable_text ( p=0x6440d0 "$nodename - $sysname $kernel on $machine\n$stippled_hr\n${color lightgrey}Uptime:$color $uptime ${color lightgrey}- Load:$color $loadavg Freq: $freq MHz $acpitemp C\n${color lightgrey}CPU Usage:${color #"...) at conky.c:4036 #2 0x0000000000418981 in main (argc=1, argv=0x7fffb3ab0548) at conky.c:8737 Here's a minimal .conkyrc that triggers the bug: --- TEXT $diskiograph --- I'm running amd64 with a 2.6.26-rc6 kernel if that makes a difference, otherwise straight Debian unstable. It looks like the latest version of conky insists on an argument to diskiograph and segfaults if one isn't given. Changing the .conkyrc to ${diskiograph /dev/hda} works; is htere any more a way to get aggregat disk I/O on a graph? -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au http://www.ertos.nicta.com.au ERTOS within National ICT Australia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]