Okay, So this is really related to the shared-mime-info update from 1.0.x to 1.1. Once you downgrade it or reinstall it the issue disappears and you can't reproduce this.