Ubuntu

Comment 10 for bug 335732

After checking this on several new installations, I can confirm this bug still happens.