Home » Eclipse Projects » Eclipse Platform » Cannot launch application on some Linux machine after upgrade to eclipse 3.5
Cannot launch application on some Linux machine after upgrade to eclipse 3.5 [message #487042] |
Mon, 21 September 2009 15:59 |
Hongying Messages: 11 Registered: July 2009 |
Junior Member |
|
|
Hello,
After upgrade our product to eclipse 3.5, we run into problem
on some Linux machines (We do have different Linux set ups due to
customers have various Linux machine setup).
The Linux machine we run into problem has following setting:
SUSE 10 SP2
nVidia Quadro graphic card and matching graphic driver
Here is the problem we have:
If use jre 1.5.0_11, we cannot launch our product at all.
If use jre 1.6.0_10, we were able to start application, how ever, when
we try to launch a dialog, we will get following error:
Xlib: sequence lost …….
Xlib: sequence lost …….
... ...
Xlib: unexpected async reply ( sequence 0x3c695)!
And after the error, the product freezes. Look at log file, I am seeing
following output:
org.eclipse.swt.internal.gtk.OS._gdk_window_clear_area(OS.ja va:-2)
org.eclipse.swt.internal.gtk.OS.gdk_window_clear_area(OS.jav a:4606)
org.eclipse.swt.widgets.Tree.rendererRenderProc(Tree.java:25 80)
org.eclipse.swt.widgets.Display.rendererRenderProc(Display.j ava:1305)
org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(OS.java:- 2)
org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:75 86)
org.eclipse.swt.widgets.Display.eventProc(Display.java:1185)
org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(OS .java:-2)
org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS. java:1858)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3110)
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2405)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:493)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
myApplication.runApplication(null:-1)
myApplication.start(null:-1)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAcc essorImpl.java:-2)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
org.eclipse.equinox.launcher.Main.run(Main.java:1311)
org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Thread[AWT-EventQueue-0,6,main]/java.awt.EventDispatchThread [Alive]
com.sun.java.swing.plaf.gtk.GTKNativeEngine.nativeFinishPain ting(GTKNativeEngine.java:-2)
com.sun.java.swing.plaf.gtk.GTKNativeEngine.finishPainting(G TKNativeEngine.java:494)
com.sun.java.swing.plaf.gtk.GTKPainter.paintButtonBackground Impl(GTKPainter.java:348)
com.sun.java.swing.plaf.gtk.GTKPainter.paintButtonBackground (GTKPainter.java:253)
javax.swing.plaf.synth.SynthButtonUI.paintBackground(SynthBu ttonUI.java:233)
javax.swing.plaf.synth.SynthButtonUI.update(SynthButtonUI.ja va:205)
javax.swing.JComponent.paintComponent(JComponent.java:763)
javax.swing.JComponent.paint(JComponent.java:1027)
javax.swing.JComponent.paintChildren(JComponent.java:864)
javax.swing.JComponent.paint(JComponent.java:1036)
javax.swing.JComponent.paintChildren(JComponent.java:864)
javax.swing.JComponent.paint(JComponent.java:1036)
javax.swing.JComponent.paintChildren(JComponent.java:864)
javax.swing.JComponent.paint(JComponent.java:1036)
javax.swing.JComponent.paintChildren(JComponent.java:864)
javax.swing.JComponent.paint(JComponent.java:1036)
javax.swing.JComponent.paintChildren(JComponent.java:864)
javax.swing.JComponent.paint(JComponent.java:1036)
javax.swing.JComponent.paintChildren(JComponent.java:864)
javax.swing.JComponent.paint(JComponent.java:1036)
javax.swing.JLayeredPane.paint(JLayeredPane.java:564)
javax.swing.JComponent.paintChildren(JComponent.java:864)
javax.swing.JComponent.paintToOffscreen(JComponent.java:5129 )
javax.swing.BufferStrategyPaintManager.paint(BufferStrategyP aintManager.java:277)
javax.swing.RepaintManager.paint(RepaintManager.java:1217)
javax.swing.JComponent.paint(JComponent.java:1013)
java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback .java:21)
sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallb ack.java:60)
sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallbac k.java:97)
java.awt.Container.paint(Container.java:1762)
javax.swing.RepaintManager.paintDirtyRegions(RepaintManager. java:814)
javax.swing.RepaintManager.paintDirtyRegions(RepaintManager. java:714)
javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManag er.java:694)
javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.r un(SystemEventQueueUtilities.java:128)
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java :209)
java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis patchThread.java:269)
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:184)
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:178)
java.awt.Dialog$1.run(Dialog.java:1047)
java.awt.Dialog$3.run(Dialog.java:1099)
java.security.AccessController.doPrivileged(AccessController .java:-2)
java.awt.Dialog.show(Dialog.java:1097)
java.awt.Component.show(Component.java:1447)
java.awt.Component.setVisible(Component.java:1400)
java.awt.Window.setVisible(Window.java:824)
java.awt.Dialog.setVisible(Dialog.java:987)
myDialog.setVisible(null:-1)
myDialog.run(null:-1)
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java :209)
java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis patchThread.java:269)
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:184)
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDis patchThread.java:174)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread. java:169)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread. java:161)
java.awt.EventDispatchThread.run(EventDispatchThread.java:12 2)
Thread[Worker-3,5,main]/org.eclipse.core.internal.jobs.Worke r [Alive]
java.awt.Component.enable(Component.java:1274)
javax.swing.JComponent.enable(JComponent.java:3563)
java.awt.Component.enable(Component.java:1298)
java.awt.Component.setEnabled(Component.java:1263)
javax.swing.JComponent.setEnabled(JComponent.java:2647)
myAppJob.run(null:-1)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Please help me. I am stuck here, tried all the work around I can find,
but no luck. I appreciate any help or hint.
Thanks,
Hongying
|
|
|
Re: Cannot launch application on some Linux machine after upgrade to eclipse 3.5 [message #487219 is a reply to message #487042] |
Tue, 22 September 2009 13:45 |
Grant Gayed Messages: 2150 Registered: July 2009 |
Senior Member |
|
|
Hi,
I see awt and swing in your output log, so I assume you're running an RCP
app. I haven't heard of problems at gdk_window_clear_area() before. Are
there other Linux machines that your app does work on? Can you provide a
code snippet that shows the problem, based on the dialog that hangs for you?
Grant
"Hongying Zhang" <hongying.zhang@ugs.com> wrote in message
news:h987su$j59$1@build.eclipse.org...
> Hello,
> After upgrade our product to eclipse 3.5, we run into problem
> on some Linux machines (We do have different Linux set ups due to
> customers have various Linux machine setup).
>
> The Linux machine we run into problem has following setting:
> SUSE 10 SP2
> nVidia Quadro graphic card and matching graphic driver
>
> Here is the problem we have:
> If use jre 1.5.0_11, we cannot launch our product at all.
> If use jre 1.6.0_10, we were able to start application, how ever, when
> we try to launch a dialog, we will get following error:
> Xlib: sequence lost
|
|
|
Re: Cannot launch application on some Linux machine after upgrade to eclipse 3.5 [message #487282 is a reply to message #487219] |
Tue, 22 September 2009 16:27 |
Hongying Messages: 11 Registered: July 2009 |
Junior Member |
|
|
Grant,
Yep, We are running an RCP application. We do have some Linux machines
that our RCP application runs good. We compared the Linux machines, the
differences are:
The Linux machine RCP app runs good has following setup: KDE GUI, nVidia
Quadro graphic card (FX 1400) and matching graphic driver
The Linux machine RCP app doesn't run has following setup: GNOME GUI,
nVidia Quadro graphic card (FX 550) and matching graphic driver
Our application runs good on both machine (eclipse 3.3) before upgrade
to eclipse 3.5
I will try to provide a snippet that can reproduce the issue.
Thanks,
Hongying
Grant Gayed wrote:
> Hi,
>
> I see awt and swing in your output log, so I assume you're running an RCP
> app. I haven't heard of problems at gdk_window_clear_area() before. Are
> there other Linux machines that your app does work on? Can you provide a
> code snippet that shows the problem, based on the dialog that hangs for you?
>
> Grant
>
>
> "Hongying Zhang" <hongying.zhang@ugs.com> wrote in message
> news:h987su$j59$1@build.eclipse.org...
>> Hello,
>> After upgrade our product to eclipse 3.5, we run into problem
>> on some Linux machines (We do have different Linux set ups due to
>> customers have various Linux machine setup).
>>
>> The Linux machine we run into problem has following setting:
>> SUSE 10 SP2
>> nVidia Quadro graphic card and matching graphic driver
>>
>> Here is the problem we have:
>> If use jre 1.5.0_11, we cannot launch our product at all.
>> If use jre 1.6.0_10, we were able to start application, how ever, when
>> we try to launch a dialog, we will get following error:
>> Xlib: sequence lost …….
>> Xlib: sequence lost …….
>> ... ...
>> Xlib: unexpected async reply ( sequence 0x3c695)!
>>
>> And after the error, the product freezes. Look at log file, I am seeing
>> following output:
>> org.eclipse.swt.internal.gtk.OS._gdk_window_clear_area(OS.ja va:-2)
>> org.eclipse.swt.internal.gtk.OS.gdk_window_clear_area(OS.jav a:4606)
>> org.eclipse.swt.widgets.Tree.rendererRenderProc(Tree.java:25 80)
>> org.eclipse.swt.widgets.Display.rendererRenderProc(Display.j ava:1305)
>> org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(OS.java:- 2)
>> org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:75 86)
>> org.eclipse.swt.widgets.Display.eventProc(Display.java:1185)
>> org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(OS .java:-2)
>> org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS. java:1858)
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3110)
>> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2405)
>> org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
>> org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
>> org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
>>
>>
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
>>
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:493)
>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
>> myApplication.runApplication(null:-1)
>> myApplication.start(null:-1)
>>
>>
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:
> 194)
>>
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(
> EclipseAppLauncher.java:110)
>>
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAp
> pLauncher.java:79)
>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAcc essorImpl.java:-
> 2)
>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
> )
>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
> .java:25)
>> java.lang.reflect.Method.invoke(Method.java:597)
>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>> org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>> org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>> org.eclipse.equinox.launcher.Main.main(Main.java:1287)
>> Thread[AWT-EventQueue-0,6,main]/java.awt.EventDispatchThread [Alive]
>>
>>
> com.sun.java.swing.plaf.gtk.GTKNativeEngine.nativeFinishPain ting(GTKNativeEn
> gine.java:-2)
>>
> com.sun.java.swing.plaf.gtk.GTKNativeEngine.finishPainting(G TKNativeEngine.j
> ava:494)
>>
> com.sun.java.swing.plaf.gtk.GTKPainter.paintButtonBackground Impl(GTKPainter.
> java:348)
>>
> com.sun.java.swing.plaf.gtk.GTKPainter.paintButtonBackground (GTKPainter.java
> :253)
>>
> javax.swing.plaf.synth.SynthButtonUI.paintBackground(SynthBu ttonUI.java:233)
>> javax.swing.plaf.synth.SynthButtonUI.update(SynthButtonUI.ja va:205)
>> javax.swing.JComponent.paintComponent(JComponent.java:763)
>> javax.swing.JComponent.paint(JComponent.java:1027)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JLayeredPane.paint(JLayeredPane.java:564)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paintToOffscreen(JComponent.java:5129 )
>>
>>
> javax.swing.BufferStrategyPaintManager.paint(BufferStrategyP aintManager.java
> :277)
>> javax.swing.RepaintManager.paint(RepaintManager.java:1217)
>> javax.swing.JComponent.paint(JComponent.java:1013)
>> java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback .java:21)
>>
> sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallb ack.java:60)
>> sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallbac k.java:97)
>> java.awt.Container.paint(Container.java:1762)
>> javax.swing.RepaintManager.paintDirtyRegions(RepaintManager. java:814)
>> javax.swing.RepaintManager.paintDirtyRegions(RepaintManager. java:714)
>>
> javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManag er.java:694)
>>
> javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.r un(SystemEventQu
> eueUtilities.java:128)
>> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java :209)
>> java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
>>
>>
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis patchThread.java
> :269)
>>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:18
> 4)
>>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:17
> 8)
>> java.awt.Dialog$1.run(Dialog.java:1047)
>> java.awt.Dialog$3.run(Dialog.java:1099)
>> java.security.AccessController.doPrivileged(AccessController .java:-2)
>> java.awt.Dialog.show(Dialog.java:1097)
>> java.awt.Component.show(Component.java:1447)
>> java.awt.Component.setVisible(Component.java:1400)
>> java.awt.Window.setVisible(Window.java:824)
>> java.awt.Dialog.setVisible(Dialog.java:987)
>> myDialog.setVisible(null:-1)
>> myDialog.run(null:-1)
>> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java :209)
>> java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
>>
>>
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis patchThread.java
> :269)
>>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:18
> 4)
>>
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDis patchThread.java
> :174)
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread. java:169)
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread. java:161)
>> java.awt.EventDispatchThread.run(EventDispatchThread.java:12 2)
>> Thread[Worker-3,5,main]/org.eclipse.core.internal.jobs.Worke r [Alive]
>> java.awt.Component.enable(Component.java:1274)
>> javax.swing.JComponent.enable(JComponent.java:3563)
>> java.awt.Component.enable(Component.java:1298)
>> java.awt.Component.setEnabled(Component.java:1263)
>> javax.swing.JComponent.setEnabled(JComponent.java:2647)
>> myAppJob.run(null:-1)
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>>
>> Please help me. I am stuck here, tried all the work around I can find,
>> but no luck. I appreciate any help or hint.
>>
>> Thanks,
>> Hongying
>>
>
>
|
|
|
Re: Cannot launch application on some Linux machine after upgrade to eclipse 3.5 [message #487349 is a reply to message #487219] |
Tue, 22 September 2009 20:00 |
Hongying Messages: 11 Registered: July 2009 |
Junior Member |
|
|
Grant,
Thanks for reply. Yep, We are running an RCP application, and we do have
some Linux machines that our RCP application runs good. We compared the
Linux machines, the differences are:
The Linux machine RCP app runs good has following setup: KDE GUI, nVidia
Quadro graphic card (FX 1400) and matching graphic driver
The Linux machine RCP app doesn't run has following setup: GNOME GUI,
nVidia Quadro graphic card (FX 550) and matching graphic driver
Our application runs good on both machine (eclipse 3.3) before upgrade
to eclipse 3.5
I will try to provide a snippet that can reproduce the issue.
Thanks,
Hongying
Grant Gayed wrote:
> Hi,
>
> I see awt and swing in your output log, so I assume you're running an RCP
> app. I haven't heard of problems at gdk_window_clear_area() before. Are
> there other Linux machines that your app does work on? Can you provide a
> code snippet that shows the problem, based on the dialog that hangs for you?
>
> Grant
>
>
> "Hongying Zhang" <hongying.zhang@ugs.com> wrote in message
> news:h987su$j59$1@build.eclipse.org...
>> Hello,
>> After upgrade our product to eclipse 3.5, we run into problem
>> on some Linux machines (We do have different Linux set ups due to
>> customers have various Linux machine setup).
>>
>> The Linux machine we run into problem has following setting:
>> SUSE 10 SP2
>> nVidia Quadro graphic card and matching graphic driver
>>
>> Here is the problem we have:
>> If use jre 1.5.0_11, we cannot launch our product at all.
>> If use jre 1.6.0_10, we were able to start application, how ever, when
>> we try to launch a dialog, we will get following error:
>> Xlib: sequence lost …….
>> Xlib: sequence lost …….
>> ... ...
>> Xlib: unexpected async reply ( sequence 0x3c695)!
>>
>> And after the error, the product freezes. Look at log file, I am seeing
>> following output:
>> org.eclipse.swt.internal.gtk.OS._gdk_window_clear_area(OS.ja va:-2)
>> org.eclipse.swt.internal.gtk.OS.gdk_window_clear_area(OS.jav a:4606)
>> org.eclipse.swt.widgets.Tree.rendererRenderProc(Tree.java:25 80)
>> org.eclipse.swt.widgets.Display.rendererRenderProc(Display.j ava:1305)
>> org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(OS.java:- 2)
>> org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:75 86)
>> org.eclipse.swt.widgets.Display.eventProc(Display.java:1185)
>> org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(OS .java:-2)
>> org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS. java:1858)
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3110)
>> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2405)
>> org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
>> org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
>> org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
>>
>>
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
>>
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:493)
>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
>> myApplication.runApplication(null:-1)
>> myApplication.start(null:-1)
>>
>>
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:
> 194)
>>
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(
> EclipseAppLauncher.java:110)
>>
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAp
> pLauncher.java:79)
>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAcc essorImpl.java:-
> 2)
>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
> )
>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
> .java:25)
>> java.lang.reflect.Method.invoke(Method.java:597)
>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>> org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>> org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>> org.eclipse.equinox.launcher.Main.main(Main.java:1287)
>> Thread[AWT-EventQueue-0,6,main]/java.awt.EventDispatchThread [Alive]
>>
>>
> com.sun.java.swing.plaf.gtk.GTKNativeEngine.nativeFinishPain ting(GTKNativeEn
> gine.java:-2)
>>
> com.sun.java.swing.plaf.gtk.GTKNativeEngine.finishPainting(G TKNativeEngine.j
> ava:494)
>>
> com.sun.java.swing.plaf.gtk.GTKPainter.paintButtonBackground Impl(GTKPainter.
> java:348)
>>
> com.sun.java.swing.plaf.gtk.GTKPainter.paintButtonBackground (GTKPainter.java
> :253)
>>
> javax.swing.plaf.synth.SynthButtonUI.paintBackground(SynthBu ttonUI.java:233)
>> javax.swing.plaf.synth.SynthButtonUI.update(SynthButtonUI.ja va:205)
>> javax.swing.JComponent.paintComponent(JComponent.java:763)
>> javax.swing.JComponent.paint(JComponent.java:1027)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paint(JComponent.java:1036)
>> javax.swing.JLayeredPane.paint(JLayeredPane.java:564)
>> javax.swing.JComponent.paintChildren(JComponent.java:864)
>> javax.swing.JComponent.paintToOffscreen(JComponent.java:5129 )
>>
>>
> javax.swing.BufferStrategyPaintManager.paint(BufferStrategyP aintManager.java
> :277)
>> javax.swing.RepaintManager.paint(RepaintManager.java:1217)
>> javax.swing.JComponent.paint(JComponent.java:1013)
>> java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback .java:21)
>>
> sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallb ack.java:60)
>> sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallbac k.java:97)
>> java.awt.Container.paint(Container.java:1762)
>> javax.swing.RepaintManager.paintDirtyRegions(RepaintManager. java:814)
>> javax.swing.RepaintManager.paintDirtyRegions(RepaintManager. java:714)
>>
> javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManag er.java:694)
>>
> javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.r un(SystemEventQu
> eueUtilities.java:128)
>> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java :209)
>> java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
>>
>>
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis patchThread.java
> :269)
>>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:18
> 4)
>>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:17
> 8)
>> java.awt.Dialog$1.run(Dialog.java:1047)
>> java.awt.Dialog$3.run(Dialog.java:1099)
>> java.security.AccessController.doPrivileged(AccessController .java:-2)
>> java.awt.Dialog.show(Dialog.java:1097)
>> java.awt.Component.show(Component.java:1447)
>> java.awt.Component.setVisible(Component.java:1400)
>> java.awt.Window.setVisible(Window.java:824)
>> java.awt.Dialog.setVisible(Dialog.java:987)
>> myDialog.setVisible(null:-1)
>> myDialog.run(null:-1)
>> java.awt.event.InvocationEvent.dispatch(InvocationEvent.java :209)
>> java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
>>
>>
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis patchThread.java
> :269)
>>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat chThread.java:18
> 4)
>>
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDis patchThread.java
> :174)
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread. java:169)
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread. java:161)
>> java.awt.EventDispatchThread.run(EventDispatchThread.java:12 2)
>> Thread[Worker-3,5,main]/org.eclipse.core.internal.jobs.Worke r [Alive]
>> java.awt.Component.enable(Component.java:1274)
>> javax.swing.JComponent.enable(JComponent.java:3563)
>> java.awt.Component.enable(Component.java:1298)
>> java.awt.Component.setEnabled(Component.java:1263)
>> javax.swing.JComponent.setEnabled(JComponent.java:2647)
>> myAppJob.run(null:-1)
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>>
>> Please help me. I am stuck here, tried all the work around I can find,
>> but no luck. I appreciate any help or hint.
>>
>> Thanks,
>> Hongying
>>
>
>
|
|
|
Re: Cannot launch application on some Linux machine after upgrade to eclipse 3.5 [message #487507 is a reply to message #487349] |
Wed, 23 September 2009 13:21 |
Grant Gayed Messages: 2150 Registered: July 2009 |
Senior Member |
|
|
Also possibly relevant, which GTK+ versions and/or linux distros are on the
working and non-working linux machines?
Grant
"Hongying Zhang" <hongying.zhang@ugs.com> wrote in message
news:h9bacj$ef5$1@build.eclipse.org...
> Grant,
>
> Thanks for reply. Yep, We are running an RCP application, and we do have
> some Linux machines that our RCP application runs good. We compared the
> Linux machines, the differences are:
> The Linux machine RCP app runs good has following setup: KDE GUI, nVidia
> Quadro graphic card (FX 1400) and matching graphic driver
>
> The Linux machine RCP app doesn't run has following setup: GNOME GUI,
> nVidia Quadro graphic card (FX 550) and matching graphic driver
>
> Our application runs good on both machine (eclipse 3.3) before upgrade
> to eclipse 3.5
>
> I will try to provide a snippet that can reproduce the issue.
>
> Thanks,
> Hongying
>
> Grant Gayed wrote:
> > Hi,
> >
> > I see awt and swing in your output log, so I assume you're running an
RCP
> > app. I haven't heard of problems at gdk_window_clear_area() before.
Are
> > there other Linux machines that your app does work on? Can you provide
a
> > code snippet that shows the problem, based on the dialog that hangs for
you?
> >
> > Grant
> >
> >
> > "Hongying Zhang" <hongying.zhang@ugs.com> wrote in message
> > news:h987su$j59$1@build.eclipse.org...
> >> Hello,
> >> After upgrade our product to eclipse 3.5, we run into problem
> >> on some Linux machines (We do have different Linux set ups due to
> >> customers have various Linux machine setup).
> >>
> >> The Linux machine we run into problem has following setting:
> >> SUSE 10 SP2
> >> nVidia Quadro graphic card and matching graphic driver
> >>
> >> Here is the problem we have:
> >> If use jre 1.5.0_11, we cannot launch our product at all.
> >> If use jre 1.6.0_10, we were able to start application, how ever, when
> >> we try to launch a dialog, we will get following error:
> >> Xlib: sequence lost
|
|
|
Goto Forum:
Current Time: Tue Mar 19 02:27:40 GMT 2024
Powered by FUDForum. Page generated in 0.02971 seconds
|