Franz Sirl wrote on Tue, 24 Jul 2018 22:00 +0200: > It turns out this is probably issue #4700 which for some reason was > never approved for the 1.9 branch, even though it was already nominated > last October. So the version that matters here is the server version. > After I upgraded the server from 1.9.5 to 1.10.2 the problem is gone > (regardless of the client version) and all is well now.
Thanks for following up with this information!
