Bug 279193 - kickoff application menu dosn't support (up/down) keyboard navigation
Summary: kickoff application menu dosn't support (up/down) keyboard navigation
Status: RESOLVED DUPLICATE of bug 276932
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-kickoff (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 17:59 UTC by shani
Modified: 2011-08-08 22:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description shani 2011-08-02 17:59:27 UTC
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

i open the kickoff menu with a keyboard shortcut hit right arrow to go to application menu. and then up and down arrows are non responsive(means marker not responding like in KDE 4.6.5).
further more th ESC. key used to go one level up in the menu ... it dosn't. it closes the menu entirely. 
the keyboard default setting may have change. but i wasn't informed :) 
if i am doing somthing that can be done another way please let me know



Reproducible: Always

Steps to Reproduce:
log in. launch kickoff

Actual Results:  
application menu not responding to keyboard arrows up and down and ESC. key closes the menu

Expected Results:  
marker moving up and down with arrow keys and ESC. key goes one level up in the menu.

machine and software details
ditro: kubuntu 11.10 - the problem started prior to oneiric alpha installation
KDE 4.7.0
machine: vaio vgn120p dual-core 1.8Ghz - not that it matters
display driver: intel 945
Comment 1 Freddy Vejen 2011-08-07 16:15:03 UTC
Same behaviour in KDE 4.7.0 on Arch Linux.
In the lists on the tabs Favorites, Computer, Recently Used and Leave it is possible to navigate with the up and down arrows, but in the list on the tab Applications the up and down arrows are ignored.
Comment 2 Christoph Feck 2011-08-08 22:46:23 UTC

*** This bug has been marked as a duplicate of bug 276932 ***