Created attachment 163555 [details]
Example file

Created attachment 163559 [details]
ODT used the create DOCX

Created attachment 163560 [details]
DOCX Example

1. Open the attached file
2. CTRL+A
3. CTRL+C
4. CTRL+N
5. CTRL+SHIFT+V RTF -> Images missing

You can store the DOCX to ODT (and still run into the same problem). Problem doesn't exist with the source ODT

Found in
4.3.7.2

but not in
4.2.0.3

Reproduced in

Version: 7.1.0.0.alpha0+
Build ID: 0de191e1d201d691c2196cf1aef412a98affb66f
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

and

Version: 5.2.0.0.alpha0+
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.19; Render: default;

When bibisecting this with repo bibisect-44max, there's a pretty large range when pasting as RTF crashes.

Crash starts from the following commit, images are still pasted before this:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=ba9b63d8101197d3fd8612193b1ca188271dfc1a
author		Michael Stahl <mstahl@redhat.com>	2014-06-13 14:47:05 +0200
committer	Michael Stahl <mstahl@redhat.com>	2014-06-13 15:27:02 +0200

"fdo#76633: writerfilter: RTF import: do not leak the XShape of image"

Crash is fixed here, images aren't pasted anymore:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=2b9e782497cb962d9ca74a851a1389b0e29df49c
author		Michael Stahl <mstahl@redhat.com>	2014-07-16 18:47:15 +0200
committer	Michael Stahl <mstahl@redhat.com>	2014-07-18 12:42:25 +0200

"(related: fdo#79319) writerfilter: RTF import: fix crash on "fake" pict

...
(regression from ba9b63d8101197d3fd8612193b1ca188271dfc1a)"

An interesting commit in between:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=083b2b1471fff9e75f4b27a8769f95b8a0ebf5a1
author		Michael Stahl <mstahl@redhat.com>	2014-07-15 23:36:51 +0200
committer	Michael Stahl <mstahl@redhat.com>	2014-07-16 11:15:34 +0200

"fdo#80924: writerfilter: RTF import: fix shapeType PictureFrame import

...
(regression from ba9b63d8101197d3fd8612193b1ca188271dfc1a)"

Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug