Comment 11 for bug 1091708

I understand bootchart is being called with the following commandline:

bootchart --quiet --format=$FORMAT --crop-after=gnome-panel,mutter,unity-panel-service --annotate=ureadahead,mountall,hostname,hwclock --annotate=Xorg --annotate=gnome-session --annotate-file=$DIR/times --output=$DIR/bootchart.$FORMAT $DIR/bootchart.tgz

For the failed bootchart in question, running with --verbose instead of --quiet produces the following output:

parsing 'bootchart.tgz'
parsing 'header'
  0.0 seconds
parsing 'proc_stat.log'
  0.1 seconds
parsing 'proc_diskstats.log'
  0.34 seconds
parsing 'proc_ps.log'
warning: no parent for pid '2' with ppid '0'
1751 samples, avg. sample length 4.000000
process list size: 719
  11.07 seconds
no selected proc in list
merged 0 logger processes
pruned 252 process, 0 exploders, 128 threads, and 18 runs
False
bootchart written to 'bootchart.png'

Crucial is the line, 'no selected proc in list'. This means that as far as bootchart is concerned, the data collection ended *before* the system startup actually completed, where system startup is defined as "one of gnome-panel, mutter, or unity-panel-service has started".

So we need to figure out why this definition of "startup" is failing here. It could be a timing thing, or it could be that the relevant process names have changed.