The sample file is attached to this report. Steps to reproduce the problem:
1. open attached file and besides create blank writer file
2. in attached file select text starting from cross-references to Table 2 and Illustration 2 to the end of document
3. press Ctrl+C to copy text block
4. move to blank file and press Ctrl+V
You will see instead of cross-reference to Table 2 and Illustration 2 'Error: Reference source not found' message. If you will select the whole content and copy / paste it to blank, cross-references will survive in this case.
Created attachment 77991
Example showing broken cross-references
The problem appeared after application of solution for somehow disturbed cross-reference dialogue (https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 50139, https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 50144, https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 45049, https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 46714, https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 47042). When creating text document with several captions, it happens from time to time, that cross references are disappearnig, showing instead 'Error: Reference source not found' message; for instance, when new caption is inserted somewhere in the middle of the document, the cross-references to other captions following to the inserted caption disappearor are misplaced. The same happens if part of the document containing captions and cross-references is copied to other document or other part of the same document.
The sample file is attached to this report. Steps to reproduce the problem:
1. open attached file and besides create blank writer file
2. in attached file select text starting from cross-references to Table 2 and Illustration 2 to the end of document
3. press Ctrl+C to copy text block
4. move to blank file and press Ctrl+V
You will see instead of cross-reference to Table 2 and Illustration 2 'Error: Reference source not found' message. If you will select the whole content and copy / paste it to blank, cross-references will survive in this case.
I guess it is quite annoing bug.