Bug 70996 - Other: paste of transparent png into presentation
Summary: Other: paste of transparent png into presentation
Status: RESOLVED DUPLICATE of bug 33114
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.1.2.3 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-29 12:48 UTC by Jozef Mlich
Modified: 2014-02-13 02:37 UTC (History)
3 users (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 Jozef Mlich 2013-10-29 12:48:14 UTC
Problem description: 
The background of transparent image import is black.

Steps to reproduce:
1. Create presentation
2. Find transparent png in firefox e.g. "http://upload.wikimedia.org/math/d/6/d/d6dba07916b9397a07f3399d037a126c.png" 
3. Right Click -> Copy
4. in Impress Right Click -> Paste

Current behavior:

The background of transparent picture is black. I have to paste the image into odt and copy it again.

Expected behavior:
Copy&Paste function should work same for presentation and document. The transparent background should stay transparent.
              
Operating System: Fedora
Version: 4.1.2.3 release
Comment 1 Cor Nouws 2013-10-30 15:40:18 UTC
Hi Jozef,

thanks for the issue. I see the problem too, but not when I first save the image to my computer and copy/paste from there.

Can you pls test that?
Comment 2 Jozef Mlich 2013-10-30 16:09:05 UTC
Problem occurs only in when using copy & paste. 

The approach "Insert" -> "Picture" -> "From File" works as expected. 

Also, the copy&paste approach in works well in document editor tool.
Comment 3 Henrik Gebauer 2014-01-13 19:28:52 UTC
I have the same problem with Libreoffice Writer, so it doesn't seem to be presentation specific.
I paste my images to a paint programm (KolourPaint) and copy it again. Using LO 4.1.3.2
Comment 4 lisamiller1963 2014-02-13 02:37:27 UTC

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