Problems with the SDK using Ubuntu 10.04 64 bit

by Joshua LÁúČckers » Wed, 14 Apr 2010 03:03:42 GMT

Sponsored Links
 I have downloaded the SDK and installed the necessary plugins for
Eclipse to start developing Android applications.
Whenever I try to start the ddms I get the following error(s):

18:57 E/ddms: shutting down due to uncaught exception
18:57 E/ddms: java.lang.UnsatisfiedLinkError: no swt-gtk-3550 or swt-
gtk in swt.library.path, java.library.path or the jar file
        at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
        at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
        at org.eclipse.swt.internal.C.<clinit>(Unknown Source)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
        at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source)

I am using the open jdk and I already installed the package libswt-
Does anyone know how to solve this problem?


Other Threads

1. Finalizing a Cursor that has not been deactivated or closed non-fatal error

Hello all,

i'm getting a "Finalizing a Cursor that has not been deactivated or
closed" error on this piece of code.
The code is used to fill a listview.
Since it's a non-fatal error , there is no crash and all works
fine..but i don't like a error.

If i close the cursor at the end of this code..the listview stay's
if i close the cursor in onStop , i get the same error.

How do i fix this??

private void updateList() {
        DBAdapter db = new DBAdapter(this);;
            //load all waiting alarm
            setListAdapter(new MyCursorAdapter(this, mCursor));

error :

E/Cursor  ( 2318): Finalizing a Cursor that has not been deactivated
or closed. database = /data/data/xxxxxxxxxxxxxxx.db, table = alerts,
query = SELECT _id, alert_id,
E/Cursor  ( 2318):
android.database.sqlite.DatabaseObjectNotClosedException: Application
did not close the cursor or database
object that was opened here
E/Cursor  ( 2318):      at
E/Cursor  ( 2318):      at
E/Cursor  ( 2318):      at
E/Cursor  ( 2318):      at


2. GLES/IntBuffer/?? Mis-placed verts?

so... I have a simple terrain mesh which, generally speaking, works

But as I walk around, occasionally, from some camera angles, a
triangle of that mesh is clearly being rendered incorrectly.  As if
one of its verts has moved (considerably).

But the vertex IntBuffer has not changed. (nor any of the other
buffers associated with that drawElements call)

I can change my heading and the badness will come and go at the same

If I move a bit or change heading, it will fix itself.


So same code, same data, but from some locations and some view
directions, one triangle will be messed up.  As if GLES is mis-reading
the vertex buffer (again, whose contents are calculated once and never

And I will go so far as to say it is never more than one triangle at a
time (though I can't prove that).

I can also fantasize it might be some internal math overflow dealing
with the integer coordinates (I mean the "one = 1<<16" form).

The Index buffer (a ShortBuffer) is also constant.  But mis-reading
that could also lead to wackiness.

It's.. weird.  But luckily, it's also rare.  Just disturbing to see a
hole in the terrain that ought not be there.

- Dan


3. Make entire screen disabled

4. TaskAffinity causes new instance being created when startActivity

5. App not showing in Market - 2.1, not copy protected

6. ContentProvider to Spinner results in blank, not empty, list

7. Download A file