| Summary: | Davinci resolve no menu bar or global menu | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kded-appmenu | Reporter: | Otis Root <otis> |
| Component: | menu exporter | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | evorster, nate |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Example of observed result when application menus daemon is enabled
Example of when applications menu daemon is not running Snapshot of the menu location |
||
Created attachment 149223 [details]
Example of when applications menu daemon is not running
To clarify - this is a solution to the issue but not the ideal solution as it breaks menu bars in all other apps
Yes, this is an issue, and there is a need to be able to disable the appmenu daemon for specific applications. Here is an interesting Reddit Post: https://www.reddit.com/r/kde/comments/vs62i0/comment/if3u9hn/?utm_source=reddit&utm_medium=web2x&context=3 Putting this into action for my pain point which is OBS studio under Wayland, I wrote this little script: ``` [evert@Evert scripts]$ cat obs_script #!/bin/bash qdbus org.kde.kded5 /kded org.kde.kded5.loadModule "appmenu" obs & qdbus org.kde.kded5 /kded org.kde.kded5.unloadModule "appmenu" ``` I made the script executable with chmod a+x [script_name] Then I edit the application in the start menu to point to the script rather than the application. For Davinci something similar might do the trick. Obviously, having to hack together scripts is less than ideal. A proper fix would be to be able to enable the appmenu daemon for certain applications through the UI. The logical place for this would have to be the "More Actions" menu that you get when right-clicking on an open application's icon in it's titlebar. (The name for which escapes me now) I'll attach a screenshot. Created attachment 160616 [details]
Snapshot of the menu location
This is where it would make the most sense to put a per-application exception for the global menu daemon.
My script needed a little tweaking. Here is one that works properly: ------------------- #!/bin/bash qdbus org.kde.kded5 /kded org.kde.kded5.unloadModule "appmenu"; obs wait 5; qdbus org.kde.kded5 /kded org.kde.kded5.loadModule "appmenu"; ---------------------- This is a bug in the specific apps. They should either be exporting their menus properly, or else not doing it at all and displaying in-window menus. |
Created attachment 149222 [details] Example of observed result when application menus daemon is enabled SUMMARY When opening davinci resolve, there is no menu bar (file, edit, etc) and it does not show up on the KDE global menu widget either. Disabling "Application menus daemon" in Background Services makes a menu bar show up in the davinci resolve menu, but then breaks menu bars for other apps. STEPS TO REPRODUCE 1. Configure global menus+enable the application menus daemon and start it 2. Install and run davinci resolve for linux (I use version 17 from the AUR - davinci-resolve) 3. Open a sample project OBSERVED RESULT There is no menu bar for davinci resolve EXPECTED RESULT There is a menu bar for davinci resolve (either in the global menu or in the app menu) SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Note that in the attachments, the black space at the very top of the screenshot represents where there should be a global menu.