The bug is still present in 5.3 (from Ubuntu). I haven't had a chance to check upstream yet. Is any maintainer monitoring this ?
The bug is still present in 5.3 (from Ubuntu). I haven't had a chance to check upstream yet. Is any maintainer monitoring this ?