It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,862

question asked: Nov 11 '09, 9:13 a.m.
question was seen: 9,869 times
last updated: Nov 11 '09, 9:13 a.m.

Related questions

Rational Team Concert 2.0.1 on Ubuntu 9.10

0
Sergey Vasilenko (11●1) | asked Nov 11 '09, 9:13 a.m.
Hi there!
Recently I've upgraded my OS to 9.10 and faced a problem of working with Team Concert. Some controls are invisible and some lead to error (for example if I open history tab for some work item).
Here are the contents of .log file located in workspace's .metadata folder 

!ENTRY org.eclipse.ui 4 0 2009-11-11 16:10:56.244

!MESSAGE Unhandled event loop exception

!STACK 0

org.eclipse.swt.SWTError: XPCOM error -2147467262

	at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:1638)

	at org.eclipse.swt.browser.Mozilla.setText(Mozilla.java:1861)

	at org.eclipse.swt.browser.Browser.setText(Browser.java:737)

	at com.ibm.team.jface.itemview.ItemViewer.refresh(ItemViewer.java:1036)

	at com.ibm.team.jface.itemview.ItemViewer.setSorter(ItemViewer.java:256)

	at com.ibm.team.workitem.ide.ui.internal.editor.presentations.HistoryPart.createContent(HistoryPart.java:230)

	at com.ibm.team.ui.editor.TeamFormPart.createContent(TeamFormPart.java:61)

	at com.ibm.team.ui.editor.TeamFormSectionPart.createPartContent(TeamFormSectionPart.java:94)

	at com.ibm.team.ui.editor.TeamFormSectionPart.createPartContents(TeamFormSectionPart.java:84)

	at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemTeamFormSectionPart.createContent(WorkItemTeamFormSectionPart.java:43)

	at com.ibm.team.ui.editor.TeamFormSectionPart.init(TeamFormSectionPart.java:57)

	at com.ibm.team.ui.editor.TeamFormSectionPart.<init>(TeamFormSectionPart.java:45)

	at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemTeamFormSectionPart.<init>(WorkItemTeamFormSectionPart.java:32)

	at com.ibm.team.workitem.ide.ui.internal.editor.presentations.WorkItemEditorSections.createSection(WorkItemEditorSections.java:101)

	at com.ibm.team.workitem.ide.ui.internal.editor.presentations.WorkItemEditorSections.createSection(WorkItemEditorSections.java:111)

	at com.ibm.team.workitem.ide.ui.internal.editor.HistoryTab.createFormContent(HistoryTab.java:70)

	at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:151)

	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

	at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:149)

	at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:488)

	at com.ibm.team.ui.editor.TeamFormEditor.pageChange(TeamFormEditor.java:203)

	at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:266)

	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)

	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)

	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182)

	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1167)

	at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1007)

	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3242)

	at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2017)

	at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:320)

	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)

	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)

	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)

	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)

	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)

	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)

	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)

	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)

	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)

	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)

	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)

	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:386)

	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:79)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

	at java.lang.reflect.Method.invoke(Method.java:618)

	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)

	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)

	at org.eclipse.equinox.launcher.Main.run(Main.java:1236)



!ENTRY org.eclipse.ui.console 4 2 2009-11-11 16:11:04.249

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.console".

!STACK 0

