Created attachment 102789 [details] Sample slides to see the bug - Take a PNG image (like that attached) with a native transparency gradient - insert it in an Impress slide - set the Impress image transparency property to more than 0% (i.e. 50%) - you will see the correct image effect: -- on editing mode views; -- on presentation console next slide views; -- on pdf exports; - you will see the wrong image effect (the native transparency gradient loses itself and image border is well defined, see attached screenshots): -- on the full screen presentation mode (bug); -- on the current/main slide frame on presenter console (bug). Attached to this bug are: - sample odp presentation; - pdf export; - sample png image; - bug evidencing screenshots. Quite similar bugs are: - bug 42836; - bug 33591; - bug 35681; - bug 36766 (Meta Bug Report to collect all Reports concerning gradient and transparency). Many of these 3.3.x bugs so that I suppose this may be either a regression or an ancient unsolved bug... What do you think about? Have a nice evening, Carlo
Created attachment 102790 [details] Sample slides to see the bug, pdf export, ok
Created attachment 102791 [details] sample png image with native transparency gradient
Created attachment 102792 [details] Impress Slides editing, dias both ok, image properties details
Created attachment 102794 [details] Impress Slides editing, dias both ok
Created attachment 102795 [details] Presentation screen, dia 1, ok
Created attachment 102796 [details] Presentation screen, dia 2, ko
Created attachment 102797 [details] Presenter console, dia 1 main, dia 2 next, both ok
Created attachment 102798 [details] Presenter console, dia 2 main, none next, dia 2 ko
Ciao Carlo. I confirm the same bug under Win7x64 using LibO 4.2.5.2 and 4.4.0.0.alpha0+ Build ID: b9dca968c6fd0ab5ca140c65b0e54d153cd34986 TinderBox: Win-x86@42, Branch:master, Time: 2014-07-18_22:51:20 AOO 4.1 shows the exact bug which is then "inherited from OOo"
Hi Everyone, I have just tested this issue on the new bug hunting session on Versione: 5.0.0.0.beta1 (x64) Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3 Versione locale: it-IT (it_IT) And I have just discovered that not only the issue is confirmed, but when you terminate the presentation time clicking on the last slide, the said LibreOffice version (5.0 beta 1, Win64) crashes. I think there may be a *duplicated rendering path* on the code by which the editing time rendering is ok, but the presentation time one is ko with some memory leaks... or something like this. I will point this just now on the libreoffice QA list. Have a nice night, Carlo
(In reply to Carlo Strata from comment #10) > Hi Everyone, > > I have just tested this issue on the new bug hunting session on > Versione: 5.0.0.0.beta1 (x64) > Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3 > Versione locale: it-IT (it_IT) > > And I have just discovered that not only the issue is confirmed, but when > you terminate the presentation time clicking on the last slide, the said > LibreOffice version (5.0 beta 1, Win64) crashes. You have run into bug 91426, which is fallout from recent internal UI toolkit code changes (VclPtr).
(In reply to Beluga from comment #11) > (In reply to Carlo Strata from comment #10) > > Hi Everyone, > > > > I have just tested this issue on the new bug hunting session on > > Versione: 5.0.0.0.beta1 (x64) > > Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3 > > Versione locale: it-IT (it_IT) > > > > And I have just discovered that not only the issue is confirmed, but when > > you terminate the presentation time clicking on the last slide, the said > > LibreOffice version (5.0 beta 1, Win64) crashes. > > You have run into bug 91426, which is fallout from recent internal UI > toolkit code changes (VclPtr). Thank you, Beluga, but I'm very worried about my original issue's mean: are there two code objects that do slide rendering, instead of one only??? Is the case to verify the situation? Have a nice day, Carlo
I have tested again the "Sample slides to see the bug" file on this system: - Microsoft Windows 10, x64, ita, home, daily updated; - LibreOffice 5.0.2.2, win64 build. The bug still remains. Carlo
** 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.6 or 5.2.3 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-20161108
Dear QA Administrators and QA Team at all, I personally test this bug each time a new version is released. I haven't see anything new until now however: the bug is still alive! My last test environment is: - Microsoft Windows 10, version 1607 "redstone 1", build 14393.693, x64, ita, home, daily updated; - LibreOffice, Windows, x64 build, 5.2.5.1 (5.2.5 final, because I understand that 5.2.5.2 was brutally skipped to permit the release of the 5.3.0.3, that is the 5.3.0 final); - LibreOffice, Windows, x64 build, 5.2.5.1 Italian local Help. or, directly from LibreOffice splash screen: Versione: 5.2.5.1 (x64) Build ID: 0312e1a284a7d50ca85a365c316c7abbf20a4d22 Thread CPU: 4; Versione SO: Windows 6.19; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT); Calc: group I haven't tested the bug on the new 5.3.0 branch yet because, despite I'm an experienced computer engineer, I prefer to adopt the new branch starting on .1 or even .2 at third version number (that is 5.3.1 or 5.3.2, in this case) and also I work with LibreOffice in my job with various other less technician people. I don't want to be boring but I suggest to you to read (my) comment 10 and comment 12. I will try as soon as possible to test both 5.3.x branch and Master one (5.4.x) and I will post here a new comment. Moreover, if I would have more free time I personally try to get a look to the code to see if there would be some duplicate rendering code all over the source or different call type or call way to the same rendering objects/functions or something else. Thank you very much and have a nice day, Carlo
(In reply to Carlo Strata from comment #15) > I don't want to be boring but I suggest to you to read (my) comment 10 and > comment 12. Do you mean you are still getting this with 5.2: "when you terminate the presentation time clicking on the last slide, the said LibreOffice version (5.0 beta 1, Win64) crashes" ?
(In reply to Buovjaga from comment #16) > (In reply to Carlo Strata from comment #15) > > I don't want to be boring but I suggest to you to read (my) comment 10 and > > comment 12. > > Do you mean you are still getting this with 5.2: "when you terminate the > presentation time clicking on the last slide, the said LibreOffice version > (5.0 beta 1, Win64) crashes" ? No at all, the bug (the original still remaining issue) is the bad (annoying) rendering - only in presentation mode and not in edit one - of the second slide in the presentation attached to this bug! Full stop. The crash is - was! - an added further, but solved problem in some older LibreOffice builds. See my comment 12. Have a nice day, Carlo
I have just upgraded my notebook to this 5.3.0.3: Versione: 5.3.0.3 (x64) Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1 Thread CPU: 4; Versione SO: Windows 6.19; Resa interfaccia: predefinito; Motore layout: nuovo; Versione locale: it-IT (it_IT); Calc: group Always the same behaviour. I'm very sorry! The bug in still there! I don't want to be boring again, but I suggest to you to read (my) comment 10 and comment 12. I also remember here that the bug is "Inherited From OOo". Have all a nice day, Carlo
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Carlo Strata, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to QA Administrators from comment #20) > Dear Carlo Strata, > > 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 with the latest version of > LibreOffice from https://www.libreoffice.org/download/ > > If the bug is present, please leave a comment that includes the information > from Help - About LibreOffice. > > If the bug is NOT present, please set the bug's Status field to > RESOLVED-WORKSFORME and leave a comment that includes the information from > Help - About LibreOffice. > > 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) from > 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: > https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa > > Thank you for helping us make LibreOffice even better for everyone! > > Warm Regards, > QA Team > > MassPing-UntouchedBug Hi to Everyone, I tested this bug each time I update my LibreOffice version in all these years! Until 7.0.4.2 the bug lives, but today I test with the 7.1.0.3 (linux flatpak updated only few days ago), the is NOT present and the presentation was OK!!! My Help --> About LibreOffice version is: Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: it-IT (it_IT.UTF-8); UI: it-IT Flatpak Calc: threaded Thank you very much for your work! I teach in a 14 - 19 years-old boys and girls Italian School and I use and make to use there the linux mative and Windows (only PortableApps at the moment) versions. Have All of You a Sunny Day! Carlo
... the bug* is NOT present and...