Bug 229665

Summary:	kmenuedit messes up the menu structure
Product:	[Applications] kmenuedit	Reporter:	Pit <P.Suetterlin>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	annma, nzlbob2332
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Pit 2010-03-06 11:39:29 UTC

Version:           0.8 Using KDE Development Platform 4.4.1 (KDE 4.4.1) "release 225" (using KDE 4.4.1)
OS:                Linux
Installed from:    openSUSE RPMs

I try to set up nested menus using kmenuedit.  However, I do have several severe problems:
 - When I try to move a complete submenu to another tree leaf using drag and drop it seems to work.  Click 'save', close menu editor, check the menu: nothing happened.  Reopen menueditor: It's back at the old location
 - try the same using 'cut' and 'paste'.  kmenuedit shows the intended layout.  Close it, reopen it:  The submenu is still at the old location with the old name, but empty.  At the new location there is a menu, with '-1' (or -2) attached to the name original name, with the menu entries.

No matter what you change:  The menu applets in the panel might show the change - or not.  I did not really find a systematics there.  And, the two menu systems (icon/tab based and old menu based) not neccessarily agree in what they show.

Comment 1 Stephen Dunn 2010-03-08 07:10:19 UTC

Duplicate of https://bugs.kde.org/show_bug.cgi?id=227836 ?

Comment 2 Pit 2010-03-08 10:29:40 UTC

Hmm, definitely related (I didn't find that one when cheking the list of possibly related bugs).
For me kmenuedit itself behaves fine, it's updating and then showing the intended layout.
I checked the xml file ~/.config/menus/applications-kmenuedit.menu and it had a lot of <Move> and <Deleted> entries.

Comment 3 Anne-Marie Mahfouf 2010-03-20 15:02:15 UTC

Tracked in 227836

I proposed a patch for the moving of folders in a location when there is not the same named folder.

Moving a "More" folder to a location when there is already a "More" folder is broken as it appends a -2 to the folder "More-2" instead of merging.

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