Verified. Doing plot->GetHistogram()->Sumw2(false); solved the problem.
I agree it does not really make sense in this context, but for a framework that handles both histograms and graphs, setting the default flag is pretty “natural”. Putting a protection is a good idea, but one needs to make sure it doesn’t break other histograms…
One could also make it clear in the documentation. I for one certainly did not imagine Sumw2 to be the culprit.
The fix should be at the graph painting time for the histogram used to draw the graph axis. I cannot imagine any case where one would like to have this empty histogram painted with errors… Therefore this histogram should be created without Sumw2 . Once fixed, there will be no need to update the documentation as it will behave as expected.