Bug 122443 - Crashes playing a video
Summary: Crashes playing a video
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Media
  Show dependency treegraph
Reported: 2019-01-03 11:55 UTC by anmeldung-documentfoundation
Modified: 2019-08-19 07:04 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description anmeldung-documentfoundation 2019-01-03 11:55:11 UTC
After starting a presentation that includes a video, the video starts to play but jerks. After a while of maybe 40-60 seconds, LibreOffice crashes.

Starting LibreOffice from command line it outputs an error after crashing:

Gdk-Message: 12:44:32.524: Error 71 (Protocol error) dispatching to Wayland display.

I am not sure, whether this a problem of LibreOffice itself.

Steps to Reproduce:
1. Embed a video into impress presentation
2. Start the presentation
3. Play the video

Actual Results:
The video jerks, LibreOffice crashes

Expected Results:
The video plays smoothly, LibreOffice does not crash

Reproducible: Always

User Profile Reset: No

Additional Info:
Comment 1 anmeldung-documentfoundation 2019-01-03 12:33:00 UTC
Update: I get a full system crash under Xorg.
Comment 2 Xisco Faulí 2019-01-03 13:50:33 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 3 anmeldung-documentfoundation 2019-01-03 13:56:14 UTC
Hi, I am using the latest version of LibreOffice under Arch Linux:

~ $ libreoffice --version
LibreOffice 10(Build:2)
Comment 4 anmeldung-documentfoundation 2019-01-03 17:14:08 UTC
Update: This problem occurs only if the video does not fit the screen. In my case the video had a Position X of -0.10 cm. I have moved it into the slide and there is no error anymore.
Comment 5 raal 2019-01-03 19:15:43 UTC

Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
Thank you
Comment 6 Hiromi Kuramoto 2019-01-08 05:55:25 UTC
Hi, I tried this bug using mp4 and 3gp in MacOS Sierra, but I cannot reproduce.

reproduce in
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
CPU threads: 4; OS: Mac OS X 10.12.5; UI render: default; 
Locale: en-US (ja_JP.UTF-8); Calc: group threaded
Comment 7 QA Administrators 2019-07-12 02:52:56 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-08-19 07:04:37 UTC
Dear anmeldung-documentfoundation,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team