Description of problem: LibreOffice Quickstarter stops working after installing libreoffice-kde. Version-Release number of selected component (if applicable): How reproducible: 100%. Reproducible every time. Steps to Reproduce: 1. Enable QuickStarter Tools > Options > Memory 2. Install libreoffice-kde 3. Actual results: QuickStarter no longer available in system tray Expected results: QuickStarter should be available in system tray. Additional info:
Forgot to mention. I am running Fedora 20 KDE. With LibreOffice Version: 4.2.4.2 Build ID: 4.2.4.2-18.fc20
The quick-starter is fairly deprecated by now, but... 1) and it doesn't exist when you log out and log in ? (i.e. the quickstarter deliberately will exit automatically during an update if it is running because the instance of libreoffice has been uninstalled and replaced) 2) If you log into a GNOME session is it also missing ?
1. No, I don't think so. If I have LibreOffice running, it would keep running without problem. Once I exit and reopen LibreOffice, quick-starter will run if libreoffice-kde is not installed and it won't run if libreoffice-kde is installed. 2. I can't test GNOME session because I can't afford to install 100s of GNOME packages over my KDE install. I did test libreoffice-kde under i3 and it started alright and worked without any problem. That points the problem to the KDE. I also tried running libreoffice --writer in terminal and enabled/disabled quick-starter but it didn't generate any error at all. What do you by fairly deprecated? Is it unmaintained? Does upstream plan to remove the feature? LibreOffice being a big and slow piece of software getting rid of quick-starter sounds like a bad idea.
(In reply to Sudhir Khanger from comment #3) > What do you by fairly deprecated? Is it unmaintained? Does upstream plan to > remove the feature? It has been disabled by default for many releases--from the very beginning, actually, unless I misremember. That has been >4 years. Nobody is actively working on it. In addition, it caused all kinds of libreoffice crashes on Fedora when the quickstarter was running during update of libreoffice and then used.
Are there any thoughts on removing this functionality altogether from LibreOffice? 1. Willingly and knowingly shipping buggy code is not in good faith. 2. With KDE Plasma moving to KStatusNotifier, Unity moving to libappindicator, and Gnome moving to message tray, it is only going to provide bad user experience.
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.