Description of problem: OpenOffice Quickstarter does not stay loaded after a logout. Version-Release number of selected component (if applicable): openoffice.org-core-3.0.0-9.10.fc10.x86_64 How reproducible: 100% Steps to Reproduce: 1. Launch OpenOffice 3 2. Navigate to Tools -> Options -> OpenOffice.org -> Memory 3. Enable "Enable systray Quickstarter" 4. Notice that Quickstarter loads in the Gnome "Notification Area". 5. Close OpenOffice 6. Go back to the Quickstarter option and you will see it is no longer enabled 7. Logout and login and you will notice that it indeed does not stay loaded Actual results: OpenOffice.org Quickstarter does not stay loaded (enabled). Expected results: OpenOffice Quickstarter stays loaded Additional info:
Indeed, hum.
bah, the code is pointing towards the old 2.X layout not the 3-layer 3.X layout
Fix filed upstream, and checked in. The reason for error can be seen visible at user level the link at ~/.config/autostart/qstart.desktop points to /usr/lib64/openoffice.org/basis3.0/share/xdg/qstart.desktop when it should point to /usr/lib64/openoffice.org3/share/xdg/qstart.desktop
Do you know when it will be pushed out to rawhide?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Done in rawhide, will be in first OOo F-10 update if there is one
*** Bug 477321 has been marked as a duplicate of this bug. ***
*** Bug 479549 has been marked as a duplicate of this bug. ***
openoffice.org-3.0.1-15.1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/openoffice.org-3.0.1-15.1.fc10
openoffice.org-3.0.1-15.2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
I have tested this from F10 updates-testing via yum and the QuickStarter now works correctly.
Should be closed fixed "currentrelease" NOT "nextrelease"--right?
Re: "currentrelease" NOT "nextrelease", you'd think so, or "errata", but that what the automated bodhi tooling does when an update is pushed, *shrug*.