(In reply to Arun Thondapu from comment #3)
> Its possible that this is an issue caused by the oxygen GTK theme that KDE
> uses. Can you please try the workaround mentioned here -
> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1241101/comments/51 -
> and update whether it resolves the crash?
Installed kde-config-gtk-style to get the GTK Configuration (screendump attached)
and set to Raleigh.
No difference, it still crashes but now with a different error message:
$ ./eclipse
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
(java:7456): GLib-GObject-WARNING **: cannot register existing type `GdkDisplayManager'
(java:7456): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fe97938573f, pid=7456, tid=140641328412416
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgdk-x11-2.0.so.0+0x5173f] gdk_display_open+0x3f
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/mdo/Downloads/Eclipse/4.4 (Luna)/eclipse/hs_err_pid7456.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
(In reply to Arun Thondapu from comment #3) /bugs.launchpad .net/ubuntu/ +source/ unity/+ bug/1241101/ comments/ 51 -
> Its possible that this is an issue caused by the oxygen GTK theme that KDE
> uses. Can you please try the workaround mentioned here -
> https:/
> and update whether it resolves the crash?
Installed kde-config- gtk-style to get the GTK Configuration (screendump attached)
and set to Raleigh.
No difference, it still crashes but now with a different error message:
$ ./eclipse m2e.logback. configuration: The org.eclipse. m2e.logback. configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
org.eclipse.
(java:7456): GLib-GObject- WARNING **: cannot register existing type `GdkDisplayManager'
(java:7456): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(java:7456): GLib-GObject- CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(java:7456): GLib-GObject- WARNING **: invalid (NULL) pointer instance
(java:7456): GLib-GObject- CRITICAL **: g_signal_ connect_ data: assertion `G_TYPE_ CHECK_INSTANCE (instance)' failed
(java:7456): GLib-GObject- WARNING **: invalid (NULL) pointer instance
(java:7456): GLib-GObject- CRITICAL **: g_signal_ connect_ data: assertion `G_TYPE_ CHECK_INSTANCE (instance)' failed
(java:7456): GLib-GObject- WARNING **: cannot register existing type `GdkDisplay'
(java:7456): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(java:7456): GLib-GObject- CRITICAL **: g_type_ register_ static: assertion `parent_type > 0' failed
(java:7456): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(java:7456): GLib-GObject- CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed 38573f, pid=7456, tid=140641328412416 x11-2.0. so.0+0x5173f] gdk_display_ open+0x3f Downloads/ Eclipse/ 4.4 (Luna)/ eclipse/ hs_err_ pid7456. log bugreport. sun.com/ bugreport/ crash.jsp
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fe979
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgdk-
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/mdo/
#
# If you would like to submit a bug report, please visit:
# http://
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#