The android application crashes at startup. Reproducible: Always Actual Results: $ android Exception in thread "main" java.lang.UnsatisfiedLinkError: org.eclipse.swt.internal.gtk.OS._g_thread_init(J)V at org.eclipse.swt.internal.gtk.OS._g_thread_init(Native Method) at org.eclipse.swt.internal.gtk.OS.g_thread_init(Unknown Source) at org.eclipse.swt.widgets.Display.createDisplay(Unknown Source) at org.eclipse.swt.widgets.Display.create(Unknown Source) at org.eclipse.swt.graphics.Device.<init>(Unknown Source) at org.eclipse.swt.widgets.Display.<init>(Unknown Source) at org.eclipse.swt.widgets.Display.<init>(Unknown Source) at org.eclipse.swt.widgets.Display.getDefault(Unknown Source) at org.eclipse.swt.widgets.Shell.<init>(Unknown Source) at org.eclipse.swt.widgets.Shell.<init>(Unknown Source) at com.android.sdkuilib.internal.repository.ui.SdkUpdaterWindowImpl2.createShell(SdkUpdaterWindowImpl2.java:168) at com.android.sdkuilib.internal.repository.ui.SdkUpdaterWindowImpl2.open(SdkUpdaterWindowImpl2.java:137) at com.android.sdkuilib.repository.SdkUpdaterWindow.open(SdkUpdaterWindow.java:111) at com.android.sdkmanager.Main.showSdkManagerWindow(Main.java:356) at com.android.sdkmanager.Main.doAction(Main.java:334) at com.android.sdkmanager.Main.run(Main.java:120) at com.android.sdkmanager.Main.main(Main.java:103)
Created attachment 350542 [details] emerge --info
Please post your `emerge -vpq dev-util/android-sdk-update-manager' output in a comment.
(In reply to Jeroen Roovers from comment #2) > Please post your `emerge -vpq dev-util/android-sdk-update-manager' output in > a comment. [ebuild R ] dev-util/android-sdk-update-manager-22.0.1
What version of SWT is installed? Did it get updated recently?
Same problem for me, just installed from ~amd64 portage, swt is 4.2-r2 built with all available USE-flags.
Update: downgraded swt to 3.7.2 and the manager comes up again.
Thanks - a few things could have gone wrong - I suspect I can figure it out (not the first time something like this has happened on this package).
Interesting - looks like it works with swt 4.2-r1 but not 4.2-r2. I'll confer with the swt maintainers. Downgrading swt will certainly fix the issue. So will installing 3.7 on the side and manually editing /etc/env.d/80android-sdk-update-manager to point to it as a workaround.
*** This bug has been marked as a duplicate of bug 470840 ***