Bug 453600 - electron-qt-apps + wayland: no working global menu (= no menus, unuseable) - needed dependecies? roadmap?
Summary: electron-qt-apps + wayland: no working global menu (= no menus, unuseable) - ...
Status: RESOLVED DUPLICATE of bug 424485
Alias: None
Product: kded-appmenu
Classification: Frameworks and Libraries
Component: menu exporter (show other bugs)
Version: 5.24.4
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-09 20:51 UTC by gonanza
Modified: 2022-08-12 08:55 UTC (History)
1 user (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 gonanza 2022-05-09 20:51:26 UTC
SUMMARY
If you start a qt-app under kde (running wayland), the apps (konsole, dolphin etc.) cant access global menu (when using sddm / kwin before, gdm3 / mutter is slightly diffent). This is independent of the graphics platform used.

The only workaround is to trick the app by using GDK_BACKEND="x11" and / or QT_QPA_PLATFORM="xcb" (= nonisolated)

1. What are the needed dependencies currently to get 'global menu' working under wayland with qt-apps (without tricking them back into x11)? 
2. What are dependencies when using 'global menu' with wayland while also using 'firejail'? under gdm3 / mutter this sems to be not a problem (because the mutter-wayland-flavor seems to be not so much 'wayland'-only currently even if you set variables strict), under sddm / kwin this produces some in part severe problems)
currently installed: appmenu-registrar, libdbusmenu-qt5-2 (as well as the gtk-flavour (lib-)appmenu-gtk-x-module, dbusmenu / gir, libayatana-appindicator-stuff)
3. If this is a bug and currently worked on: what is the roadmap. The current situation is terrible it brakes systems or produces follow-up-problems when workarounds are used.


STEPS TO REPRODUCE
1. setup sddm, kde, wayland-compatible graphics 
2. setup global menu 
3. start a qt-app (with  QT_QPA_PLATFORM="wayland",  GDK_BACKEND="wayland")

OBSERVED RESULT
no global menu entries show up (tested with intel, amd, nvidia)

EXPECTED RESULT
transfer of global menu entries

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: debian 11
(available in About System)
KDE Plasma Version:  5.24.4
KDE Frameworks Version:  5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 gonanza 2022-05-09 21:23:34 UTC
Another question would be how to activate 'global menu' in electron-based apps (brave, freetube, signal etc.) when they are started wayland only (--enable-features=UseOzonePlatform --ozone-platform=wayland --enable-features=WaylandWindowDecorations).

as well as the above: only workaround seems to be 'QT_QPA_PLATFORM="xcb"' thus destroying all wayland-benefits (as well as downgrading resolution to 1920x1080 max and rendering all texts blurry), ending again in an x11-environment.
Comment 2 gonanza 2022-05-23 21:23:16 UTC
First issue does work normally after updating again to 5.24.5 and 5.93.0 (workaround before was using gtk as QT_QPA_PLATFORMTHEME).

however second issue, electron-apps do not show the menu under wayland-only conditions (workaround is GDK_BACKEND="x11" and *not* --ozone-platform=wayland, thus making the blurry and reducing UHD to HD resolutions) as before, any plans to fix this (or any workaround to gain at least UHD-resolution)?
Comment 3 phrxmd 2022-08-12 08:55:20 UTC

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