KDE Question: Extended "Start" menu went away

[StefanJ]

Core 5, running on a kernel from a few weeks back. Everything is hunky-dory except this frustration:

I do most of my work with the system logged in as user "mythtv".

Until last night, the KDE equivalent of a "Start" menu included all sorts of useful administrative stuff, like an Administration menu, and a System menu with a wide range of utilities.

For some reason, I am now only able to access a shrunken sub-menu with only "safe" choices.

I logged out and started a new xsession, this time as root. The "Start" menu was the real deal, with all choices.

Logged back in as mythtv. A right-click on the "F" logo brings up a menu-admin window, with a tantalizing "Edit Menu" selection . . . that does nothing.

I don't recall doing anything that would have removed user mythtv's administrative access. I haven't edited any KDE preferences that would have resulted in a stunted menu.

Anyone have an idea what happened? Any idea on how to go back to the way things were.

[alpha645]

Originally Posted by StefanJ

Core 5, running on a kernel from a few weeks back. Everything is hunky-dory except this frustration:

I do most of my work with the system logged in as user "mythtv".

Until last night, the KDE equivalent of a "Start" menu included all sorts of useful administrative stuff, like an Administration menu, and a System menu with a wide range of utilities.

For some reason, I am now only able to access a shrunken sub-menu with only "safe" choices.

I logged out and started a new xsession, this time as root. The "Start" menu was the real deal, with all choices.

Logged back in as mythtv. A right-click on the "F" logo brings up a menu-admin window, with a tantalizing "Edit Menu" selection . . . that does nothing.

I don't recall doing anything that would have removed user mythtv's administrative access. I haven't edited any KDE preferences that would have resulted in a stunted menu.

Anyone have an idea what happened? Any idea on how to go back to the way things were.

COuld be a bug in KDE. You could try to remove the KDE settings from your home dir (.kde I think). You will lose all settings, but after that KDE should function properly again.

[StefanJ]

Removing the KDE definitions for the effected user sounded like a darn sensible solution.

I didn't get around to trying it out until this weekend.

There seems to be a whole rat's nest under the name .kde* in the user's home directory.

The most logical culprit, .kderc, didn't seem to have much in it.

Any other suggestions on where to look?

Thanks

Stefan

[daneel971]

Backup the following and try to remove them:
~/.local
~/.kde/config/kickerrc
~/.kde/share/apps/kicker

Restore then one at a time and see what happen.
Sometimes, to refresh the KDE menu you need to open kmenuedit and save the active configuration.