Bug 271398 - klipper popup remains open upon keyboard selection
Summary: klipper popup remains open upon keyboard selection
Status: RESOLVED DUPLICATE of bug 258749
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-21 03:59 UTC by Joseph Reagle
Modified: 2011-11-07 11:53 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Reagle 2011-04-21 03:59:04 UTC
Version:           4.6 (using KDE 4.6.2) 
OS:                Linux

Before KDE 4.6, when I hit ctrl+alt+v, then cursored to select a entry in klipper, when I hit return, the klipper pop-up would go away. Now it stays there! I see there's a timeout option, but I'm not sure what that is for, and even when I set it to one second, the klipper popup menu stays open even after keyboard selection. (Mouse/focus policy makes no difference.)

Reproducible: Didn't try

Steps to Reproduce:
ctrl-alt-v
cursor to item
select item by hitting enter

Actual Results:  
popup remains open

Expected Results:  
popup closes and focus returns to previously focussed window.
Comment 1 Simon St James 2011-04-24 13:59:23 UTC
Confirmed here using KDE4.6.2 on Kubuntu 10.10 installed via the Kubuntu Backports PPA.  Seems to be 100% reproducible.  The requested entry is indeed set to the current selection upon pressing Enter (although the popup menu does not reflect this until manually dismissed and re-summoned), it's just that the popup menu does not go away.
Comment 2 Pistos 2011-05-29 19:48:46 UTC
Same here under Gentoo.  KDE 4.6.2, Klipper 4.6.2.  By the way, why is this bug filed under "plasma" instead of "klipper"?  Workaround is to press Enter and then Escape, but that's borderline tolerable, from a UX standpoint.
Comment 3 Jekyll Wu 2011-11-07 11:53:44 UTC

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