Description of problem:
gnome-session-properties does not save a start-up job which is same as previously deleted one.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open gnome-session-properties. Create a new start-up job. Save it. Close gnome-session-properties.
2. Re-open gnome-session-properties. Verify the job created at step 1 exists. Delete it. Close gnome-session-properties.
3. Re-open gnome-session-properties. Verify the delete job is absent. Create a new one, identical to the deleted job. Save it. Verify the job is in the list of start-up jobs. Close gnome-session-properties
4. Re-open gnome-session-properties. The job created at step 3 is misisng fom the list.
A new job is not saved if it matches a previously deleted one.
A new job should always be saved.
It could be even worse: it seems the job does not even have to be identical to a delete one; if the command line is different, the job is still not saved. Likely the bug occurs even if only the name of the job matches a previously deleted one.
i vaguely remember this bug getting fixed upstream, devack+, but still need to investigate.
turns out this is just another case of bug 785828
*** Bug 1069499 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.