Bug 240053

Summary:	klipper popup menu should be shouwn above the panel
Product:	[Applications] klipper	Reporter:	anton <benderamp>
Component:	general	Assignee:	Esben Mose Hansen <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	adaptee, bluedzins, colin.thomson, dimsuz, m.wege, pascal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	KDE: 4.5.85 (4.6 Beta2) if panel is set to 'auto hide'.

Description anton 2010-05-30 09:31:45 UTC

Version:           unspecified
OS:                Linux

KDE 4.4.81

When click on the klipper icon in the system tray, the popup menu shown right above the bottom screen border, but not above the panel, so it hides the system tray and clipper icon I have just clicked. All other programs (kmix, knetworkmanager etc) show their popups above the panel, so in most cases I can click on the icon to show popup and click again to hide popup. For the klipper I click once to show it and with current menu layout it suggests me to quit on the second click as this menu option comes just below the mouse position.

Reproducible: Didn't try

Comment 1 Esben Mose Hansen 2010-06-06 17:33:09 UTC

must be a recent breakage in some lib or interaction, since this is not in 4.4 and klipper has seen little or no development recently.

Comment 2 Jonathan Marten 2010-06-26 10:19:49 UTC

*** Bug 241825 has been marked as a duplicate of this bug. ***

Comment 3 Colin J Thomson 2010-08-27 00:16:36 UTC

I am seeing this with KDE-4.5, it only happens when my panel is set to Auto-hide.

Comment 4 Colin J Thomson 2010-09-01 01:08:39 UTC

Updated to 4.5.1 and all seems OK now

Comment 5 Hans-Rudi Denzler 2010-12-09 17:27:37 UTC

Created attachment 54363 [details]
KDE:  4.5.85 (4.6 Beta2) if panel is set to 'auto hide'.

Right clicking klipper does nothing.

Comment 6 Jekyll Wu 2011-11-06 19:27:01 UTC

*** Bug 243229 has been marked as a duplicate of this bug. ***

Comment 7 Jekyll Wu 2011-11-09 11:42:27 UTC

*** Bug 137981 has been marked as a duplicate of this bug. ***