...as it seems to do more harm than good, at least from my perspective of a user who upgraded and got something unexpected (no, switching the icon theme is not enough if you have that other option active, which is a default state). Related: http://unix.stackexchange.com/questions/79085/libreoffice-from-rpm-looks-ugly Or maybe it's just the algorithm to detect high contrast mode what is broken here. I am using dark theme in my LXDE env. (Cillop Midnite), but I definitely wouldn't classify it as hight contrast one. Well, as per [1]: > Automatically detect high contrast mode of operating system > > Switches LibreOffice into high contrast mode when the system background > color is very dark. This is so naïve. So please consider switching the discussed option off by default until the thing gets fixed on this level, and by then the default appearance can remain as with older LO releases. Observed with: libreoffice-4.1.4.2-2.fc20.x86_64 [1] https://help.libreoffice.org/Common/Accessibility
Also related: http://chakra-project.org/bbs/viewtopic.php?id=9707
Can I get a short concise summary of how to reproduce.
If you want to know my personal reproducer (Fedora 20): 1. install LXDE 2. install and apply Cillop Midnite GTK2 theme (IMHO not a high contrast one) 3. logout/login to make sure the theme is 100% applied 4. install LibreOffice 5. run LibreOffice (e.g., open some document) -> observe HighContrast icon theme applied automatically 6. try to switch icon theme -> nothing happens 7. disable "Automatically detect high contrast mode of operating system" -> suddently, icon theme can be changed to something normal Will provide any other circumstances if needed.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.