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 356478 - Unchangeable profile
Unchangeable profile
Status: RESOLVED FIXED
Product: sabayon
Classification: Deprecated
Component: general
2.12.x
Other Linux
: Normal major
: ---
Assigned To: Maintainers of sabayon
Maintainers of sabayon
: 333906 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-18 03:02 UTC by Russell Perkins
Modified: 2010-01-18 19:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Russell Perkins 2006-09-18 03:02:55 UTC 
After setting a profile. No other profiles are able to be applied or removed because of the lock on the gconf.
Comment 1 Guillaume Desmottes 2006-12-14 17:39:52 UTC 
I can confirm this very annoying but with Sabayon 2.12.4 (Ubuntu Feisty).

Set the severity on major as Sabayon it's not very useful if we can't update profils.
Comment 2 Guillaume Desmottes 2006-12-14 17:43:40 UTC 
*** Bug 333906 has been marked as a duplicate of this bug. ***
Comment 3 Sayamindu Dasgupta 2006-12-21 15:01:54 UTC 
Does manually removing .gconf directory help ?? 
If that is the case - a quick and dirty fix/hack may be to modify /etc/X11/Xsesssion.d/60sabayon_apply so that it deletes the users .gconf directory first.
Comment 4 Scott Balneaves 2009-12-16 17:06:04 UTC 
Well, it looks to me as if sabayon is storing most of it's stuff within $HOME/.gconf.path.default, but for mandatory items they SHOULD be in $HOME/.gconf.path.mandatory

I know this is an old bug, but someone posted on this in the mailing list the other day, so I'll dig into it, and see what's going on.
Comment 5 Scott Balneaves 2010-01-18 19:49:13 UTC 
ok, tested on latest version.  Items set mandatory definitely ARE going into mandatory for me.  I'm going to close this one off.