On Sat, 27 Jan 2001 19:44, you wrote:
> On Saturday 27 January 2001 02:02, you wrote:
> > On Wednesday 24 January 2001 10:31 am, you wrote:
> > > For those of you who don't have extensve edits to try to merge, I
> > > omitted the following lines from my earlier post inadvertantly.
> > >
> > > In a terminal
> > >
> > > # menudrake --ecit-system-menu
> > >
> > > should do what you want, but it does it for all users.
> > >
> > > Civileme
> >
> > I just tried that a couple days ago. It worked like you said - but -
> > that broke the control panel. My control panel can't access any of it's
> > menu items now. As of a matter of fact it doesn't come up with any menu
> > items at all. The left window is completely blank. I've tried to fix it
> > but I can't. How do I fix it ???
> >
> > Kelley Terry <[EMAIL PROTECTED]>
>
> Well, the simple way to fix the control panel is
> linux 3 at boot
> login as the user with the broken control panel
>
> $ rm -r ~/.kde -f
> $ startx
>
> and use .gnome instead if it is the gnome panel you refer to.
>
> more complicated is
>
> $ su -
> password:
> # updatedb
> # rpm --rebuilddb
> # update-menus
> log out and back in
>
> Civileme
Nope...dosn't work (at least with the KDE 2.1 stuff - which I know is
unsupported). What I noticed (after blowing away my .kde several times) is
that any menu entries via menudrake or the menu editor item on control panel
basically trashes the kcontrol
the items are still runnable from a command line (with a bit of tweaking)
Andrew
