Community
Participate
Working Groups
THe issue happen sometimes in the recently eclipse. When I try to copy some java code lines ( one line or mutiple lines), 1. Using ctrl + c and ctrl + p to do the copy paste. It not working. 2. Or using copy/ paste from the menu of right click. Still not working. 3. Cut / Paste works well. 4. copy/paste one word is ok. 5. I found a workaround by uncheck Update imports as below. I'm running Eclipse 3.5.1 in a virtual environment. And occasionally the copy/paste (either through the menu or Ctrl-C/Ctrl-V) stops working. Fortunately, I found a fix. In Window > Preferences > Java > Editor > Typing, uncheck "Update imports". Then copy/paste will work. -- Configuration Details -- Product: Eclipse 1.4.0.20110609-1120 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.jdt 3.7.0.v20110520-0800-7z8gFchFMTdFYKuLqBLqRja9B15B
> ctrl + p I guess that was a typo. So it's only paste that doesn't work? When you paste it to another application (e.g. notepad), does it work? I can't reproduce. Does it always happen for you? Can you add an example file and concrete steps to reproduce? Maybe it also has something to do with the breadcrumb (bug 347622).
Can you give more details on the "virtual environment" you are using? I'm guessing that may be at the heart of the problem.
(In reply to comment #2) > Can you give more details on the "virtual environment" you are using? I'm > guessing that may be at the heart of the problem. Sorry. I confuse you guys. The below solution is waht I find using google. The solution works for me. I am running the latest eclipse ee under Windows XP SP3, not virtual machine. Here is the link: http://www.otweb.com/phramework/pw/module/blog/?id=935 I'm running Eclipse 3.5.1 in a virtual environment. And occasionally the copy/paste (either through the menu or Ctrl-C/Ctrl-V) stops working. Fortunately, I found a fix. In Window > Preferences > Java > Editor > Typing, uncheck "Update imports". Then copy/paste will work.
(In reply to comment #1) > > ctrl + p > I guess that was a typo. > > So it's only paste that doesn't work? When you paste it to another application > (e.g. notepad), does it work? > > I can't reproduce. Does it always happen for you? Can you add an example file > and concrete steps to reproduce? > > Maybe it also has something to do with the breadcrumb (bug 347622). Thank you for your comments. 1. I will check whehter the paste it to another application work well or not later. 2. The problem does NOT always happen. It will happen some times. Such as 3, 4 time one day( 8 hours). Sometimes, restart eclipse can solve the issue, but not all the times. 3. In fact, I didn't use breadcrumb before. 4. What can I found the logs or some useful information if the issue happen again. So I can attached them to the bug.
Looks like some interaction issues with the clipboard.
(In reply to comment #5) > Looks like some interaction issues with the clipboard. Hi All, The issue happen again today when I try to copy one line code as below. String serialNumber = "004010222808"; When try to paste, nothing happen. Copy to the Java file or some txt file outside eclipse, both failed. When copy and paste to the eclipse, it will hang 1 or 2 seconds, no response, nothing else can be done. I use ctrl + c or copy from the right click menu. Both failed. But below operation successfully. 1. copy "String serialNumber " and " = "004010222808" ok. 2. copy each words of the line ok. 3. cut the line is ok. BTW, I installed the easy explorer in my eclipse ee. I will attached the .log under the .metadata. Hope it will help. Thanks. Allen
Created attachment 199082 [details] long file Logs under .metadata
> BTW, I installed the easy explorer in my eclipse ee. I will attached the .log > under the .metadata. Hope it will help. Do you still see the copy problem if you de-install the easy explorer?
(In reply to comment #8) > > BTW, I installed the easy explorer in my eclipse ee. I will attached the .log > > under the .metadata. Hope it will help. > Do you still see the copy problem if you de-install the easy explorer? I have remove the easy explorer jar from the plugin folder. but the issue still exist. I am not sure whether my de-install is complete or not?
(In reply to comment #9) > (In reply to comment #8) > > > BTW, I installed the easy explorer in my eclipse ee. I will attached the .log > > > under the .metadata. Hope it will help. > > Do you still see the copy problem if you de-install the easy explorer? > > I have remove the easy explorer jar from the plugin folder. but the issue still > exist. I am not sure whether my de-install is complete or not? Well, if the feature is not working/there anymore then uninstall worked.
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > > BTW, I installed the easy explorer in my eclipse ee. I will attached the .log > > > > under the .metadata. Hope it will help. > > > Do you still see the copy problem if you de-install the easy explorer? > > > > I have remove the easy explorer jar from the plugin folder. but the issue still > > exist. I am not sure whether my de-install is complete or not? > > Well, if the feature is not working/there anymore then uninstall worked. The feature is not there. Currently, I am using external tools to open the folder instead of easy explorer. I will update thread if the issue happen again.
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > > BTW, I installed the easy explorer in my eclipse ee. I will attached the .log > > > > under the .metadata. Hope it will help. > > > Do you still see the copy problem if you de-install the easy explorer? > > > > I have remove the easy explorer jar from the plugin folder. but the issue still > > exist. I am not sure whether my de-install is complete or not? > > Well, if the feature is not working/there anymore then uninstall worked. BTW, Is there any parameter to set to get more log of eclipse itself? Such as -debug? How? Thanks.
where are you seeing this problem: a) Eclipse 3.5.1 in a virtual environment (please describe your virtual environment) b) latest eclipse ee under Windows XP SP3 (latest eclipse ee == Eclipse 3.7 ?)
(In reply to comment #13) > where are you seeing this problem: > > a) Eclipse 3.5.1 in a virtual environment > (please describe your virtual environment) > > > b) latest eclipse ee under Windows XP SP3 > (latest eclipse ee == Eclipse 3.7 ?) 1. I am running Eclipse ee under Windows XP SP3. 2. Here is the version information. I also saw the problem in the previous eclipse. Eclipse Java EE IDE for Web Developers. Version: Indigo Release Build id: 20110615-0604 3. DO you know any parameter to make eclipse output more logs? I think that would be helpful. Thanks.
I am using a complete new eclipse ee and no other plugin installed. But the issue still there. Eclipse Java EE IDE for Web Developers. (Windows XP SP3) Version: Indigo Release Build id: 20110615-0604 ************************************** I have 2 workarounds. 1. The workaround I take is disable Update imports. Everything is ok. In Window > Preferences > Java > Editor > Typing, uncheck "Update imports". Then copy/paste will work. 2. Use cut(ctrl + x ) instead of ctrl +c, which is a little stupid. ************************************** So I think the issue it related to "Update imports". I may need to use older version of eclipse ee in future.
Here are some log from error log. Hope it helps. java.lang.NullPointerException at org.eclipse.jdt.internal.codeassist.SelectionEngine.selectFrom(SelectionEngine.java:1127) at org.eclipse.jdt.internal.codeassist.SelectionEngine.select(SelectionEngine.java:944) at org.eclipse.jdt.internal.core.Openable.codeSelect(Openable.java:162) at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:377) at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:371) at org.eclipse.jdt.internal.ui.javaeditor.JavaElementHyperlinkDetector.detectHyperlinks(JavaElementHyperlinkDetector.java:84) at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:286) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:258) at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:462) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:211) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) eclipse.buildId=I20110613-1736 java.version=1.6.0_26 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
The NPE stack trace does not look like coming from Copy. Are you sure it's related? Can you reproduce the NPE? If so, can you provide a test snippet?
(In reply to comment #17) > The NPE stack trace does not look like coming from Copy. Are you sure it's > related? Can you reproduce the NPE? If so, can you provide a test snippet? Here is the java file I use. import java.text.DateFormat; import java.text.SimpleDateFormat; import java.util.Date; import java.util.TimeZone; public class GMTtoCST { public static void main(String args[]) throws Exception { Date date = new Date(1273622935*1000l); DateFormat cstFormat = new SimpleDateFormat("yyyyMMddHHmmss"); DateFormat gmtFormat = new SimpleDateFormat("yyyyMMddHHmmss"); TimeZone gmtTime = TimeZone.getTimeZone("GMT"); TimeZone cstTime = TimeZone.getTimeZone("CST"); System.out.println(date); gmtFormat.setTimeZone(gmtTime); cstFormat.setTimeZone(cstTime); System.out.println("GMT Time: " + gmtFormat.format(date)); System.out.println("CST Time: " + cstFormat.format(date)); System.out.println("GMT Time: " + gmtFormat.parse("20100512075855")); System.out.println("CST Time: " + cstFormat.parse("20100512075855")); Date dd = gmtFormat.parse("20100512075855"); String str="can copy...."; System.out.println(gmtFormat.format(dd)); System.out.println(cstFormat.format(dd)); } }
(In reply to comment #18) > (In reply to comment #17) > > The NPE stack trace does not look like coming from Copy. Are you sure it's > > related? Can you reproduce the NPE? If so, can you provide a test snippet? > > Here is the java file I use. > > import java.text.DateFormat; > import java.text.SimpleDateFormat; > import java.util.Date; > import java.util.TimeZone; > > public class GMTtoCST { > public static void main(String args[]) throws Exception { > Date date = new Date(1273622935*1000l); > DateFormat cstFormat = new SimpleDateFormat("yyyyMMddHHmmss"); > DateFormat gmtFormat = new SimpleDateFormat("yyyyMMddHHmmss"); > TimeZone gmtTime = TimeZone.getTimeZone("GMT"); > TimeZone cstTime = TimeZone.getTimeZone("CST"); > > System.out.println(date); > > gmtFormat.setTimeZone(gmtTime); > cstFormat.setTimeZone(cstTime); > > System.out.println("GMT Time: " + gmtFormat.format(date)); > > System.out.println("CST Time: " + cstFormat.format(date)); > > System.out.println("GMT Time: " + gmtFormat.parse("20100512075855")); > System.out.println("CST Time: " + cstFormat.parse("20100512075855")); > > Date dd = gmtFormat.parse("20100512075855"); > String str="can copy...."; > > System.out.println(gmtFormat.format(dd)); > System.out.println(cstFormat.format(dd)); > > } > } I can't copy and paste lines such as " Date dd = gmtFormat.parse("20100512075855");" or " String str="can copy...."; ". But after uncheck Update imports, I can copy and paste.
(In reply to comment #19) I can neither reproduce the NPE nor the Copy problem with that snippet. Can you reproduce the NPE with it? Do you use a tool that interacts with the clipboard, e.g. keeps the clipboard history?
The NPE is tracked by bug 343260 but I don't think it is related to the Copy issue.
If you always see the NPE then I think you see bug 343260. And you might run into this more often than other users because your mouse is more (or lesss) sensitive than the default (see bug 343260 comment 0 for the scenario).
(In reply to comment #21) > The NPE is tracked by bug 343260 but I don't think it is related to the Copy > issue. Yes, I agree with you.
(In reply to comment #20) > (In reply to comment #19) > I can neither reproduce the NPE nor the Copy problem with that snippet. Can you > reproduce the NPE with it? > > Do you use a tool that interacts with the clipboard, e.g. keeps the clipboard > history? No, I didn't use any tools that keeps the clipboard history. Do you have any good suggestions for debug the issue or problem as it is related to ----<<<<< "Update imports" - >>>>>>. I have the same issue as the link, but I am not running in the VM machines, I am running eclipse ee under general machines(XP SP3). http://www.otweb.com/phramework/pw/module/blog/?id=935
> Do you have any good suggestions for debug the issue or problem as it is > related to ----<<<<< "Update imports" - >>>>>>. When updating imports is selected, we directly communicate with the clipboard instead of letting StyledText do the work. If you can reproduce the problem, then the simplest thing would be to remote debug your workspace.
(In reply to comment #25) > > Do you have any good suggestions for debug the issue or problem as it is > > related to ----<<<<< "Update imports" - >>>>>>. > When updating imports is selected, we directly communicate with the clipboard > instead of letting StyledText do the work. > > If you can reproduce the problem, then the simplest thing would be to remote > debug your workspace. That sounds good. But I think remote debug my workspace is not easy thing. There may exist some network issue.
(In reply to comment #26) > (In reply to comment #25) > > > Do you have any good suggestions for debug the issue or problem as it is > > > related to ----<<<<< "Update imports" - >>>>>>. > > When updating imports is selected, we directly communicate with the clipboard > > instead of letting StyledText do the work. > > > > If you can reproduce the problem, then the simplest thing would be to remote > > debug your workspace. > > That sounds good. But I think remote debug my workspace is not easy thing. > There may exist some network issue. I think you can do that yourself. For details see http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Fconcepts%2Fcremdbug.htm. In your second instance make sure to have 'org.eclipse.jdt.ui' in your workspace and add a breakpoint to org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.doCutCopyWithImportsOperation().
(In reply to comment #27) > (In reply to comment #26) > > (In reply to comment #25) > > > > Do you have any good suggestions for debug the issue or problem as it is > > > > related to ----<<<<< "Update imports" - >>>>>>. > > > When updating imports is selected, we directly communicate with the clipboard > > > instead of letting StyledText do the work. > > > > > > If you can reproduce the problem, then the simplest thing would be to remote > > > debug your workspace. > > > > That sounds good. But I think remote debug my workspace is not easy thing. > > There may exist some network issue. > > I think you can do that yourself. For details see > http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Fconcepts%2Fcremdbug.htm. > > In your second instance make sure to have 'org.eclipse.jdt.ui' in your > workspace and add a breakpoint to > org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.doCutCopyWithImportsOperation(). Hi Dani Megert, Do you mean I use one eclipse to debug another eclipse? Is the source code of eclipse within the package or shall I build the eclipse myself? Thanks.
1. start your workspace which has the bug with the following additional VM arguments: -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n NOTE: you might have to use a different address if 14143 is already busy. 2. start another new workspace 3. File > Import... > Plug-ins and Fragments 4. import 'org.eclipse.jdt.ui' as binary project from the active target platform 5. add the breakpoint as indicated in my previous comment 6. Run > Debug Configurations... 7. create a new 'Remote Java Application' with 'localhost' as host and the port from above (14143). Also add the 'org.eclipse.jdt.ui' on the 'Source' tab 8. click 'Debug' 9. when you now do Copy (Ctrl+C) or Cut (Ctrl+X) in your buggy workspace, it should hit the breakpoint in the other one. You should now be able to track down the problem.
(In reply to comment #29) > 1. start your workspace which has the bug with the following additional VM > arguments: > -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n > NOTE: you might have to use a different address if 14143 is already busy. > 2. start another new workspace > 3. File > Import... > Plug-ins and Fragments > 4. import 'org.eclipse.jdt.ui' as binary project from the active target > platform > 5. add the breakpoint as indicated in my previous comment > 6. Run > Debug Configurations... > 7. create a new 'Remote Java Application' with 'localhost' as host and the port > from above (14143). Also add the 'org.eclipse.jdt.ui' on the 'Source' tab > 8. click 'Debug' > 9. when you now do Copy (Ctrl+C) or Cut (Ctrl+X) in your buggy workspace, it > should hit the breakpoint in the other one. > > You should now be able to track down the problem. Great. Thank you for the detail steps. I will try to track the problem later. Thanks.
(In reply to comment #29) > 1. start your workspace which has the bug with the following additional VM > arguments: > -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n > NOTE: you might have to use a different address if 14143 is already busy. > 2. start another new workspace > 3. File > Import... > Plug-ins and Fragments > 4. import 'org.eclipse.jdt.ui' as binary project from the active target > platform > 5. add the breakpoint as indicated in my previous comment > 6. Run > Debug Configurations... > 7. create a new 'Remote Java Application' with 'localhost' as host and the port > from above (14143). Also add the 'org.eclipse.jdt.ui' on the 'Source' tab > 8. click 'Debug' > 9. when you now do Copy (Ctrl+C) or Cut (Ctrl+X) in your buggy workspace, it > should hit the breakpoint in the other one. > > You should now be able to track down the problem. HI Dani Megert, I get the problem again today and try to debug using the steps you mentioned. But when i try to do the step 7 and 8, I get a message " Failed to connect to remote VM. Connection refused. Connection refused: connect" . I have try to use different port, the issue still there. What is wrong with it? Can you give me some suggestions? Thanks. java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.<init>(Unknown Source) at java.net.Socket.<init>(Unknown Source) at org.eclipse.jdi.internal.connect.SocketTransportService$2.run(SocketTransportService.java:136) at java.lang.Thread.run(Unknown Source) eclipse.buildId=I20110613-1736 java.version=1.6.0_26 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
(In reply to comment #29) > 1. start your workspace which has the bug with the following additional VM > arguments: > -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n > NOTE: you might have to use a different address if 14143 is already busy. > 2. start another new workspace > 3. File > Import... > Plug-ins and Fragments > 4. import 'org.eclipse.jdt.ui' as binary project from the active target > platform > 5. add the breakpoint as indicated in my previous comment > 6. Run > Debug Configurations... > 7. create a new 'Remote Java Application' with 'localhost' as host and the port > from above (14143). Also add the 'org.eclipse.jdt.ui' on the 'Source' tab > 8. click 'Debug' > 9. when you now do Copy (Ctrl+C) or Cut (Ctrl+X) in your buggy workspace, it > should hit the breakpoint in the other one. > > You should now be able to track down the problem. For the step1, I am updating the target property of the eclipse icon to " D:\java\eclipse\eclipse_ee1\eclipse.exe -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n " Is that right?
(In reply to comment #32) > (In reply to comment #29) > > 1. start your workspace which has the bug with the following additional VM > > arguments: > > -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n > > NOTE: you might have to use a different address if 14143 is already busy. > > 2. start another new workspace > > 3. File > Import... > Plug-ins and Fragments > > 4. import 'org.eclipse.jdt.ui' as binary project from the active target > > platform > > 5. add the breakpoint as indicated in my previous comment > > 6. Run > Debug Configurations... > > 7. create a new 'Remote Java Application' with 'localhost' as host and the port > > from above (14143). Also add the 'org.eclipse.jdt.ui' on the 'Source' tab > > 8. click 'Debug' > > 9. when you now do Copy (Ctrl+C) or Cut (Ctrl+X) in your buggy workspace, it > > should hit the breakpoint in the other one. > > > > You should now be able to track down the problem. > > For the step1, I am updating the target property of the eclipse icon to " > D:\java\eclipse\eclipse_ee1\eclipse.exe -Xdebug > -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n " Is that right? No, this is not correct. In order to pass VM arguments to eclipse.exe you need to use "-vmargs", e.g. eclipse.exe -vmargs -Xrunjdwp:server=y,transport=dt_socket,address=14143,suspend=n
Are you using VNC?
I am running under Windows Vista 64 (non virtual) using Eclipse 3.7.1 (Classic plus too many additional plugins to list here) and am currently suffering from exactly the same problem. Unchecking Organize Imports does indeed remedy the problem. I am not using breadcrumbs. The log contains no related information. Voted this bug up. Regards, Torsten
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.
