Since updating to LO RC3 (using a package built-from-source, with no patching on top of the sources), I notice that only Writer will launch from the .desktop file. Looking at the entries, I notice the "TryExec" and "Exec" lines are inconsistent with each other; example: thinkpad ~ $ grep Exec /usr/share/applications/{writer,calc,impress}.desktop /usr/share/applications/writer.desktop:TryExec=oowriter /usr/share/applications/writer.desktop:Exec=lowriter %U /usr/share/applications/calc.desktop:TryExec=localc /usr/share/applications/calc.desktop:Exec=oocalc %U /usr/share/applications/impress.desktop:TryExec=loimpress /usr/share/applications/impress.desktop:Exec=ooimpress %U ..Writer is all that works here, which does indeed have the correct Exec entry to spawn the binary. I am using enlightenment:0.17, which builds its menu from gnome-menus for the FDo spec. In RC2, all entries worked as expected, so it seems like a regression.
I do not see any TryExec in any .desktop file provided by LO. Where exactly did you get those sources?
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
needinfo keyword redundant by needinfo status.
@ Andrew In 3.5.0 still reproducible?
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
Thanks, I don't think it's necessary to comment so many times however :-) My poor inbox!
Sorry for that. It is not only your inbox, mine as well. ( In CC of ~900 bugs) I will check that ASAP...
Could you please test it with a vewer version of LibreOffice??
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/FDO/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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.