Comment 4 for bug 1641339

There has been no activity on this bug in nearly a year. We're a week away from releasing 17.10, which will put us well on the way to being in the dev cycle for the next LTS. I have grave concerns about a fix making it into the repo in time having witnessed deadlines come and go on previous releases. I really don't want to have to keep local patches around post-upgrade next year.

The upstream bug does have a patch associated with it. Is there anything else I need to do to shepherd this along?