After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 611596 - Startup Applications Preferences Manager Fails to Save Changes.
Startup Applications Preferences Manager Fails to Save Changes.
Status: RESOLVED DUPLICATE of bug 597623
Product: gnome-session
Classification: Core
Component: gnome-session-properties
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-02 13:42 UTC by Wayne Sallee
Modified: 2010-03-02 13:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Wayne Sallee 2010-03-02 13:42:33 UTC 
After editing a startup item, the Startup Applications Preferences Manager fails to save the change.


To reproduce: 

In the Startup Applications Preferences Manager, click on a startup item, click edit, make a change in the command block, click save, click close. Then open the Startup Applications Preferences Manager, and click on the startup item, click edit, and you will see that the change was not made.


To get around the bug:

After clicking save, reclick on the startup item, and it will show the changes that you just made, click save, click close. Then open the Startup Applications Preferences Manager, and click on the startup item, and you will see that it correctly saved your changes.


Summary:

If you don't make it recheck the changes made before closing the Startup Applications Preferences Manager, it will fail to save the changes.
Comment 1 Vincent Untz 2010-03-02 13:57:22 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 597623 ***