I only reported this because the proprietary works in this case.

If this is an application bug, then I guess this can be closed as such. There
is no reason why Mesa should fall back to the compatibility profile when more
than one context is used I guess?