You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Plasma settings go Widget Style -> Fine tuning -> Menubar: Titlebar button :
Add this Application menu to window decoration: Widget Style -> Window decorations -> Buttons:
Open any KDE app, and see that menu is gone and new button appeared:
Open Visual Studio Code app, and check the menus:
Reproduces without extensions: Yes
Expected behavior:
menubar should disappear, and button should work.
Actual behaior:
Menu is still there and button do nothing.
As electron supports KDE's global menus (or at least supported to draw them in previous versions) i'd expect them to work. But since fix of the electrons high CPU usage bug, menus are not working at all in VS Code.
Reacted by Władysław Glebowicz, Kolya Ay and Luan Martins
What is the status of this issue? I would like to use the global menu with Visual Studio Code. It is working with Atom Editor and the new Electron release.
somniumAeternam strange, just installed atom (I'm on Arch Linux) and global menu didn't worked for me. What versions of atom and electrom did you use? Were you using a git build?
Checked electron itself. Same story with electron version 1.6.15 electron/electron#10532
So the global menus work for some people. Not for me, but i think that maybe something missing in my particular system. Maybe some plasma packages are missing. I don't know.
With the lastest plasma update global menu started to work in electron and all electron based applications.
Update
Ok I've run into problem that global menus worked for me on my work PC which is running archlinux, but didn't worked on my home PC which runs archlinux as well. So I've dumped my installed packages from both PCs and used diff to find missing one. It seems that installing libdbusmenu-glib (somniumAeternam please try to install/remove it and respond if possible) fixes lack of global menus in electron apps on KDE PLasma 5.12.0
If I won't run into any issue in near future i'll close this issue.
Activity
[-]KDE's menubar button does not work[/-][+][Linux] KDE's menubar button does not work[/+]somniumAeternam commentedon Dec 4, 2017
What is the status of this issue? I would like to use the global menu with Visual Studio Code. It is working with Atom Editor and the new Electron release.
andreyorst commentedon Dec 4, 2017
somniumAeternam strange, just installed atom (I'm on Arch Linux) and global menu didn't worked for me. What versions of atom and electrom did you use? Were you using a git build?
Checked electron itself. Same story with electron version 1.6.15
electron/electron#10532
somniumAeternam commentedon Dec 4, 2017
I use Atom Editor 1.22.1 x64 on openSUSE Tumbleweed with latest updates. It is also working with electron 1.7.9.
andreyorst commentedon Jan 30, 2018
So the global menus work for some people. Not for me, but i think that maybe something missing in my particular system. Maybe some plasma packages are missing. I don't know.

andreyorst commentedon Feb 12, 2018
With the lastest plasma update global menu started to work in electron and all electron based applications.
Update
Ok I've run into problem that global menus worked for me on my work PC which is running archlinux, but didn't worked on my home PC which runs archlinux as well. So I've dumped my installed packages from both PCs and used diff to find missing one. It seems that installing
libdbusmenu-glib(somniumAeternam please try to install/remove it and respond if possible) fixes lack of global menus in electron apps on KDE PLasma 5.12.0If I won't run into any issue in near future i'll close this issue.
worldofpeace commentedon Feb 19, 2018
Andrey Listopadov (@andreyorst) I can verify that installing
libdbusmenu-glibon archlinux does solve this.andreyorst commentedon Feb 20, 2018
WORLDofPEACE (@worldofpeace) awesome!
kolya-ay commentedon Feb 20, 2018
Can confirm that installing
libdbusmenu-glib4package on my Debian testing solves the issue for me. KDE Plamsa 5.10.5Tyriar commentedon Feb 20, 2018
Great that there's a workaround, it looks like an upstream issue