Created attachment 123136 [details] confirmation text invisible When using base (it happens in other places too), if I modify a request then quit, the message box doesn't display the text. Workaround: if I try to select the invisible text, it appears. This workaround doesn't always work. Platform: archlinux, x64 with radeonsi. Intel i7 4770k+HD7850 I thought it was a font problem, but as the text can appear when selected, I don't think so. What is strange is that most of the time (in writer for example), the display messages are ok. In Base, I can reproduce this 100% of the time. It may happen in Calc too.
Created attachment 123137 [details] if I select the text, it appears Tried with the english and french interfaces: same problem. Tried also resetting my LibreOffice config: idem
Created attachment 123138 [details] in writer after a "search & replace" Happens in writer too: after a "search and replace" for example
Created attachment 123139 [details] same workaround
Please provide test document and step by step instructions how to reproduce the bug. Thanks.
Created attachment 123661 [details] test document with procedure
Not reproduced. 64-bit, KDE Plasma 5 Build ID: 5.1.1.3 Arch Linux build-2 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 8d267cdd48e8b736a81a9e76ea5803e6847d791e CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on March 24th 2016
Hello, please could you test https://wiki.archlinux.org/index.php/LibreOffice VCL UI interface, use one of the SAL_USE_VCLPLUGIN Thanks
Created attachment 124128 [details] visible but unreadable fonts
My system now display visible text, but unreadable for some messages. So, I enabled experimental features in LO and tried export SAL_USE_VCLPLUGIN=gtk3 libreoffice This works great ! I can see the messages. The other options (kde4, gtk and gen) result in the same unreadable text.
I'm not alone with this pb, seems driver related (radeon hd7850 here) https://bbs.archlinux.org/viewtopic.php?pid=1617906
The problem depicted in attachment 124128 [details] is already reported as bug 99446, and is currently exclusive to the 5.1 series (fixed in 5.2 and later).
jdruel: could you try with 5.2 http://dev-builds.libreoffice.org/pre-releases/rpm/x86_64/ https://wiki.documentfoundation.org/Installing_in_parallel/Linux If all your problems go away, I think you could set this to RESOLVED DUPLICATE of bug 99446
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20161207
Dear Bug Submitter, 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 MassPing-NeedInfo-20170131