Comment 14 for bug 1615614

If this is with boost 1.61, either the problem is still present in boost or, if the local files were messed up somehow, the exception would legitimately be raised because the locale definition is broken.

Comment #9 seems to indicate that the problem was fixed after regenerating the locale. In that case, the exception is perfectly legitimate, and there is no bug at all. If the locale info is broken, we can't parse essential configuration files in scopes-api, which prevents the runtime from being started. In that case, all scopes are inaccessible, period.

If the problem indeed went away after regenerating the local info, there is no bug here. In that case, can you close as invalid please?