Comment 24 for bug 1899485

This was a in-app upgrade from prev. version 52.1.1 where the issue already exists.
Fresh install might be a little bit tricky from timing perspective but i'll check.

(In reply to :Dossy Shiobara from comment #18)
> coxmatthew, AllUses:
>
> How did you install the version of TB you're on? In-app upgrade from
> previous version of TB, or fresh complete install via download of installer
> package? Or, some other method (built from source, etc.)?
>
> I'm wondering if the problem is a bad MAR file which got applied during a
> partial update upgrade within TB. If possible, can you do a full install
> using a freshly downloaded installer package, and see if you can still
> reproduce the bug?