Yes, I have now very grudgingly upgraded to 19.10 and the problem seems to be resolved.
This problem was new at some point in 19.04 (ie did not exist at first with 19.04) and I do not think pressuring eople to upgrade (so soon after a release) is a good solution.
On the other hand, strangely, no one else has reported the bug.
Yes, I have now very grudgingly upgraded to 19.10 and the problem seems to be resolved.
This problem was new at some point in 19.04 (ie did not exist at first with 19.04) and I do not think pressuring eople to upgrade (so soon after a release) is a good solution.
On the other hand, strangely, no one else has reported the bug.
Thanks, Olivier!