Community
Participate
Working Groups
Build Identifier: 20110916-0149 Strange bug. Only appears in Eclipse, has been seen in every Eclipse variant I've tried, from SpringSource Tool Suite 32 and 64 bit editions, v2.8 and 2.7, and in Eclipse Indigo 64 bit. To reproduce (in my environment): Open any text file in eclipse or create a new text file. Type some text. Copy some text. Use CTRL-V to paste. The text is pasted twice. Using Edit->Paste or ALT+E+P does a single paste. Also, CTRL-Z may be double-undoing. No other applications (Textpad, etc) exhibit this behavior. SoapUI, which I believe is java-based, does not exhibit the behavior. Also: SHIFT+INSERT only single-pastes as well. So it appears to be the CTRL-based shortcuts. Reproducible: Always Steps to Reproduce: 1. Open eclipse or eclipse-based IDE in Windows 7 64-bit 2. Create text file, type some text, CTRL-C or copy it 3. Paste text using CTRL-V and it double-pastes.
Fascinating, ever since I did the SHIFT-INSERT, CTRL-V single-pastes.
Or maybe when I opened Soap UI it started behaving normally... will try closing IDE and reopening. Perhaps the compatibility layer in Windows 7 64 got "taught" something.
I closed down an IDE, reopened one (a Springsource Tool Suite one), and it wasn't doing it, then a popup from Cisco Security Agent told me I was violating blah blah blah, and now it is double-pasting again. But there was a very minor window. SHIFT-INSERT did not fix CTRL-V, I'll try opening SOAPUI. No, copy-pasting there did not do the temporary fix. Anyway, aside from the two minutes it wasn't double-pasting the double-pasting has been occurring for the entire time I've had Win7-64. I have been running the app as administrator. I have local administrator rights. Since the Cisco security agent may be the problem, I am running V6.0.2.1.138 Also, there is Symantic Endpoint Protection running.
I'm about 90% certain this is the Cisco Security Agent causing the double-paste problems.
I and other people on my dev team are experiencing this issue as well. When I first launch eclipse, I have about 20 seconds of normal behavior, and then all CTRL based hot-keys begin to fire twice. It's EXTREMELY annoying and disruptive of flow. We are also running Cisco Security Agent (and Symantec Endpoint Protection), and I'm pretty sure that's the problem, although when I watch the cisco log, I can't find any event that corresponds specifically to the moment when the problem starts. I doubt this bug is really eclipse's, and I blame Cisco -- but obviously the company requires us to run it. So if anyone has a workaround or solution, I would love to know.
(In reply to comment #5) > I and other people on my dev team are experiencing this issue as well. When Could you run a session with key debugging turned on and attach the output here? http://wiki.eclipse.org/Platform_Command_Framework#Tracing_Option Probably with a trace file like: org.eclipse.ui/debug=true org.eclipse.ui/trace/keyBindings=true org.eclipse.ui/trace/keyBindings.verbose=true org.eclipse.ui/trace/sources=true org.eclipse.ui/trace/handlers=true org.eclipse.ui/trace/handlers.verbose=true org.eclipse.ui/trace/handlers.verbose.commandId=org.eclipse.ui.edit.copy org.eclipse.ui/trace/contexts=true When the double paste happens, note what is in the log file output. Maybe we can learn what eclipse thinks the system is doing. PW
Created attachment 220281 [details] debug log from an eclipse session exhibiting the problem
This is wierd: As soon as I tried to get a debug log of the issue, I was no longer able to reproduce it. I have since removed the debug.options and restarted my machine, and I can't get it to misbehave anymore. I have no idea why -- great news for me, but bad news for understanding the issue. The attachment I just added is a log that one of my teammates created. He is still having the problem.
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. If the bug is still relevant, please remove the stalebug whiteboard tag.
