Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Standard Widget Toolkit (SWT) » Can't commit in Git because of XPCOM error -2147467262(XPCOM error -2147467259 when trying to do commit)
Can't commit in Git because of XPCOM error -2147467262 [message #719233] Fri, 26 August 2011 13:43 Go to next message
unax  is currently offline unax
Messages: 4
Registered: August 2011
Junior Member
Hello all.
Tried everything! and still can't solving this problem.
now i use Arch Linux x86_64, kernel 3.0.0, eclipse with Pydev, Aptana and JGit (1.0.0.201106090707-r)
Quote:
eclipse.buildId=M20110210-1200
java.version=1.6.0_22
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=ru_RU
Command-line arguments: -os linux -ws gtk -arch x86_64

# xulrunner -v => Mozilla XULRunner 6.0 - 20110823172340

wrote a lot variants of eclipse.ini,
tried to use many option combination, like this:
-Dorg.eclipse.swt.browser.UseWebKitGTK=true - fail
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-6.0/xulrunner - fail
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-6.0 - fail
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-5.0 - fail
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/firefox-6.0/
-Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null - fail
..and much more
tried to use OpenJDK and OracleJDK, no results Sad Every time:
org.eclipse.swt.SWTError: XPCOM error -2147467259
	at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2414)
	at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2377)
	at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:641)
	at org.eclipse.swt.browser.Browser.<init>(Browser.java:119)
	at com.aptana.git.ui.internal.actions.CommitDialog.createDiffArea(CommitDialog.java:214)
	at com.aptana.git.ui.internal.actions.CommitDialog.createDialogArea(CommitDialog.java:135)
	at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:760)
	at org.eclipse.jface.window.Window.create(Window.java:431)
	at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
	at org.eclipse.jface.dialogs.StatusDialog.create(StatusDialog.java:203)
	at com.aptana.git.ui.internal.actions.CommitDialog.create(CommitDialog.java:179)
	at org.eclipse.jface.window.Window.open(Window.java:790)
	at com.aptana.git.ui.internal.actions.CommitHandler.doExecute(CommitHandler.java:27)
	at com.aptana.git.ui.internal.actions.AbstractGitHandler.execute(AbstractGitHandler.java:94)
	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
	at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
	at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
	at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
	at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:820)
	at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:806)
	at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:796)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	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:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

I really need to solve this problem, but I see no exit.
I would be very grateful for any help
Mihail
Re: Can't commit in Git because of XPCOM error -2147467262 [message #719265 is a reply to message #719233] Fri, 26 August 2011 14:39 Go to previous messageGo to next message
Mark Fishman is currently offline Mark Fishman
Messages: 27
Registered: March 2011
Junior Member
Hi Mihail,

I have been trying to feel my way through this stuff myself. What I can tell you for sure is that the swt Browser component does not support any xulrunner versions later than the 1.9.x series. It also, obviously, has to be a 64 bit version of xulrunner to work.

As for why:

-Dorg.eclipse.swt.browser.UseWebKitGTK=true

did not work, I am less sure of that one. It does say in the SWT FAQ that WebKitGTK 1.2.0 or newer must be in the library load path for this to work. Have you checked for that?


-- Mark
Re: Can't commit in Git because of XPCOM error -2147467262 [message #719293 is a reply to message #719265] Fri, 26 August 2011 15:54 Go to previous messageGo to next message
unax  is currently offline unax
Messages: 4
Registered: August 2011
Junior Member
Thanks, Mark. Smile
Everything is clear about xulrunner, so i thought. But first! for why these all components, i just need to do the simplest operation (commit in git)
If i no set option -Dorg.eclipse.swt.browser.XULRunnerPath=* there is another error - it requires variable MOZILLA_FIVE_HOME from me.
now to WebKitGTK..
You mean h++p://www.eclipse.org/swt/faq.php#browserwebkitgtk (sorry bots protection "You cannot use links")
In my system found WebKitGTK
Quote:
# pacman -Ss WebKitGTK
extra/libwebkit 1.4.2-1 [установлен]
An opensource web content engine (for GTK2)

So what options are needed more than -Dorg.eclipse.swt.browser.UseWebKitGTK=true for error gone? How to force eclipse to use UseWebKitGTK only, I do not fully understand.
Re: Can't commit in Git because of XPCOM error -2147467262 [message #719722 is a reply to message #719293] Sun, 28 August 2011 15:53 Go to previous messageGo to next message
unax  is currently offline unax
Messages: 4
Registered: August 2011
Junior Member
problem still urgent Sad
Re: Can't commit in Git because of XPCOM error -2147467262 [message #719896 is a reply to message #719722] Mon, 29 August 2011 11:35 Go to previous messageGo to next message
Mark Fishman is currently offline Mark Fishman
Messages: 27
Registered: March 2011
Junior Member
Hi Mihail,

Yes, that was the SWT FAQ that I was mentioning.

I think that your problem is as stated in the faq at:

h++p://www.eclipse.org/swt/faq.php#browserwebkitgtk

It says:

--- clip ---

Eclipse/SWT 3.6.x can also use WebKitGTK for SWT.NONE-style Browsers created on GTK, but the user must explicitly request this by setting java property "org.eclipse.swt.browser.UseWebKitGTK" to "true". In the absence of this property being set, Mozilla is used for all SWT.NONE-style Browsers. (Note that Eclipse/SWT 3.6.x is only able to use WebKitGTK 1.2.x; it will fail if a newer WebKitGTK release is found.)

--- end clip ---

It looks like you are using 1.4.2-1. You might want to try upgrading to Eclipse 3.7 or else downgrading your webkit.

-- Mark

Re: Can't commit in Git because of XPCOM error -2147467262 [message #719948 is a reply to message #719896] Mon, 29 August 2011 14:33 Go to previous messageGo to next message
Grant Gayed is currently offline Grant Gayed
Messages: 2151
Registered: July 2009
Senior Member
Yes, this is the problem. Eclipse 3.7 should work better for this case
(and no need to specify -Dorg.eclipse.swt.browser.UseWebKitGTK with 3.7).

That being said, your GIT client's functionality should not be disabled
by failure to create a Browser control, as there are other contexts
(eg.- running on AIX or HPUX) where Browser instantiation will also
fail. You should log a report with them (I'm guessing you're using EGit
(?)) to let them know that fallback functionality should be provided for
the case of Browser instantiation failing.

Grant


On 8/29/2011 7:35 AM, mfishm1 wrote:
> Hi Mihail,
>
> Yes, that was the SWT FAQ that I was mentioning.
> I think that your problem is as stated in the faq at:
>
> h++p://www.eclipse.org/swt/faq.php#browserwebkitgtk
>
> It says:
>
> --- clip ---
>
> Eclipse/SWT 3.6.x can also use WebKitGTK for SWT.NONE-style Browsers
> created on GTK, but the user must explicitly request this by setting
> java property "org.eclipse.swt.browser.UseWebKitGTK" to "true". In the
> absence of this property being set, Mozilla is used for all
> SWT.NONE-style Browsers. (Note that Eclipse/SWT 3.6.x is only able to
> use WebKitGTK 1.2.x; it will fail if a newer WebKitGTK release is found.)
> --- end clip ---
>
> It looks like you are using 1.4.2-1. You might want to try upgrading to
> Eclipse 3.7 or else downgrading your webkit.
>
> -- Mark
>
>
Re: Can't commit in Git because of XPCOM error -2147467262 [message #720648 is a reply to message #719948] Wed, 31 August 2011 02:24 Go to previous message
unax  is currently offline unax
Messages: 4
Registered: August 2011
Junior Member
Eclipse 3.7 works!) here, it's different implemented and no problem now.
Quote:
I'm guessing you're using EGit

yes it is
Quote:
You should log a report with them to let them know that fallback functionality should be provided for the case of Browser instantiation failing.

it would be right, but they know this problem probably.
thanks all for help)
Previous Topic:set text input to overwrite/insert mode programatically
Next Topic:Bad text alignment for Label
Goto Forum:
  


Current Time: Wed Sep 17 19:48:38 GMT 2014

Powered by FUDForum. Page generated in 0.01757 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software