Comment 13 for bug 340515

I wouldn't have expected so—with no upstream attention and no noticeable updates—so I hadn't attempted again, but I just tried right now and it seems to be fixed. Whatever it was must've been some growing pains.