Created attachment 89898 [details] Printscreen after the changed layout - before there were almost straight Positions of all connectors lines change randomly (often after saving) to some automatic or random ones. This means all settings done before to the positions are lost with a practical impact, that the presentation with a diagram or any usage of connectors means a disaster during presentation time. (Create, save, close, present and all diagrams are unusable.) If the position of the connector lines is an automatic one, it should be changed as well, because of it makes a line with a big bow or other type of line very far from the connected objects even if there is no other object or line between the connected objects.
Can you please show an image of the connectors when they were correctly drawn. And please attach an example document. What type of connectors do you use?
Created attachment 89991 [details] odp with some connectors and prinscreens ilustrated the changed positions The former example is unnecessary big, but here is a very easy odp file with some connectors showing, that the connectors are not locked after manual editing, i.e. that after closing and opening again the manually edited connectors forgot all the manually edited positions and turn back to an automatic ones. --- So, that means, that it is a repeatable behaviour and that a problem is in missing block for automatic replacement of manually edited connectors. BTW accepting a user "decision" without an attempt to correct him/her, so that means the user safety of finding next time exactly how it was left is AFAIK one of the biggest advantages of LO to MSO. :-) -- If it could help you, I can send you the former odp as well, because of it shows another, even if much less important, bug - a suboptimal automatic placement of connector. Especially the curved ones.
Thanks. From your screenshots I would say, that is bug 70210. The fix is already in the LO4.2 (developer version). You can download a "daily build" and try, whether it solves your problem. Feel free to reopen the bug report, if you find it is still broken in an actual developer build. *** This bug has been marked as a duplicate of bug 70210 ***