Bug 1069499

Summary: gnome-session-properties does not save modified start-up jobs
Product: Red Hat Enterprise Linux 6 Reporter: Assen Totin <assen>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6CC: tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-23 00:00:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Assen Totin 2014-02-25 07:16:37 UTC
Description of problem:
gnome-session-properties fails to save modifications to command line in a start-up job. 


Version-Release number of selected component (if applicable):
gnome-session-2.28.0-18

How reproducible:
Every time.

Steps to Reproduce:
1. Open gnome-session-properties. Create a new start-up (fill all 3 fields) job and save it. Close gnome-session-properties.
2. Re-open gnome-session-properties. Open the job created in step 1. Verify it has the same command line as entered at step 1. Modify the command line and save the chages. Close gnome-session-properties.
3. Re-open gnome-session-properties. Open the job created at step 1. The command line is still the one, set in step 1 (and not the one, modified in step 2).

Actual results:
Modification to comamnd line are not saved.

Expected results:
Modification to comamnd line should be saved.

Additional info:
There are other issues with this component too, e.g. if you delete a job and try to create the same, it will not be saved at all. This is rather confusing and needs attention.

Comment 2 Ray Strode [halfline] 2014-04-03 13:00:26 UTC
devack+

Comment 4 Ray Strode [halfline] 2014-06-23 00:00:24 UTC
i'm going to dupe this with bug 1069503 since they have the same root cause

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