(In reply to bmilreu from comment #2) > Fix was pushed to 5.0, should we mark this as resolved for now? You're the reporter, if you consider it resolved, please mark it as such.