Bug 384530

Summary:	If a window doesn't support global menus, closing system settings won't get rid of the menus
Product:	[Plasma] plasmashell	Reporter:	Matthew Trescott <matthewtrescott>
Component:	Global Menu widget	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	kde, notuxius, plasma-bugs-null, uhhadd
Priority:	NOR
Version First Reported In:	5.10.5
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Recording of problem

Description Matthew Trescott 2017-09-09 16:27:10 UTC

Steps to reproduce:

1. Open Chrome or Firefox.
2. Open System Settings (with the browser still visible)
3. Close System Settings.
4. The menus for System Settings remain in the global menu bar.

Comment 1 Kai Uwe Broulik 2017-09-12 12:05:57 UTC

I tried with kate (KDE_NO_GLOBAL_MENU=1) and some Java application and it works fine for me. (Firefox and Chrome support global menu here)

Comment 2 David Edmundson 2017-09-12 12:09:02 UTC

Matthew, are you on X or wayland?

Comment 3 Matthew Trescott 2017-09-12 20:05:26 UTC

I am on X. Global menus don't work at all on Wayland, nor really, for me, does Plasma. Too many crashes. But Arch doesn't provide debug symbols so I can't help with that. :(

I am able to reproduce using the KDE_NO_GLOBAL_MENU=1 env variable, with kate. I'll attach a screen recording; hopefully that will help.

Comment 4 Matthew Trescott 2017-09-12 20:06:28 UTC

Created attachment 107823 [details]
Recording of problem

Comment 5 Alexander Mentyu 2018-01-29 16:19:23 UTC

Can't reproduce in:

Plasma: 5.11.5
Apps: 17.12.1
Qt: 5.10.0
Frameworks: 5.42.0
Kernel: 4.14.14-1-MANJARO

Comment 6 Janet Blackquill 2020-07-31 17:46:18 UTC

This should be fixed with the port to libtaskmanager. Please reopen if it's not.