Comment 29 for bug 1723857

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

All, you're not helping the situation by unmarking this as a duplicate.

The first report was bug 1721315. The correct developer was assigned to bug 1721315. And the correct upstream bug link was assigned to bug 1721315. And bug 1721315 is the only one correctly formatted already in such a way that a fix can be backported to 17.10 (SRU).

I've duplicated the upstream link in here now, but I think this bug should be closed as a duplicate of bug 1721315.