Created attachment 120222 [details] Screenshot showing Format-Paragraph-Borders issues When I highlight a selection of a block of text (made up of 11 single line paragraphs) and select Format-Paragraph; then click on the Borders tab, the displayed 7 example radio buttons under Default Line Style are tiny, (about 5 pixels high!) and the four example radio buttons under Shadow Style Position are only about 3 pixels wide. Version: 5.0.3.2 Build ID: 1:5.0.3~rc2-0ubuntu1~trusty2 Locale: en-GB (en_IE.UTF-8) Running under Linux Mint 7.02 Cinnamon 64-bit
Perhaps this is because it is using Gtk3, which is still experimental. Does it look ok, if you launch LibreOffice from a terminal like this: SAL_USE_VCLPLUGIN=gtk Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
(In reply to Beluga from comment #1) > Perhaps this is because it is using Gtk3, which is still experimental. > > Does it look ok, if you launch LibreOffice from a terminal like this: > SAL_USE_VCLPLUGIN=gtk > > Set to NEEDINFO. > Change back to UNCONFIRMED after you have provided the information. Sorry about the delay. Not sure what you meant by this. I tried launching it from a terminal with: SAL_USE_VCLPLUGIN=gtk libreoffice& and it launched with warning message on the terminal saying: Warning: failed to read path from javaldx The theme seemed to have changed The same behaviour occurred in the file when I selected several paragraphs and did FORMAT-PARAGRAPH-BORDER.
I'm not seeing this in Ubuntu with Unity, so might be something specific to Cinnamon. Mint 17.3 with a new Cinnamon is coming real soon, so I hope you will give us an update on this issue after it hits. Ubuntu 15.10 64-bit Version: 5.0.3.2 Build ID: 1:5.0.3~rc2-0ubuntu1 Locale: en-US (en_US.UTF-8)
Created attachment 121877 [details] Screenshot of icons Icons show up normal for me when I tested it. LO version: 5.0.3.2 Build ID: 1:5.0.3~rc2-0ubuntu1 Locale: en-AU (en_AU.UTF-8)
Forgot to add to my last comment that I am using Ubuntu 15.10 with unity.
Tested on mint cinnamon too and was still not able to reproduce the bug. LO Version: 5.0.3.2 Build ID: 1:5.0.3~rc2-0ubuntu1~trusty2 Locale: en-AU (en_AU.UTF-8) OS: Mint 17.2 Cinnamon
Niall: could you try this: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
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 INVALID 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 Sun, 11 Sep 2016 21:43:24 +0200
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-20161010