Summary: | KMenuedit no longer utilizes application directory structure | ||
---|---|---|---|
Product: | [Applications] kmenuedit | Reporter: | lnxusr |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | REPORTED --- | ||
Severity: | major | CC: | kde, nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
lnxusr
2021-10-09 01:26:42 UTC
When you say "KMenu" are you referring to Kickoff (Application Launcher) or Kicker (Application Menu) Or something else? Does it work if you restart Plasma manually with `plasmashell --replace` in a terminal window and then try to launch the app whose menu entry you edited? (In reply to Nate Graham from comment #1) > When you say "KMenu" are you referring to Kickoff (Application Launcher) or > Kicker (Application Menu) Or something else? > > Does it work if you restart Plasma manually with `plasmashell --replace` in > a terminal window and then try to launch the app whose menu entry you edited? I've tried Application Dashboard, Application Launcher, Application Menu, Excalibur Menu and Simple Menu, all three show (or don't show) the same items. Does it really matter which I meant, though? All menus should be using the same data and structure, and KMenuEdit should handle it properly and consistently. I've rebooted several times since, and the issue hasn't changed. Right yeah, so there does seem to be an issue with KMenuEdit for you. There's no issue with the menu editor. Kickoff has "flat: true" set on the model. The reporter said it reproduces with menus that aren't Kickoff, though. |