org.eclipse.swt.SWTException: Device is disposed

	at org.eclipse.swt.SWT.error(SWT.java:3777)

	at org.eclipse.swt.SWT.error(SWT.java:3695)

	at org.eclipse.swt.SWT.error(SWT.java:3666)

	at org.eclipse.swt.widgets.Display.error(Display.java:1142)

	at org.eclipse.swt.widgets.Display.asyncExec(Display.java:665)

	at org.eclipse.ui.internal.console.ConsoleDropDownAction.consolesRemoved(ConsoleDropDownAction.java:150)

	at org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.run(ConsoleManager.java:154)

	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)

	at org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.notify(ConsoleManager.java:174)

	at org.eclipse.ui.internal.console.ConsoleManager.fireUpdate(ConsoleManager.java:262)

	at org.eclipse.ui.internal.console.ConsoleManager.removeConsoles(ConsoleManager.java:244)

	at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeProcess(ProcessConsoleManager.java:98)

	at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeLaunch(ProcessConsoleManager.java:81)

	at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.shutdown(ProcessConsoleManager.java:198)

	at org.eclipse.debug.internal.ui.DebugUIPlugin.stop(DebugUIPlugin.java:388)

	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(BundleContextImpl.java:1050)

	at java.security.AccessController.doPrivileged(AccessController.java:246)

	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:1046)

	at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:457)

	at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:531)

	at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)

	at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:655)

	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:312)

	at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257)

	at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236)

	at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678)

	at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576)

	at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:424)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

	at java.lang.reflect.Method.invoke(Method.java:618)

	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)

	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)

	at org.eclipse.equinox.launcher.Main.run(Main.java:1236)



!ENTRY org.eclipse.ui.console 4 120 2009-11-11 16:11:04.251

!MESSAGE An exception occurred during console notification

!STACK 0

org.eclipse.swt.SWTException: Device is disposed

	at org.eclipse.swt.SWT.error(SWT.java:3777)

	at org.eclipse.swt.SWT.error(SWT.java:3695)

	at org.eclipse.swt.SWT.error(SWT.java:3666)

	at org.eclipse.swt.widgets.Display.error(Display.java:1142)

	at org.eclipse.swt.widgets.Display.asyncExec(Display.java:665)

	at org.eclipse.ui.internal.console.ConsoleDropDownAction.consolesRemoved(ConsoleDropDownAction.java:150)

	at org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.run(ConsoleManager.java:154)

	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)

	at org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.notify(ConsoleManager.java:174)

	at org.eclipse.ui.internal.console.ConsoleManager.fireUpdate(ConsoleManager.java:262)

	at org.eclipse.ui.internal.console.ConsoleManager.removeConsoles(ConsoleManager.java:244)

	at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeProcess(ProcessConsoleManager.java:98)

	at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeLaunch(ProcessConsoleManager.java:81)

	at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.shutdown(ProcessConsoleManager.java:198)

	at org.eclipse.debug.internal.ui.DebugUIPlugin.stop(DebugUIPlugin.java:388)

	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(BundleContextImpl.java:1050)

	at java.security.AccessController.doPrivileged(AccessController.java:246)

	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:1046)

	at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:457)

	at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:531)

	at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)

	at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:655)

	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:312)

	at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257)

	at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236)

	at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678)

	at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576)

	at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:424)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

	at java.lang.reflect.Method.invoke(Method.java:618)

	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)

	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)

	at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

6 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Tim Mok (6.6k●3●8) | answered Nov 11 '09, 11:19 a.m.
JAZZ DEVELOPER
Can you check the version of GTK you're using?

Ubuntu 9.10 might have upgraded the version of GTK to 2.18 and there are issues with buttons not displaying correctly.

Try this workaround:
http://blog.export.be/2009/10/fixing-eclipse-for-ubuntu-karmic-koala-9-10/

Or you can downgrade to an older GTK. I believe 2.16 should work and was the version used in Ubuntu 9.04.
0
permanent link
Clemens Drews (6) | answered Nov 11 '09, 3:02 p.m.
I also use Ubuntu 9.10. I tried the workaround setting the environment variable GDK_NATIVE_WINDOWS without success.

Is there any other way that downgrading gtk to make this work?
Are you aware of an ubuntu package that allows downgrading to an older version of GTK.


Regards
-Clemens

