Thanks Per for bringing this issue to upstream. Is it correct that this bug will be fixed in the next upstream release? Is there something left to do for me?
Thanks Per for bringing this issue to upstream. Is it correct that this bug will be fixed in the next upstream release? Is there something left to do for me?