Comment 19 for bug 1718931

@Mathieu, the issue described here was fixed, it's probably best to open a new bug (& upstream as well if possible) with a full journal log and description of your issue