Bug 382962

Summary:	Doesn't load global menu initially for Google Chrome or Chromium
Product:	[Plasma] plasmashell	Reporter:	Unknown <null>
Component:	Global Menu widget	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	notuxius, null, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.10.4
Target Milestone:	1.0
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Unknown 2017-07-31 15:41:28 UTC

BEHAVIOR
When I load Google Chrome or Chromium web browsers, the global menu doesn't show any of the menu entry items. Switching to another window and then switching back to Chrome or Chromium will then show the menu items in the global menu.

EXPECTED BEHAVIOR
For the global menu options to appear in the global menu on program start, without the need to switch between another window and switch back.

BUG DISCOVERED USING
Kubuntu 17.04 x64
KDE Plasma 5.10.4 (via ppa:kubuntu-ppa/backports)
KDE Frameworks 5.36.0
Qt 5.7.1
Linux kernel 4.10.0-28-generic
Nvidia GTX 1080 graphics card
Nvidia 384.59 proprietary graphics driver

Comment 1 Kai Uwe Broulik 2017-08-01 13:17:14 UTC

Unfortunately I am not able to reproduce this. I start Chrome or Chromium and the global menu applet shows their menu right away.

Comment 2 Unknown 2017-08-02 21:02:40 UTC

Thanks for the reply, Kai. I just launched a fresh instance of Google Chrome, and the global menu didn't show the menu options. I went to another desktop and selected Dolphin (which showed the global menu), and then switched back to the desktop that had Google Chrome, and the global menu appeared.

Would taking a screencast help? Could the NVidia drivers have a part in it? (I know Plasma behaves a little differently on Nvidia's proprietary drivers vs. Nouveau's open-source drivers).

Comment 3 Alexander Mentyu 2018-01-29 15:20:18 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
Intel 4400

Comment 4 Unknown 2019-06-29 03:32:10 UTC

Confirmed that this is fixed in KDE Plasma 5.16.2