Bug 86473

Summary:	Once a submenu is edited it can no longer be accessed
Product:	[Applications] kmenuedit	Reporter:	Taylor Sutherland <tsutherland>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	0.5
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Tar file containing .local and .config

Description Taylor Sutherland 2004-08-03 04:23:10 UTC

Version:           0.5 (using KDE 3.2.1, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.95-default

I noticed that the new version of Gaim was not showing up in the k-menu where it was supposed to go.  Once I found it, I simply dragged it and dropped it to the proper place (Internet/Chat/Gaim) and saved the menu.  Voila.  Gaim is now in it's rightful place and works flawlessly.  However, when I went to the k-menu editor to change the icon, I can no longer access the Internet/Chat/ submenu.  Clicking the little (+) symbol changes it to a (-) symbol but nothing expands.

Comment 1 Taylor Sutherland 2004-08-03 04:23:59 UTC

p.s. where is the file that the menu reads off of?  I thought it was /home/user/.kde/applnk/ but there's nothing in there.

Comment 2 Waldo Bastian 2004-08-03 12:36:14 UTC

Changes to the menu structure are stored in ~/.config/menus/applications-kmenuedit.menu

Changes to individual applications are stored under ~/.local/applications

Could you make a tarbal of your .config and .local directory and attach that to this bugreport? For example with:
     tar -czvf ~/br86473.tgz ~/.local ~/.config

What does "rpm -q kdebase3" say?

Comment 3 Jerome Haynes-Smith 2004-09-14 00:10:58 UTC

Created attachment 7516 [details]
Tar file containing .local and .config

When starting kmenuedit, only two menu options are seen under the 'work'
submenu, while six are seen in the actual menu.

$ rpm -q kdebase3
kdebase3-3.2.1-68.15

Comment 4 Waldo Bastian 2004-09-21 14:02:37 UTC


*** This bug has been marked as a duplicate of 86846 ***