newb85
December 30th, 2009, 01:03 PM
Whilst attempting to remove the gnome panel (to make way for a Cairo Dock) in an easily reversible fashion, I've run into a few quirks which have me baffled. I'm probably missing something, so I'll refrain from calling any of them bugs and instead describe them here in hopes of answers from someone(s) more knowledgeable than I.
First off, here's the method CD's help recommends:
Open gconf-editor, edit the key /desktop/gnome/session/required_components_list, and erase its content ("panel"). Restart your session : the GNOME-panel will not be started.That method did not work in its unmodified form. The panel still persists in spite of attempts to "killall" it. I also attempted to go down one tier in the folder list and remove the value of "panel" (gnome-panel). I can't say why that method didn't work, either (even when I replaced the value with "__" in case of default behavior for blank values). Then I got the brilliant idea of using gconf to force Cairo-Dock; when I replaced the value of "panel" with cairo-dock, gconf did not force CD, but it did finally stop forcing the panel. :confused:
Also, I read somewhere that these settings should be accessible in the terminal under the folder .gconf in the home directory. It appears that, while this is the case, folders shown in gconf-editor do not exist in the .gconf folder unless something within them has been changed from its default value. For example, in my case, the folders existed as far down as .gconf/desktop/gnome, but the folder "session" didn't exist until after I used gconf-editor to change the value of "panel" to cairo-dock. I suppose this behavior makes sense, but it did have me frustrated for some time.
Thirdly, I've heard several people quip that Ubuntu is superior to Windows because you don't have to reboot when changes are made. Isn't there a way to make GNOME reload its configuration without completely rebooting?
Input would be appreciated. Thanks!
First off, here's the method CD's help recommends:
Open gconf-editor, edit the key /desktop/gnome/session/required_components_list, and erase its content ("panel"). Restart your session : the GNOME-panel will not be started.That method did not work in its unmodified form. The panel still persists in spite of attempts to "killall" it. I also attempted to go down one tier in the folder list and remove the value of "panel" (gnome-panel). I can't say why that method didn't work, either (even when I replaced the value with "__" in case of default behavior for blank values). Then I got the brilliant idea of using gconf to force Cairo-Dock; when I replaced the value of "panel" with cairo-dock, gconf did not force CD, but it did finally stop forcing the panel. :confused:
Also, I read somewhere that these settings should be accessible in the terminal under the folder .gconf in the home directory. It appears that, while this is the case, folders shown in gconf-editor do not exist in the .gconf folder unless something within them has been changed from its default value. For example, in my case, the folders existed as far down as .gconf/desktop/gnome, but the folder "session" didn't exist until after I used gconf-editor to change the value of "panel" to cairo-dock. I suppose this behavior makes sense, but it did have me frustrated for some time.
Thirdly, I've heard several people quip that Ubuntu is superior to Windows because you don't have to reboot when changes are made. Isn't there a way to make GNOME reload its configuration without completely rebooting?
Input would be appreciated. Thanks!