the menu has disapeard

[NoOp]

On 01/22/2010 02:28 PM, Johnneylee Rollins wrote:
> On Fri, Jan 22, 2010 at 2:16 PM, NoOp <configure your client to eliminate this! - it's rude> wrote:
>> On 01/22/2010 12:44 PM, Johnneylee Rollins wrote:
...
>>>>
>>> gconftool –recursive-unset /apps/panel
>>> rm -rf ~/.gconf/apps/panel
>>> pkill gnome-panel
>>> run those commands, they may need root privileges for one or two. That
>>> should reset you back to default. If you don't see anything change do
>>> this command
>>> sudo /etc/init.d/gdm restart
>>
>> That's a bit drastic don't you think? Have you done that on your own
>> system today before recommending? Please do & tell us the results.
>>
> The results is a default set of panels.

And, for those of us with heavily configured panels means that the user
needs to go through re-configuring them.

>> First of all you/we have no idea what he may have done to remove the
>> panel to begin with. Second, using Tab's suggestion will most likely fix
>> the issue. The Applications|Places|System menu can easily be added to
>> the new top panel (if the panel doesn't restore properly) by:
>> right-click the new top panel, 'Add to Panel'|Main Menu.
> What does it matter what he did to remove the panel?
> If he has a bottom one, he can remove the directory and it will be
> created again.
> Maybe you should work on getting away from the desktop and work more
> in the command line... hmm...

hmm... I'm quite familiar with the cli and make full use of it daily.
Perhaps you should realize that gui tools are available for a reason.

>>
>> Please don't recommend rm'ing anything (particularly to a potential new
>> user) without first checking to see if it is something that may be
>> simple first. Further, 'killall gnome-panel' would have been my
>> suggested method to restart the gnome-panel(s). See: man killall
>>
> I don't see why the rm'ing of that command would do anything hurtful
> as it generates it again...

No. You blow out his .gconf/apps/panel without even backing it up first!
You've no idea what customizations may have been done by the user prior
to suggesting an rm.

> 
> I have done the exact same set of commands. Maybe you should read it
> clearly and notice it removes some config files in the user's home
> directory. Even running sudo with that rm will only remove his own
> files, which I have said are regenerated...
> Maybe you should read a bit more and not jump on any rm command.

Maybe you should *think* first.

> 
> Tab's command is fine if you want to work on getting it reconfigured
> manually. I'm not a fan of manually doing something that can be fixed
> quickly.
> 
> As per rm'ing in general. It's permanently deleting files.
> you can also do this set of commands instead.
> 
> gconftool –recursive-unset /apps/panel
> cp -r ~/.gconf/apps/panel ~/.gconf/apps/panel.backup
> killall gnome-panel
> 
> Thanks for the killall tip. I messed that one up a bit, but not badly.