Bug 340343 - Sabayon: Unable to save SLAB\Main Menu and Application browser settings
Summary: Sabayon: Unable to save SLAB\Main Menu and Application browser settings
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: Other Other
: P2 - High : Major with 5 votes (vote)
Target Milestone: ---
Assignee: Federico Mena Quintero
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-08 18:52 UTC by Forgotten User XNr0AseFVw
Modified: 2011-04-04 03:15 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User XNr0AseFVw 2007-11-08 18:52:13 UTC
Sabayon seems to not have any control over what can or cannot be presented on the main menu or the application browser.
Comment 1 Mark Gordon 2007-11-08 20:31:11 UTC
Some possibly relevant gconf keys are under /desktop/gnome/applications/main-menu.  Those should work, but they're probably not as discoverable as they would be if they were in the GUI.

It would probably help to make it explicitly clear what exactly you want to be able to do, especially if the lockdown features already in gconf aren't sufficient.
Comment 2 Forgotten User XNr0AseFVw 2007-11-09 16:27:20 UTC
I am unable to save any changes to the "SLAB" or Application browser.
When I run a sabayon session and > run more applications>Utilities>main menu.
I can edit the "main menu" and "more applications" content and when I view these changes by re-opening the more applications screen again the changes are there.
If I change the contents of the "favorites" on the SLAB and reopen the SLAB these changes are there. When I save this view and then logout out of the sabayon session and reopen the session the changes are all gone.
Comment 3 Gary Ekker 2008-03-26 18:08:12 UTC
Changing to component GNOME. Sorry for the spam.
Comment 4 Forgotten User wbt-beX79k 2008-05-27 20:24:18 UTC
This is currently not working in SLED 10 SP2, either.  Sabayon is not tracking any changes made to the slab so even if you try to customize it by adding/removing items from the gnome slab, sabayon never notices (and the changes are never saved as a result).
Comment 5 Forgotten User XNr0AseFVw 2008-05-30 16:25:05 UTC
How do we provide desktop configuration in this manner then?
Comment 6 Forgotten User wbt-beX79k 2008-05-31 01:23:07 UTC
It looks like the slab is populated by entries in ~/.local/share/gnome-main-menu/applications.xbel instead of gconf entries.  I'm not sure when this changed but gconf seems like a much more suitable backend for storing gnome configuration information.  
Comment 7 Forgotten User XNr0AseFVw 2008-05-31 11:42:37 UTC
can this be fixed soon? it is a goal of the education project to predefine several desktops for certain age groups so that only appropriate software is available.
Comment 8 Federico Mena Quintero 2008-06-02 14:24:18 UTC
Hmmm, the profile zipfiles should have an entry for ~/.local/share/gnome-main-meu/applications.xbel.  Could you please check if this is the case?  We definitely don't ignore the .local hierarchy, so I wonder what's wrong there.
Comment 9 Forgotten User wbt-beX79k 2008-06-02 14:29:56 UTC
In SLED 10 SP2, if I open up a terminal and manually cp /path/to/good/applications.xbel ~/.local/share/gnome-main-meu/applications.xbel (after doing an su to root for permissions reasons), sabayon will track it and add it to the profile.  If I just modify the slab entries like I normally would (drag and drop launchers onto it, right-click in the application browser, etc...) it never gets tracked.  I'll try to do some testing in OpenSUSE 11 to see if the behavior is the same.
Comment 10 Forgotten User XNr0AseFVw 2009-01-12 17:10:18 UTC
Will there be any resolution to this soon? It would be extremely nice to market openSUSE as having "parental" controls.
Comment 11 Larry Finger 2011-04-04 03:15:04 UTC
The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks!