Bug 472758 – dev-util/android-sdk-update-manager-22.0.1 - android: Exception in thread "main" java.lang.UnsatisfiedLinkError: org.eclipse.swt.internal.gtk.OS._g_thread_init(J)V

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Krzysztof Magusiak 2013-06-09 16:38:38 UTC]

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)

[Comment 1 Krzysztof Magusiak 2013-06-09 16:50:46 UTC]

Created attachment 350542 [details]
emerge --info

[Comment 2 Jeroen Roovers (RETIRED) 2013-06-09 16:59:54 UTC]

Please post your `emerge -vpq dev-util/android-sdk-update-manager' output in a comment.

[Comment 3 Krzysztof Magusiak 2013-06-09 17:56:14 UTC]

(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

[Comment 4 Richard Freeman 2013-06-10 00:15:54 UTC]

What version of SWT is installed?  Did it get updated recently?

[Comment 5 avx 2013-06-10 11:10:15 UTC]

Same problem for me, just installed from ~amd64 portage, swt is 4.2-r2 built with all available USE-flags.

[Comment 6 avx 2013-06-10 11:17:24 UTC]

Update: downgraded swt to 3.7.2 and the manager comes up again.

[Comment 7 Richard Freeman 2013-06-10 11:42:42 UTC]

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).

[Comment 8 Richard Freeman 2013-06-10 12:50:10 UTC]

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.

[Comment 9 Richard Freeman 2013-06-10 12:57:49 UTC]

*** This bug has been marked as a duplicate of bug 470840 ***