Bug 69579

Summary:	[Clipboard] Ctrl-X (Cut) doesn't cut, copies instead
Product:	[Eclipse Project] Platform	Reporter:	Heiko Selber <wadenwickel>
Component:	SWT	Assignee:	Kevin Barnes <cocoakevin>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	steve_northover
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Heiko Selber

2004-07-08 04:53:48 EDT

Sometimes, the "cut" command (i.e. Ctrl-X or Menu->Cut) stops working 
correctly:

The marked text is copied to the clipboard, but is not deleted.

In other words: "cut" becomes "copy".

This affects only Eclipse, no other programs. In Eclipse, it affects at least 
Java and plain text editing.

I cannot reproduce this behavior, but it generally occurs after using Eclipse 
for some hours.

When it occurs, it remains "active" until I close and restart Eclipse.

This bug is not a duplicate of bug # 39207, which shows the same symptoms, but 
occurs only on 2-processor machines.

Besides Eclipse I use several of the usual MS Windows/Office applications.

PS: I believe that I might have reported this bug already a while ago, but I 
was unable to find it in Bugzilla. Apologies if it is a duplicate.

Comment 1 Veronika Irvine

2004-08-31 15:57:57 EDT

I believe this is fixed by the fix for bug 70077.  Please retry in Eclipse 
3.0.1 M20040901 or later.  Closing for now.  Please reopen if problem 
continues to occur.

Comment 2 Heiko Selber

2004-09-13 09:24:33 EDT

Sorry to say, but the bug persists in 3.0.1.

(Honestly, I am a bit confused by the eclipse version numbering scheme: You 
suggested to try 3.0.1 M20040901. I downloaded eclipse-SDK-M3.0.1RC1-
win32.zip, whose about box shows "Version: 3.0.1 Build id: 200409010800". I 
guess these are the same versions.)

Comment 3 Eclipse Webmaster

2019-09-06 16:18:34 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.