It's not fixed. The error is the same. FWIW, it also happens on my User: page, although not necessarily other User: pages.
As far as I can see, this should now be resolved.