Comment 2 for bug 1525290

Hi,
this is fairly old and I'm currently cleaning up old bugs to make sure they are either actionable or closed to get a better view on the active issues to solve.

For this bug in particular it lacks the details to reproduce the issue, more detail like a stacktrace and so on. If you'd have steps to repdoduce that would help a lot to check which upstream change fixed that and would need to be backported.

Without that this is hard to action upon, therefore marking this invalid for now to reflect that a fix is waiting on more detail.