Bug 39772

Summary:	VIEWING: Custom animation ends with a black rectangle during preview
Product:	LibreOffice	Reporter:	Andreas Mantke <maand>
Component:	Impress	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	jeffdchang, LibreOffice, maand, yfjiang
Priority:	high
Version:	3.4.2 release
Hardware:	IA64 (Itanium)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:
Attachments:	A screenshot of the rewrite bug at the end.

Description Andreas Mantke 2011-08-02 13:44:50 UTC

Create a new presentation with only a bit text on a side. Then add the custom animation credits (Abspann in German)to the text. You will see a black rectangle during the preview inside the menu bar at the top of LibreOffice. Environment: openSUSE 11.4-x64, KDE 4.6, Nvidia-Graphic-Card Geforce 9600M GS (Laptop), Intel Core2 Duo 2 Ghz).

Comment 1 Andreas Mantke 2011-08-02 13:46:57 UTC

@ Rainer Bielefeld: I tried this custom animation with your sample document from Bug 35278.

Comment 2 Andreas Mantke 2011-08-02 13:51:58 UTC

Created attachment 49849 [details]
A screenshot of the rewrite bug at the end.

This is the screenshot after the preview was running. The black rectangle was a bit bigger beforehand.

Comment 3 Andreas Mantke 2011-08-02 13:52:50 UTC

@ Rainer Bielefeld: could you please test it with Windows?

Comment 4 Rainer Bielefeld Retired 2011-08-02 14:21:01 UTC

@Andreas:
Might be a "DUP of Bug 35278 - VIEWING: Custom animation ends with filled rectangle". I will check the Details tomorrow.

Comment 5 Jeffrey 2011-08-02 18:19:31 UTC

Reproduced on LibreOffice 3.4  340m1(Build:103) for OpenSuse Linux.

Problem occurs exactly as reporter describes.

The custom animation name in English is "Move Credits". It is under "Exciting" in the "Entrance Tab".

Comment 6 Rainer Bielefeld Retired 2011-08-17 06:39:00 UTC

DUP of "Bug 35278 - VIEWING: Custom animation ends with filled rectangle", what already has been assigned.

@reporter:
Please feel free to reopen this Bug if you find evidence that we have an independent issue here.

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