Bug 269251

Summary: Mouse Actions | Right-Button not working when set to Application Launcher
Product: [Unmaintained] plasma4 Reporter: pablo <pablo>
Component: containment-desktopAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: hessijames, weldabar
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description pablo 2011-03-23 18:07:34 UTC
Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

Howdy,

If you set the `Right-Button' `Mouse-Actions' to `Application Launcher' and rt-click on the desktop, you do not get the list of applications available from Kicker.  Instead, you get a single menu item:  Desktop Settings.

On the other hand, if you set, say, Vertical-Scroll to `Application Launcher', as expected, you get the list of applications.

FYI:  I went on the #kde IRC and confirmed this is a 4.6.1 problem seen on other distros (Fedora and Arch ... along with mine:  openSUSE 11.4).

Reproducible: Always

Steps to Reproduce:
o Rt-click on default desktop and select `Desktop Settings'
o In new window, select `Mouse Actions'
o For `Right-Button', from the pull-down list to its right, select `Application Launcher'.
o Click `Apply'
o Rt-click on the desktop and notice `Application Launcher' values are not displayed.

o Return to the `Desktop Settings' window and, say, change `Middle-Button' to `Application Launcher'.  Click `Apply'
o Middle-button on the desktop and notice the `Application Launcher' works.

Actual Results:  
A single menu item is displayed:  `Desktop Settings'

Expected Results:  
The list of Applications available via Kicker should be displayed.
Comment 1 Robert Strahl 2011-06-07 20:23:45 UTC
I confirm that this bug is also present in Kubuntu 11.04.
Comment 2 Daniel Faust 2011-12-02 18:17:44 UTC
I can't reproduce it with KDE 4.7.2, please reopen if the problem still exists.
Comment 3 pablo 2011-12-02 18:19:08 UTC
Hi Daniel,

I'm sorry, I should have closed this bug with 4.7.x  You're right, it's now fixed.  :)