Comment 40 for bug 1576799

Hi,
I come by trying to clear or revive bugs that are dormant for too long.
Especially since the originally reported release was Xenial which is now in extended security maintenance it might be worth to re-visit the validity of the issue going forward.

OTOH all the time in the last 4 years nobody else chimed in here, so maybe (hopefully) this isn't a problem for anyone anymore - at least not in the newer releases? Lowering severity based on this for now.

It seems the many tasks of Andreas kept him too busy for making progress/updates on this :-/
We do so much more tests in the new versions, maybe we just know that it works at least with the newer versions already?
@Andreas - is this worth to be revisited?