Created attachment 942655 [details] planner-gnome656373-broken-open-file-on-startup.patch Description of problem: If you double-click on a .planner data file (Nautilus), Planner opens blank and does not open it. You may open it from the menu. The real bugs are the upstream bugs, and have already been solved: https://bugzilla.gnome.org/show_bug.cgi?id=656373 https://bugzilla.gnome.org/show_bug.cgi?id=675679 This is a bug for the _maintainer_ of the package. Given that the upstream bugs are solved, and that the bug is really inconvenient for the user, I think an update should be issued. I have rebuilt the RPM package with two additional patches (downloaded from the links above), and Planner now works as expected, and opens all files by double-clicking. I attach the patches to this bug. Version-Release number of selected component (if applicable): planner-0.14.6-13.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Navigate to a folder with a Planner file inside 2. Double-click on the planner file 3. Planner opens blank Actual results: Planner opens blank. Expected results: The .planner file should be opened. Additional info:
Created attachment 942656 [details] planner-gnome675679-files-with-spaces-fail.patch
Just added this four lines to planner.spec: Patch15: planner-gnome656373-broken-open-file-on-startup.patch Patch16: planner-gnome675679-files-with-spaces-fail.patch and %patch15 -p1 -b .fileonstartup %patch16 -p1 -b .filespacesfail
In Fedora 21 is the same...
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.