Bug 285084

Summary:	No Clipboard in NEdit when Klipper is running
Product:	[Unmaintained] klipper	Reporter:	Wonko <wonko>
Component:	general	Assignee:	Esben Mose Hansen <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adaptee
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Wonko 2011-10-27 11:05:44 UTC

Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

When using the NEdit text editor, I can no longer use the copy/paste
feature when in KDE. It is working again when I quit Klipper.


Reproducible: Always

Steps to Reproduce:
Just try using the Clipboard inside NEdit when Klipper is running.

Actual Results:  
Neither the keyboard shortcuts (both Ctrl-C/V and Ctrl/Shift-Insert) nor the Edit menu has an effect. Klipper does not show stuff I copied in NEdit.

Expected Results:  
Klipper should not disable NEdit's clipboard.

This has been working fine with 4.7.1. I have been away for some weeks from my desktop PC, running NEdit remotely in an NX session without KDE, and updated the system from remote. So I suspect the KDE upgrade to 4.7.2 is the cause for this.

I also re-installed openmotif 2.3.3 due to a libpng upgrade in that time,
but when I start NEdit from a backup as
'LD_LIBRARY_PATH=/weird/usr/lib /backup/usr/bin/nedit' , it also does not
work, so I guess that's not the problem.
There also was an X upgrade.

BTW, Klipper is version 0.9.7, but this is not available in the Application Version dropdown list.

Comment 1 Jekyll Wu 2011-11-06 23:29:40 UTC

I did observed this problem when using KDE 4.7.2, but it seems gone after upgrading to KDE 4.7.3 .

Comment 2 Wonko 2011-11-07 03:33:31 UTC

I'm also using 4.7.3 now, but the bug still happens.

Comment 3 Jekyll Wu 2011-11-07 22:38:15 UTC

Well, it seems this problem is a old problem.

https://bugs.launchpad.net/ubuntu/+source/lesstif2/+bug/74518
http://bugs.kde.org/show_bug.cgi?id=129994

Comment 4 Jekyll Wu 2011-12-14 12:57:48 UTC


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