Bug 353041

Summary: Menu fails to open under specific circumstances.
Product: [Plasma] plasmashell Reporter: Paul <pip.kde>
Component: Application Menu (Kicker) widgetAssignee: Eike Hein <hein>
Status: RESOLVED WORKSFORME    
Severity: normal CC: notuxius, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.4.0   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Paul 2015-09-22 14:32:25 UTC 
If an icon in "Icons-only Task Manager" is right clicked to open the context menu, and, that menu is then closed either by a left click on the desktop or by using the ESC key, and, the Application Menu icon is then left clicked; the application whose context menu was opened is launched, the Application Menu does not open.

Reproducible: Always

Steps to Reproduce:
1. Place "Application Menu" and "Icons-only Task Manager" into the panel. (as needed)
2. In that Task Manager set one or more Applications to "Show A Launcher When Not Running".
3. Right click on one of those launcher icons to open the context menu.
4. Close the context menu by left click on empty desktop space or by using the ESC key.
5. Left click the Application Menu icon to open the Application Menu.

Actual Results:  
At step [5] Instead of the Application Menu opening, the application whose context menu was opened at step [3] is launched.

Expected Results:  
At step [5] the Application Menu opens.
Comment 1 Alexander Mentyu 2017-08-28 10:43:10 UTC 
Cannot reproduce this bug in:

Distribution: KDE neon Developer Edition Unstable Branches
KDE Plasma Version: 5.10.90
KDE Frameworks Version: 5.37.0
Qt Version: 5.9.1
Kernel Version: 4.10.0-32-generic
Comment 2 Eike Hein 2017-08-28 11:10:30 UTC 
Sorry - Plasma 5.4 is two years old and will not receive bugfixes anymore.
Comment 3 Paul 2017-08-30 17:30:46 UTC 
(In reply to Eike Hein from comment #2)
> Sorry - Plasma 5.4 is two years old and will not receive bugfixes anymore.

OK :)

The bug report was two years old also. );

Now using 5.10.5, and indeed somewhere along the way from 5.4 whatever was causing that behaviour has been fixed.
Comment 4 Eike Hein 2017-08-31 08:51:46 UTC 
Aye, I didn't notice at first that Alexander was going through old tickets :).