P.S.:
Here's the stack dump I get:
============== SNIP ===============
~/jazz/client/eclipse$ export GDK_NATIVE_WINDOWS=1
~/jazz/client/eclipse$ ./eclipse
Exception in thread "Thread-8" org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Display.error(Display.java:1142)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4012)
at org.eclipse.platform.internal.EclipseRSSViewer$NewsFeed.run(EclipseRSSViewer.java:98)
at java.lang.Thread.run(Thread.java:810)
Exception in thread "Thread-12" org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Display.error(Display.java:1142)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4012)
at com.ibm.ccl.welcome.bits.rss.RSSViewer$NewsFeed.run(RSSViewer.java:363)
at java.lang.Thread.run(Thread.java:810)
Exception in thread "Thread-13" org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Display.error(Display.java:1142)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4012)
at com.ibm.ccl.welcome.bits.rss.RSSViewer$NewsFeed.run(RSSViewer.java:363)
at java.lang.Thread.run(Thread.java:810)
============== SNIP ===============

Can you check the version of GTK you're using?

Ubuntu 9.10 might have upgraded the version of GTK to 2.18 and there are issues with buttons not displaying correctly.

Try this workaround:
http://blog.export.be/2009/10/fixing-eclipse-for-ubuntu-karmic-koala-9-10/

Or you can downgrade to an older GTK. I believe 2.16 should work and was the version used in Ubuntu 9.04.
0
permanent link
Sergey Vasilenko (11●1) | answered Nov 12 '09, 4:07 a.m.
Can you check the version of GTK you're using?

Ubuntu 9.10 might have upgraded the version of GTK to 2.18 and there are issues with buttons not displaying correctly.

Try this workaround:
http://blog.export.be/2009/10/fixing-eclipse-for-ubuntu-karmic-koala-9-10/

Or you can downgrade to an older GTK. I believe 2.16 should work and was the version used in Ubuntu 9.04.


The workaround did help me to see invisible buttons =) but when I open history of some work item or some sort of Plan editor -> team concert crashes.
0
permanent link
Michael Valenta (3.7k●3) | answered Nov 12 '09, 10:23 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
I've been told that the latest Eclipse milestone has fixes for the GTK
issues. One thing you could try is installing RTC into Eclipse 3.6 M3.
You can get Eclipse 3.6 M3 from
http://download.eclipse.org/eclipse/downloads/. The instructions for
installing RTC into Eclipse 3.5 are at
http://jazz.net/wiki/bin/view/Main/InstallRTC20IntoEclipse35 and the
same instructions apply for 3.6. I must warn you, however, that 3.6M3 is
a pre-release milestone of Eclipse. I have been using it myself and
haven't encountered any problems but your mileage may vary.

Michael

Oldman wrote:
tmokwrote:
Can you check the version of GTK you're using?
Ubuntu 9.10 might have upgraded the version of GTK to 2.18 and there
are issues with buttons not displaying correctly.
Try this workaround:

http://blog.export.be/2009/10/fixing-eclipse-for-ubuntu-karmic-koala-9-10/
Or you can downgrade to an older GTK. I believe 2.16 should work and
was the version used in Ubuntu 9.04.

The workaround did help me to see invisible buttons =) but when I open
history of some work item or some sort of Plan editor team concert
crashes.
0
permanent link
Dr. Hans-Joachim Pross (1.1k●44●58) | answered Jan 15 '10, 4:20 a.m.
JAZZ DEVELOPER
Is the problem caused by an "old" eclipse, which is used in RTC?
If yes, are there plans to use the "newer" eclipse?

BTW: The easiest work around is to modify the start icon for RTC. Extend the command by "env GDK_NATIVE_WINDOWS=1 " that it looks like 
env GDK_NATIVE_WINDOWS=1 /home/hajo/IBM/TeamConcert/eclipse -product com.ibm.team.concert.product
0
permanent link
Sergey Vasilenko (11●1) | answered Jan 25 '10, 7:01 a.m.
Is the problem caused by an "old" eclipse, which is used in RTC?
If yes, are there plans to use the "newer" eclipse?

BTW: The easiest work around is to modify the start icon for RTC. Extend the command by "env GDK_NATIVE_WINDOWS=1 " that it looks like 
env GDK_NATIVE_WINDOWS=1 /home/hajo/IBM/TeamConcert/eclipse -product com.ibm.team.concert.product


Thanks a lot. works like magic

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.