Bug 206690

Summary:	profile changes not saved
Product:	[Fedora] Fedora	Reporter:	jim <fedorajim>
Component:	sabayon	Assignee:	Tomáš Bžatek <tbzatek>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	medium
Version:	9	CC:	extras-qa, jonstanley, tsmetana
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-15 03:54:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jim 2006-09-15 17:32:36 UTC

Description of problem:  Profile changes are not saved 


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. open sayabon
2. create new profile
3.  edit profile and save after every change 
  
Actual results: 
Edit --> Changes shows no changes   
exit the editor and the main window is greyed out  leaving you to force quit the
application 
Expected results:
profile changes saved  

Additional info:
fc6 test 3   fully updated  9-15-06

Comment 1 Alexander Larsson 2006-10-12 16:14:16 UTC

I don't see this with the current code. I wonder if it fixed itself or if
something is different on your box.

Comment 2 Alexander Larsson 2007-05-02 13:46:22 UTC

Do you still see this?

Comment 3 Bug Zapper 2008-05-14 02:21:39 UTC

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Jon Stanley 2008-05-15 03:54:31 UTC

The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming 
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.