Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 95105

Summary: [DND] DBCS3.3: DBCS named file drag&drop not function
Product: [Eclipse Project] Platform Reporter: Masayuki Fuse <fuse>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: RESOLVED WONTFIX QA Contact: Kevin Barnes <cocoakevin>
Severity: normal    
Priority: P3 CC: b.muskalla, camle, duongn, eclipse.felipe, gheorghe, Karice_McIntyre, karim, kitlo, snorthov, steven.wasleski, tadayuki, veronika_irvine
Version: 3.1Keywords: triaged
Target Milestone: ---   
Hardware: Sun   
OS: Solaris-GTK   
Whiteboard:

Description Masayuki Fuse CLA 2005-05-13 07:03:18 EDT
driver : Eclipse3.1 I20050513-0010
JVM : Sun 1.4.2_07
Platform : Solaris 9 (9/2004) and Solaris 10 (3/2005)
locale : ja for Japanese, ko for Korean, zh for S Chinese, zh-TW for T Chinese

steps
1. drag a DBCS named file at Nautilus (2.0.7 on Solaris9, 2.6.1 on Solaris10)
2. drop it at a project of Eclipse Package Explorer

result
Nothing happen. No error stack. 
English named file worked fine.
Comment 1 Veronika Irvine CLA 2005-05-17 16:23:53 EDT
Fuse-san,

I am trying to reproduce this bug so I can work on a fix.  Unfortunately, our
Solaris 9 machine does not have Gnome installed on it and does not have
Nautilus.    Do you have the steps you followed to install Gnome on your Solaris
9 machine?  Did you get it from Sun or from some other site?  We have tried a
few times to install Gnome on Solaris and failed.

Thank you,
Veronika
Comment 2 Masayuki Fuse CLA 2005-05-18 00:11:24 EDT
We installed Gnome in the first Solaris installation time by the 9/2004 
Solaris 9 CDs. We could not add Gnome properly after Solaris9 installation. 
Thanks.
Comment 3 Veronika Irvine CLA 2005-05-24 13:32:57 EDT
So far I am unable to install Gnome/Nautilus on our Solaris machine.  I have
tried to recreate the problem on Linux but without success.  If I have a locale
mismatch (e.g. start nautilus with LANG-ja_JP.UTF-8 and start eclipse with
LANG=en_US.ISO8859-1), the file is copied over from Nautilus to Eclipse but it
shows up in Eclipse with the wrong characters.  File has the correct characters
in Nautilus (looked in workspace where file was dropped).

I am using Nautilus 2.8.1 on RedHat EL4.
Comment 4 Tadayuki Yoshida CLA 2006-03-07 02:44:06 EST
Problem still exists.

driver : Eclipse3.2 I20060304-0010
JVM : Sun 1.4.2_11 (sparc)
Platform : Solaris 10 sparc (1/2006)
locale : ja for Japanese, ko for Korean, zh for S Chinese, zh-TW for T Chinese

steps
1. drag a DBCS named file at Nautilus (2.6.1)
2. drop it at a project of Eclipse Package Explorer

result
Nothing happen. No error stack. 
Mouse pointer won't change even if it is over droppable area.
English named file worked fine.
Comment 5 Karim Hamzaoui CLA 2007-03-26 05:10:09 EDT
Problem still exists.

Driver: Eclipse3.3 I20070313-1051
OS: Solaris 10 11/2006 (Sparc GTK ) 
locale : ja for Japanese, ko for Korean, zh for S Chinese, zh-TW for T Chinese

steps
1. drag a DBCS named file at Nautilus (2.6.1)
2. drop it at a project of Eclipse Package Explorer

result
Nothing happen. No error stack. 
Mouse pointer does change into a cross when over a droppable area but the file is not copied.
Same problem occur when Drag&Droping a file from a path that contains DBCS folder names.
English named file worked fine.
Comment 6 Karim Hamzaoui CLA 2008-04-10 04:52:03 EDT
The problem now occurs only with non-UTF8 DBCS locales. 
It also throws the following exception:

!ENTRY org.eclipse.ui 4 0 2008-04-10 17:43:22.527
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
        at org.eclipse.swt.SWT.error(SWT.java:3766)
        at org.eclipse.swt.SWT.error(SWT.java:3684)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3323)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2985)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2375)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2339)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2205)
        at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:478)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:473)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
        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:362)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed:
        at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
        at org.eclipse.core.runtime.Assert.isTrue(Assert.java:95)
        at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
        at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
        at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
        at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:130)
        ... 22 more


Driver: Eclipse3.4 I20080405-1031
OS: Solaris 10 8/2007 (Sparc ) 
    Sun JDK 1.6.0_04-b12
locale : ja for Japanese, ko for Korean, zh for S Chinese, zh-TW for T Chinese
JDK: 

steps
1. Launch eclipse in a non-UTF8 DBCS locale (e.g. ja)
1. Drag a DBCS named file at Nautilus (2.6.1)
2. Drop it at a project of Eclipse Package Explorer

result
The file is not opened
Mouse pointer does change into a cross when over a droppable area but the file
is not copied.
Same problem occur when Drag&Droping a file from a path that contains DBCS
folder names.
English named file worked fine.
Comment 7 Steve Northover CLA 2008-04-10 10:33:01 EDT
If I am decoding the stack trace right, it seems that the original exception is being caused by org.eclipse.ui.internal.ide.EditorAreaDropAdapter.  Since we don't have the hardware and Veronika could not recreate the problem on RedHat, I'm not sure what we can do.

Can we remote into your machine?
Comment 8 Karim Hamzaoui CLA 2008-04-15 00:19:20 EDT
Sure Steve, I will setup a vnc server and send you access information when ready.
Could you first send me the Notes IDs of those who will be working on this bug? (you and Veronika I guess), I need to grant you guys access through our firewall etc.
Comment 9 Steve Northover CLA 2008-04-15 09:53:36 EDT
It will be Duong and Felipe working on this.  Duong, go ahead and send the required information.  When you can make the problem happen, let us know.
Comment 10 Duong Nguyen CLA 2008-10-21 17:38:33 EDT
Filipe, do you know if this was fixed? I thought it was?
Comment 11 Masayuki Fuse CLA 2008-10-22 01:23:45 EDT
I've just tried 3.4.1 GM on Solaris10 Nautilus 2.6.1. It worked on ja_JP.UTF-8 locale but not on ja_JP.eucJP and ja_JP.PCK non UTF-8 locales without any error.
Comment 12 Lakshmi P Shanmugam CLA 2017-06-20 02:39:25 EDT
Solaris is no longer a supported platform.