Bug 129381 - Crash when using "edit > cut" on a picture in impress on iOS using app version 4.2
Summary: Crash when using "edit > cut" on a picture in impress on iOS using app versio...
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: iOS Editor (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other iOS
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-13 17:47 UTC by Nicolas Christener
Modified: 2020-01-20 19:09 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Christener 2019-12-13 17:47:54 UTC
Description:
When a picture is inserted into a slide on iOS using the app version 4.2 and then the user taps on "edit > cut" the app crashes.

Test picture I used is the otter taken from here:
https://de.wikipedia.org/wiki/Otter#/media/Datei:Loutre_des_pyrenees_baronnies_2004.jpg

Long press in the iOS browser -> copy, then paste into an impress slide.

Steps to Reproduce:
1. Copy/paste a picture into a slide in impress using the iOS app (version 4.2.)
2. Select the pasted picture so it has the focus
3. Tap on menu "edit > cut"

Actual Results:
The app crashes.

Expected Results:
The app should not crash.


Reproducible: Always


User Profile Reset: No



Additional Info:
This does not happen in writer and calc (on iOS).

I currently run iOS 13.3.x
Comment 1 Xisco Faulí 2019-12-16 18:37:14 UTC
Moving to NEW
Comment 2 How can I remove my account? 2019-12-18 09:43:41 UTC
At the moment I am not even able to paste any image into a presentation...
Comment 3 How can I remove my account? 2020-01-01 10:35:58 UTC
Nicolas, could you please attach a .odp (or .ppt or .pptx) document with an image where this crash can be reproduced, thanks. I can't reproduce it in a current build.
Comment 4 Nicolas Christener 2020-01-14 15:11:28 UTC
Tested in 4.2 (30). This issue is fixed and can be closed.

(Just for the records: with e.g. 4.2 (23) one can reproduce the issue).

Thanks a lot to the Collabora team and especially to Tor for taking care of this.
Comment 5 QA Administrators 2020-01-15 03:38:20 UTC Comment hidden (obsolete)
Comment 6 Xisco Faulí 2020-01-20 19:09:15 UTC
(In reply to Nicolas Christener from comment #4)
> Tested in 4.2 (30). This issue is fixed and can be closed.
> 
> (Just for the records: with e.g. 4.2 (23) one can reproduce the issue).
> 
> Thanks a lot to the Collabora team and especially to Tor for taking care of
> this.

Closing as RESOLVED FIXED then