Comment 56 for bug 1422143

Revision history for this message
Stephan Springer (geryon) wrote :

Martin Pitt committed some fix in October 2015, but apparently that did not solve this bug, or only partly.

What's the correct way to handle this? Reopen this bug or open a new one referring to this one?

This still happens for me, too (Ubuntu 16.04), and the workaround from #50 fixes it.