Bug 1327833

https://git.gnome.org/browse/gtk+/commit/gtk?id=96f0ed9ec5b5b071efabb15b03c37f40df7ae3b1 might be related

Would you please try with Neon I-builds? This issue should be fixed there but Mars stream is closed for development.

Oops, mixed bugzilla instances. Mat, should we try to identify the patch to backport? I would vote for pushing Neon builds as from upstream work I'm expecting many such issues so backporting all of them is probably not feasible.

(In reply to Alexander Kurtakov from comment #2)
> Would you please try with Neon I-builds? This issue should be fixed there
> but Mars stream is closed for development.

I guess you meant me. Where do I get them?

https://www.eclipse.org/downloads/ seems to be offline. eclipse.org is loading pretty slow or not at all.

https://copr.fedorainfracloud.org/coprs/mbooth/eclipse-neon/ has 4 months old builds

It doesn't seem to be in Fedora 25 aka rawhide yet.

Sorry Christian, I thought I was replying in eclipse.org bz. Let's give Mat some time to jump in, we have to provide Neon builds for f24 (the sooner the better).

*** Bug 1328388 has been marked as a duplicate of this bug. ***

Now that abrt/uReport works again, I've reported the crasher as bug #1328388 which might be a duplicate of bug #1264644 and bug #1264512

Hi,

Eclipse Neon is now available for F25 (Rawhide).

Once I'm happy everything works, backporting Neon to F24 should be possible for the F24 release or F24 zero-day update.

(In reply to Mat Booth from comment #8)
> Once I'm happy everything works, backporting Neon to F24 should be possible
> for the F24 release or F24 zero-day update.

Do you really want to ship a not-yet-released Eclipse (Neon) in F24? Or do you provide it in a separate repo?

(In reply to Christian Stadelmann from comment #9)
> (In reply to Mat Booth from comment #8)
> > Once I'm happy everything works, backporting Neon to F24 should be possible
> > for the F24 release or F24 zero-day update.
> 
> Do you really want to ship a not-yet-released Eclipse (Neon) in F24? Or do
> you provide it in a separate repo?

Today is the last development day for Neon upstream switching to bugfix mode till release in June. With RC2 on May 27 this is the most likely release. Due to the amount of changes in both Neon and Gtk 3.20 (in terms of CSS machinery) it's not feasible to backport all the changes needed so in order to provide usable Eclipse this is our only feasible path.

(In reply to Alexander Kurtakov from comment #10)
> Today is the last development day for Neon upstream switching to bugfix mode
> till release in June. With RC2 on May 27 this is the most likely release.
> Due to the amount of changes in both Neon and Gtk 3.20 (in terms of CSS
> machinery) it's not feasible to backport all the changes needed so in order
> to provide usable Eclipse this is our only feasible path.

Ok, I didn't know that. Thanks for clarification!

Similar problem has been detected:

Starting JBDS

reporter:       libreport-2.7.1
backtrace_rating: 4
cmdline:        /usr/lib/jvm/java/bin/java -javaagent:/home/<username>/jbdevstudio9/studio/plugins/com.zeroturnaround.eclipse.optimizer.plugin_1.0.9/agent/eclipse-optimizer-agent.jar -Xms512m -Xmx1024m -Dosgi.instance.area.default=/workspace -jar /home/<username>/jbdevstudio9/studio//plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher /home/<username>/jbdevstudio9/studio/jbdevstudio -name Jbdevstudio --launcher.library /home/<username>/jbdevstudio9/studio//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.300.v20150602-1417/eclipse_1612.so -startup /home/<username>/jbdevstudio9/studio//plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar --launcher.overrideVmargs -exitdata 130003 -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product -clean -vm /usr/lib/jvm/java/bin/java -vmargs -javaagent:/home/<username>/jbdevstudio9/studio/plugins/com.zeroturnaround.eclipse.optimizer.plugin_1.0.9/agent/eclipse-optimizer-agent.jar -Xms512m -Xmx1024m -Dosgi.instance.area.default=/workspace -jar /home/<username>/jbdevstudio9/studio//plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
crash_function: os::abort(bool)
executable:     /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.92-1.b14.fc24.x86_64/bin/java
global_pid:     3710
kernel:         4.5.7-300.fc24.x86_64
package:        java-1.8.0-openjdk-devel-1.8.0.92-1.b14.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         java killed by SIGABRT
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           CCpp
uid:            1000

Created attachment 1171992 [details]
File: backtrace

(In reply to Thom Carlin from comment #12)
> Similar problem has been detected:
> 
> Starting JBDS
> 

Hi Thom, it looks like you are using some third-party edition of Eclipse and not the Fedora packaged version. Unfortunately we cannot support something that is not part of the distro -- you would be better reporting this problem to the JDBS people.

(In reply to Christian Stadelmann from comment #11)
> (In reply to Alexander Kurtakov from comment #10)
> > Today is the last development day for Neon upstream switching to bugfix mode
> > till release in June. With RC2 on May 27 this is the most likely release.
> > Due to the amount of changes in both Neon and Gtk 3.20 (in terms of CSS
> > machinery) it's not feasible to backport all the changes needed so in order
> > to provide usable Eclipse this is our only feasible path.
> 
> Ok, I didn't know that. Thanks for clarification!

Christian, is this problem fixed for you with Eclipse 4.6.0?

I don't see this any more on eclipse-swt-4.6.0-0.6.git201605092000.fc24.x86_64 with both, x11 and wayland Gdk backends. Seems to be fixed.