Bug 98625 - Rendering of ellipse filled with bitmap in slideshow
Summary: Rendering of ellipse filled with bitmap in slideshow
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected) release
Hardware: IA64 (Itanium) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Slide-Show
  Show dependency treegraph
Reported: 2016-03-12 21:37 UTC by Colin Brown
Modified: 2019-01-12 13:53 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

.odp file illustrating bug (23.26 KB, application/vnd.oasis.opendocument.presentation)
2016-03-12 21:37 UTC, Colin Brown

Note You need to log in before you can comment on or make changes to this bug.
Description Colin Brown 2016-03-12 21:37:50 UTC
Created attachment 123532 [details]
.odp file illustrating bug

Slide containing an ellipse drawn with the ellipse tool, then area filled with bitmap, renders as an octagon in slideshow mode. 

However it is rendered correctly in normal mode and in the slide pane. Also tried exporting as pdf and jpg. They were also rendered correctly. Ellipse filled with colour rendered also OK too.

Suspect it might be meant to render as a many sided polygon, but the number of sides sticks at 8 for some reason.
Comment 1 Regina Henschel 2016-03-13 13:37:12 UTC
Please have a look at the settings in Tools > Options > LibreOffice > View. Try it with enabled hardware acceleration and without it.

I see the bug, if I disable use of hardware acceleration. I use LO 5.1 and LO build from master, on Windows 7 32-bit.

[I thought have read such bug report already, but I can't find it. Perhaps bug 50429]
Comment 2 Colin Brown 2016-03-15 10:36:13 UTC
Unfortunately, the option to use hardware acceleration is greyed out on my installation. Presumably my hardware does not have it. (It's a Lenovo H530S, unmodified, running Windows 10). So I can only run without hardware acceleration - I would guess that there will be many other users in the same situation.

I have run many previous versions on my machine and never encountered this bug. It did not exist in, which I only replaced with to get away from a different bug (98579).
Comment 3 Colin Brown 2016-04-20 11:57:12 UTC
The bug is still present in version This time, running on a different machine, my wife's HP laptop under up-to-date Windows 10. The option to enable hardware acceleration as suggested by Regina Henschel is greyed out on that machine too.
Comment 4 QA Administrators 2017-05-22 13:27:28 UTC Comment hidden (obsolete)
Comment 5 Roman Kuznetsov 2019-01-12 13:53:30 UTC
don't repro in

Build ID: 7809ec859d5bdb5dedb259a362a15324088b334c
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

with and without "Hardware acceleration"