Bug 247523 - Klipper doesn't fade out after clicking history entries or anything else other than its System Tray icon
Summary: Klipper doesn't fade out after clicking history entries or anything else othe...
Status: RESOLVED DUPLICATE of bug 247348
Alias: None
Product: klipper
Classification: Applications
Component: general (show other bugs)
Version: 0.9.6
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Esben Mose Hansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-12 16:02 UTC by Leonardo La Malfa
Modified: 2010-08-13 22:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
snapshot (313.91 KB, image/png)
2010-08-12 16:02 UTC, Leonardo La Malfa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo La Malfa 2010-08-12 16:02:08 UTC
Created attachment 50064 [details]
snapshot

Version:           0.9.6 (using KDE 4.5.0) 
OS:                Linux

After upgrading to KDE 4.5, Klipper icon doesn't behave like expected anymore.

What happened before: I could hit Klipper icon in the System Tray to see the clipboard tool appear fading in and showing me various selections to pick from, along with the available options, the Help section, etc. In order to close the clipboard tool, it was enough to click on one of the history entry, to see it fading out gracefully, or one could simply click elsewhere, outside the "popup window", if nothing of interest was to be found.

What happens now: the "popup window" doesn't fade out anymore, no matter if I click on something within it, or outside it. The only way to close it is to click again on Klipper icon in the System Tray. The snapshot attached demonstrates this by showing that I filled in the entire bug report in its company ---------------------->

Reproducible: Always




OS: Linux (i686) release 2.6.32-24-generic
Compiler: cc
Comment 1 H.H. 2010-08-13 22:17:38 UTC
I think this is a duplicate of bug 247348
Comment 2 Leonardo La Malfa 2010-08-13 22:49:37 UTC
(In reply to comment #1)
> I think this is a duplicate of bug 247348

I agree.
Comment 3 Leonardo La Malfa 2010-08-13 22:51:08 UTC

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