i have the same messages too since the upgrade to 2.0b3