Bug 375464 - The edit is not bieng saved
Summary: The edit is not bieng saved
Status: RESOLVED DUPLICATE of bug 322968
Alias: None
Product: kmenuedit
Classification: Applications
Component: general (show other bugs)
Version: 5.8.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-23 18:13 UTC by Akshaya D N
Modified: 2019-02-15 14:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Akshaya D N 2017-01-23 18:13:24 UTC
I can't save anything in kmenuedit application. Tried creating a new item and then a new sub menu but it doesn't appear on the menu after saving. 
I'm using Opensuse Leap 42.2
Comment 1 Burkhard Lück 2017-01-24 12:56:49 UTC
Confirmed using:
Ubuntu 16.04.1 LTS
kmenuedit Version 5.8.4
KDE Frameworks 5.28.0
Qt 5.6.1 (kompiliert gegen 5.6.1)
Das xcb Fenstersystem
Comment 2 Burkhard Lück 2017-01-24 14:09:33 UTC
Re-checked again in System from Comment 1 and in a VM with up to date neon devedition gitunstable and read the Handbook of KMenuEdit on docs.kde.org, where the issue with Items without command is mentioned:
 
1) An Item needs Name + Command to be displayed and saved, otherwise these changes are lost even if KMenuEdit ask to save the changes and you confirm.

2) A submenu needs at least one valid Item (with Name and Command) to be displayed, but is saved also without a valid item

2) Submenus are always saved also without a valid Item in their tree

3) A toplevel Submenu with a valid Item (with Name+Command) is only displayed using the Application Launcher on the page Applications; but not using the Application Menu

4) A valid toplevel Item (with Name+Command) is never diplayed, neither in  Application Launcher nor in Application Menu

Do you have this behavior in your Opensuse Leap 42.2 as well?
Comment 3 Patrick Silva 2019-02-15 14:35:51 UTC

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