Bug 127630 - It is impossible to include a picture that was only linked previously
Summary: It is impossible to include a picture that was only linked previously
Status: RESOLVED DUPLICATE of bug 127474
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-18 21:44 UTC by Andy
Modified: 2019-09-19 00:32 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 Andy 2019-09-18 21:44:52 UTC
Description:
The function in the edit menu that manages pictures links to external file for not embedded images does not allow to embed a picture by "cutting" the link. the link seems gone until you save and close the file. When you reopen it, the link is still there...

Steps to Reproduce:
1.open a new impress file. Insert any picture in it, enabling the "link" option.
2. Save the presentation file. 
3. Now open file menu and click on the third last item, "links to external files" (or something like that, I cannot see the english menu item)
4. Apparently, the link disappears from the list, and it is gone, i.e. the image file is now embedded in the impress file. Now save and close.
5. Now reopen the file, and go check the same menu item dialog: the linked picture has reappeared in the list, as if you never deleted the link

Actual Results:
No way to delete links from the dialog and embed the images if you have first inserted them as links to external files

Expected Results:
It should be possible to embed image files previously linked to the presentation


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Andy 2019-09-18 21:47:43 UTC
This seems to be a regression: the linked image file dialog was working perfectly in LO 3.3.4
Comment 2 Regina Henschel 2019-09-19 00:32:24 UTC
That is indeed a problem. It has already been reported.

*** This bug has been marked as a duplicate of bug 127474 ***