Bug 11587

Summary:	Eclipse break when use completition
Product:	Mageia	Reporter:	Filipe Saraiva <mail>
Component:	RPM Packages	Assignee:	D Morgan <dmorganec>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	gpmpublic, pterjan
Version:	Cauldron	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	eclipse-platform-4.3.1-5.mga4	CVE:
Status comment:
Attachments:	My eclipse.ini

Description Filipe Saraiva 2013-11-02 22:53:47 CET

Hello, My Eclipse installation is breaking when I use completition.

I change the eclipse.ini in /usr/lib64/eclipse/eclipse.ini and now it is working fine.

I added the follow line:

-Dorg.eclipse.swt.browser.DefaultType=mozilla

Before the line:

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

in eclipse.ini.

Thanks.

Reproducible: 

Steps to Reproduce:

Comment 1 Filipe Saraiva 2013-11-02 22:55:22 CET

Created attachment 4470 [details]
My eclipse.ini

My eclipse.ini from /usr/lib64/eclipse/eclipse.ini, change by add the line -Dorg.eclipse.swt.browser.DefaultType=mozilla

Manuel Hiebel 2013-11-03 00:00:14 CET

Keywords: (none) => Triaged
Assignee: bugsquad => dmorganec

Comment 2 D Morgan 2014-01-07 14:34:51 CET

we disabled xulrunner support in eclipse for webkit. so i don't think this is a good idea to use -Dorg.eclipse.swt.browser.DefaultType=mozilla

Comment 3 Filipe Saraiva 2014-01-19 20:32:13 CET

Hi dmorgan,

Today I tested my eclipse without the line -Dorg.eclipse.swt.browser.DefaultType=mozilla but eclipse broken many times.

When I put the previous line, it don't break anymore.

Does not eclipse break with you?

Thanks.

Comment 4 Gilles Mauroy 2014-02-13 18:39:06 CET

Same problem here with fresh Mageia 4 install and external Eclipse Kepler.

Same workaround too: -Dorg.eclipse.swt.browser.DefaultType=mozilla added to eclipse.ini.

Following are some other references re. what I suspect is the same problem referencing an issue with Google Talk plugins -- others have uninstalled it to fix the same symptom:

http://stackoverflow.com/questions/7959491/birt-preview-crashes-in-eclipse-designer-on-linux

http://stackoverflow.com/questions/21134508/eclipse-crash-on-fedora-20

CC: (none) => gpmpublic

Comment 5 Gilles Mauroy 2014-02-13 18:39:47 CET

Note everything else being the same, I did not have this problem with Mageia 3.

Comment 6 Pascal Terjan 2014-02-13 23:58:39 CET

I don't have the problem here, but hard to know what is different :(

Reading your links it seems it could be due to a plugin, do you have any installed?

[pterjan@chopin ~]$ rpm -qa | grep -i eclipse
icu4j-eclipse-50.1.1-3.mga4
eclipse-swt-4.3.1-8.mga4
eclipse-jdt-4.3.1-8.mga4
eclipse-platform-4.3.1-8.mga4
eclipse-pde-4.3.1-8.mga4
eclipse-ecf-core-3.6.1-2.mga4
eclipse-equinox-osgi-4.3.1-8.mga4
eclipse-emf-core-2.9.1-2.mga4

CC: (none) => pterjan

Comment 7 Pascal Terjan 2014-02-17 11:16:27 CET

I tried more over the week-end, on another Mageia 4 installation, and still fail to reproduce (I have google talk plugin installed on both machines).

Comment 8 Pascal Terjan 2014-02-17 22:59:17 CET

[000:000] Cpu: 6.42.7, x4, 3092Mhz, 14018MB
[000:000] Computer model: Not available
[000:000] Browser XEmbed support present: 1
[000:000] Browser toolkit is Gtk2.
[000:000] Using Gtk2 toolkit
No bp log location saved, using default.
[000:000] Cpu: 6.42.7, x4, 3092Mhz, 14018MB
[000:000] Computer model: Not available
java version "1.7.0_45"
OpenJDK Runtime Environment (mageia-2.4.4.2.mga4-x86_64 u45-b15)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)

I am not getting any "DEBUG: NP_Initialize" that other people report on their bug and which would mean it loads some browser plugins.

Do you?

Comment 9 Filipe Saraiva 2014-02-18 01:58:43 CET

My eclipse plugins are:

$ rpm -qa | grep eclipse
eclipse-emf-core-2.9.1-2.mga4
eclipse-platform-4.3.1-8.mga4
icu4j-eclipse-50.1.1-3.mga4
eclipse-jdt-4.3.1-8.mga4
eclipse-swt-4.3.1-8.mga4
eclipse-ecf-core-3.6.1-2.mga4
eclipse-equinox-osgi-4.3.1-8.mga4

Comment 10 Filipe Saraiva 2015-05-28 00:53:51 CEST

Closing this bug because the problem was solved.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 11 Filipe Saraiva 2015-05-28 00:57:23 CEST

Mark the resolution as "OLD" is more correct for this case I think.

Resolution: FIXED => OLD