Bug 249004 - klipper: accelerator keys prevent filtering for substring
Summary: klipper: accelerator keys prevent filtering for substring
Status: RESOLVED FIXED
Alias: None
Product: klipper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Esben Mose Hansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-25 16:25 UTC by g111
Modified: 2011-01-19 11:57 UTC (History)
6 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 g111 2010-08-25 16:25:58 UTC
Version:           unspecified (using Devel) 
OS:                Linux

I am playing around with KDE 4.5.64 (KDE 4.6 >= 20100811) and found that filtering for a string in the klipper clipboard history does no longer work. Instead you are triggering some menu items by accelerator keys.


Reproducible: Always

Steps to Reproduce:
E.g. when trying to filter the list for the string "libck"...

Actual Results:  
...klipper asks me if I really want to clear the history, because this menu item has the accel key "l".

Expected Results:  
The displayed history list should be restricted to entries that contain the typed word "libck".

Greetings,
Gert
Comment 1 ancow 2010-09-07 14:23:18 UTC
This started with the upgrade to KDE SC 4.5.0 for me. It's rather annoying and at the very least calls for an option to disable the accelerators.
Comment 2 Vedran 2010-09-17 09:02:49 UTC
To call this rather annoying is an understatement :)
The actions to reproduce this bug are accurate.

I have also made a global shortcut to the klipper dbus command showKlipperPopupMenu. When called in this way, not even the accelerators work. The popup doesn't get the focus, and keyboard presses are sent to the application that had focus prior to showing the popup. I have tried to force window stealing prevention to "none" for klipper, but this doesn't solve anything.
Comment 3 Vedran 2010-09-17 09:03:39 UTC
To call this rather annoying is an understatement :)
The actions to reproduce this bug are accurate.

I have also made a global shortcut to the klipper dbus command showKlipperPopupMenu. When called in this way, not even the accelerators work. The popup doesn't get the focus, and keyboard presses are sent to the application that had focus prior to showing the popup. I have tried to force window stealing prevention to "none" for klipper, but this doesn't solve anything.
Comment 4 Marios Andreopoulos 2010-09-28 01:05:01 UTC
Really, it seems that somehow klipper, a perfectly working program for 5 years on my computer, is destroyed with KDE 4.5.0!

I cannot invoke klipper with the KDE default ctrl+alt+v anymore and even when I access it through the tray icon, the search function does not work.

I am using Gentoo Linux and have kept my ~/.kde directory since KDE 4.1.
Comment 5 Patrick Boutilier 2010-10-10 13:32:54 UTC
Same problem in Platform Version 4.5.2 (KDE 4.5.2) on Fedora 13 (x86_64)
Comment 6 g111 2010-10-17 21:07:36 UTC
I am currently testing 4.5.72 (4.6 >= 20101012) and it seems that filtering does work again. The accelerator keys are gone now. Is this intentionally so this bug entry can be closed? Or is it by accident and it will reoccur sooner or later?

btw: Ctrl+Alt+c to start the klipper popup menu has to be configured via the systray "entries" settings.
see here: https://bugs.kde.org/show_bug.cgi?id=244620#c36
Comment 7 g111 2010-10-17 21:18:57 UTC
My last comment was not 100% correct. There are still accelerator keys present. But filtering does work again. So I am closing this entry, ok?
Comment 8 Kevin Kofler 2010-11-18 17:31:27 UTC
Well, we'd still like a fix on the 4.5 branch!
Comment 9 Sérgio Basto 2010-11-18 21:18:30 UTC
ya , why isn't apply on 4.5 branch ?
Comment 10 Roberto Ragusa 2011-01-16 18:16:02 UTC
Still broken on 4.5.5.

Please, port to fix to 4.5.

This is a huge productivity loss (I'm really used to having a very big history and do Ctrl-Alt-V and type a few letters).
Comment 11 Sérgio Basto 2011-01-19 03:02:11 UTC
yeah , this is a big regression why the fuck is not ported to stable , we have 5 minor versions, and biggest difference that I found is in help: about where it change a number.
Comment 12 g111 2011-01-19 08:20:40 UTC
I am not a developer, just a user reporting this bug. So sorry, I cannot help with this. But as KDE4.6 will be released soon, I think, it becomes more and more less important to backport this fix, doesn't it? I hope that it is really fixed in this release (before it goes to debian/sid)...
Comment 13 Roberto Ragusa 2011-01-19 11:57:08 UTC
(In reply to comment #12)
> I am not a developer, just a user reporting this bug. So sorry, I cannot help
> with this. But as KDE4.6 will be released soon, I think, it becomes more and
> more less important to backport this fix, doesn't it? I hope that it is really
> fixed in this release (before it goes to debian/sid)...

The problem is that some distributions will not update to 4.6 easily.
For example, Fedora's KDE maintainers have a (good) habit of pushing 4.x+1 even if the distro was originally shipped with 4.x, but there are people arguing that only bugfixing should be allowed in updates, and 4.6 could be considered more than a simple 4.5 bugfix.

There are distributions with stricter policies, in these cases the fix is delayed to users for many months.