This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Hi, Netbeans 5.5 Build 200610171010 EP 20061020 crashes D&D support if run under JVM 1.6.0-b105. The first D&D operation emits some X11 console messages: robi@2[bin]$ ./netbeans _X11TransSocketOpen: socket() failed for local _X11TransSocketOpenCOTSClient: Unable to open socket for local _X11TransOpen: transport open failed for local/xp2006:0 Then D&D will silently not work for the entire session. Shutting down and restarting nb again reproduces the same behaviour. My solution was to revert to JVM build 1.5.0_06-b05 where everithing seems to work. This D&D problem (seen from 1.3) has been reported as Java bug 5069437 back in 2004 against Tiger and it randomly resurfaces... Please ask if I have to resubmit as JVM bug. Ciao, Roberto
Hello, you are right it's jdk bug 5069437. I added the link to this issue and reproduction information you provided. From information in related bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6451487 it seems bug may be already fixed in dolphin JDK release...
Please note that bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5069437 is not fixed. The reference above states: "We should check this as the fix for 6451487 becomes accessible. Posted Date : 2006-11-01 11:21:34.0" Related bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6451487 is closed but the problem (in Linux) still persists. The link to the JVM You edited into my initial message points to a nonexistant NB bug not to the JVM bug database and should be corrected to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5069437. Ciao, Roberto
See my last comment.
Yes, thanks for the corrected link. I know all you wrote and it's true, however it's also true that we can do nothing more with this bug, as it's not in NetBeans. So the fair process is to close as "will not fix" (in NetBeans, because we can't) and link the issue to real JDK problem, as the fix will come from JDK side.
v/c