Open the file A0 activity.odt. The title ("Activities") have missing letters, but a copy paste in a text editor recover all the text so the problem is about the displaying in LO. This is always reproducible. Enable OpenGL for all rendering (Tools-Options menu) makes the title have right displaying. The OS is Debian Jessie (8) with Xfce. Its anti-aliasing is disabled because it has no advantage with HDMI display. Backwards of anti-aliasing is a degraded quality of displaying of Xfce programs like Xfce Desktop. The anti-aliasing in options of LO is enabled. But it does nothing. When anti-aliasing is enabled again in Xfce, all works fine. Iceweasel and others software work fine with better displaying when the anti-aliasing is disabled in Xfce. Why not with LO. Expected : LO should have a fine displaying for all characters of text when the anti-aliasing is disabled in the window manager like Xfce when a great quality of screen is used. OpenGL should not be needed in this case. lspci 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] lscpu model name: AMD A4-5300 APU with Radeon(tm) HD Graphics
Created attachment 119035 [details] Original file
Created attachment 119036 [details] With no anti-aliasing in Xfce
Created attachment 119037 [details] With no anti-aliasing in Xfce (deleting the A of the title)
> Enable OpenGL for all rendering (Tools-Options menu) makes the title have right displaying. The title is right but the remaining text has a big aliasing effect.
IMHO, this is a bug in the Liberation fonts, which are not prepared (hinted) for use without antialiasing.
(In reply to Adolfo Jayme from comment #5) > IMHO, this is a bug in the Liberation fonts, which are not prepared (hinted) > for use without antialiasing. But Liberation font is not concerned. In the title, only Arial is used from the non-free :/ msttcorefonts. So, do you think that the culprit should be Arial ? I will explore the track. Thanks.
(In replty of comment #6) After some tries, all fonts are concerned by this issue. None of the other software that I am using, have this bug.
I disabled anti-aliasing in Xfce options Appearance - Fonts. Not observing the problems in your screenshots. It was curious that the text font stayed anti-aliased in LibO, even though I disabled anti-al. in LibO settings. Do you have any other font setting changes? Antergos 64-bit Xfce 4.12, LibO 5.0.1
(In reply to Beluga from comment #8) > Do you have any other font setting changes? Hinting is set on small in Xfce settings. I expect that this setting is enabled only with anti-aliasing. Still with LO 5.1.0.1.
This issue is still in 5.1.2.2 Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f.
So the "use anti-aliasing" LO option in tools menu has always no effect. Only the XFce parameter controls the anti-aliasing. Yes this does not explain why some characters are disappearing. But, is the "use anti-aliasing" LO option obsolete or disabled in code ? If it is right, it should be removed from the UI. Same issue with 4.5 Linux kernel. Architecture: amd64 (Radeon HD 7480D). mesa-utils: 8.2.0-1 xserver-xorg: 1:7.7+7 from Debian.
Still in LO 5.1.3.2, Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b
Bug 95547 and bug 89970 seem to be about the same issue. I'm hesitant to close bug 95547 as duplicate, but maybe if it counts as independent reproduction of the bug, then this could be set to new, and that one could be closed?
Rpnpif: do you observe the same as the reporter of bug 95547, that "Changing the size of the window will push the problem around (different letters will be missing) and sometimes hide the problem"? And also the effect of different font sizes.
(In reply to Buovjaga from comment #14) > Rpnpif: do you observe the same as the reporter of bug 95547, that "Changing > the size of the window will push the problem around (different letters will > be missing) and sometimes hide the problem"? And also the effect of > different font sizes. Sorry for the time to answer. Yes, I have the same effects of the bug 95547. And I can complete with an effect that I am seeing now: Change the zoom of the document has the same effect than change the font size, in other words, some letters are missing with some zoom ratio and anti-aliasing disabled. Regards.
So, I had also the bug 89970.
*** Bug 95547 has been marked as a duplicate of this bug. ***
Created attachment 125845 [details] Video demonstrating the issue coming on and off with antialiasing (from #99547) This video was uploaded by me for bug 95547.
Comment on attachment 125845 [details] Video demonstrating the issue coming on and off with antialiasing (from #99547) See the other attachments at bug #99547, including an ODP file which demonstrates the problem shown in this video.
** 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.4.1 or 5.3.6 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-20170901
Dear Rpnpif, 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 Rpnpif, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I do not see this issue in LO 7.0.4.2. Thanks.