Created attachment 160088 [details]
Example file

Shapes, Fontwork. Appears to fine with images and and textboxes, form buttons

Gallery objects

Thank you for reporting the bug. I can confirm the bug present in

Version: 6.4.0.0.alpha1+ (x86)
Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded

No repro with
LibreOffice 3.5.7.2 
Build ID: 3215f89-f603614-ab984f2-7348103-1225a5

Telesto: how did you test with 4.4? I tried Linux 44max and 50max and indeed it seems to appear somewhere in there. However, a big chunk of commits from the latest of 44max towards the oldest and oldest of 50max towards the latest actually crash upon saving! I jumped around multiple times, but was unable to find a working commit to test against.

If it doesn't crash for you, can you bibisect it (maybe on Windows)?

I also tried with fresh profile, but it still crashed.

(In reply to Buovjaga from comment #6)
> Telesto: how did you test with 4.4? I tried Linux 44max and 50max and indeed
> it seems to appear somewhere in there. However, a big chunk of commits from
> the latest of 44max towards the oldest and oldest of 50max towards the
> latest actually crash upon saving! I jumped around multiple times, but was
> unable to find a working commit to test against.
> 
> If it doesn't crash for you, can you bibisect it (maybe on Windows)?
> 
> I also tried with fresh profile, but it still crashed.

Telesto: how did you test with 4.4? I used regular 4.4.7.2 build
 
It's already broken in
Version: 4.2.0.0.alpha1+
Build ID: fc8f44e82de4ebdd50ac5fbb9207cd1a59a927e3

Bibisected with Linux 43all to range https://git.libreoffice.org/core/+log/bec62421a45da89d2812bdff30fbbab73291cf91..f260c656da4457c5d87c161bdd43ad3023d07472

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