The bug has been initially filled to cairo <https://bugs.freedesktop.org/show_bug.cgi?id=49118> But after careful analysis, it happens that libreoffice creates surface of 0x0 size which is forbidden in the specs (Xlib requires at least 1x1) and correct the size before displaying it. Unfortunately, a change in cairo to be complaint with the specs breaks libreoffice slideshow. There are now a good dozen of bugs in debian and until cairo 12.1 is available, it could be wyse to fix in in 3.5.3. In the link above you have a full backtrace that exhibits the call path for the 0x0 size
The corresponding commit [1] allowing such “illegal” behavior is already committed the Cairo repository. [1] http://cgit.freedesktop.org/cairo/commit/?id=9e81c5b737cda9dc539b2cf497c20ac48ddb91ac
(In reply to comment #1) > The corresponding commit [1] allowing such “illegal” behavior is already > committed the Cairo repository. However, cairo maintainer indicated that while he agrees that the cairo behavior did change, he thinks that creating 0x0 surface still should not be allowing as it not allowed in X protocol. He is the comment in the patch /* Note: the minimum surface size allowed in the X protocol is 1x1. * However, as we historically did not check the minimum size we * allowed applications to lie and set the correct size later (one hopes). * To preserve compatability we must allow applications to use * 0x0 surfaces. */
Not sure if the reason is the same, but the behaviour is the same with cairo 1.12.16 and libreoffice 4.1.3.2. Maybe some regression? see here, not sure if it is a duplicate or not because I don't know if the root cause is the same: https://bugs.freedesktop.org/show_bug.cgi?id=70987
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
If you have not fixed it the bug is still there. I cannot test as cairo has been changed for compatibility reason and because you haven't responded in a timmely manner.
This bug is confirmed to be present also in LO 4.4.2.2 cairo: 1.14.2 the behaviour is exactly the same as described earlier.
Still here, libreoffice 4.4.4.3 & cairo 1.14.2
Some info: on gentoo, compiling cairo (1.14.2) without xcb renderer over xlib seems to fix this behaviour.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Xisco, why did you touch this bug after such a long time, and even changed the “resolved reason” from *fixed* to *worksforme* without any explanation? This just created noise, and is additionally in my opinion incorrect.
Setting it to RESOLVED FIXED is incorrect too. RESOLVED FIXED is only used when the commit fixing the problem is identified.