desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #148671
[Bug 1379431] Re: Eclipse crashes very often because of problems with GTK
Launchpad has imported 55 comments from the remote bug at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2014-03-19T21:30:42+00:00 Mari-donkers-1 wrote:
Starting a freshly downloaded Eclipse Luna fails. Error log attached.
Tried Java and Java EE versions (both fail with the same error).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/0
------------------------------------------------------------------------
On 2014-03-19T21:35:06+00:00 Mari-donkers-1 wrote:
Created attachment 241028
Error log produced by Eclipse at startup.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/1
------------------------------------------------------------------------
On 2014-03-19T21:37:27+00:00 Mari-donkers-1 wrote:
Comment on attachment 241028
Error log produced by Eclipse at startup.
Configured Sun Java 8 via -vm in eclipse.ini (but it also fails with the
same error when using default OpenJDK 7 - hence no -vm specified in
eclipse.ini ).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/2
------------------------------------------------------------------------
On 2014-03-24T09:51:55+00:00 Arunkumar-thondapu-i wrote:
This is a very unusual crash during the initial load of GTK+ itself.
Which versions of GTK+ 2 and GTK+ 3 are installed on this machine?
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?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/3
------------------------------------------------------------------------
On 2014-03-24T14:09:55+00:00 Mari-donkers-1 wrote:
(In reply to Arun Thondapu from comment #3)
> This is a very unusual crash during the initial load of GTK+ itself. Which
> versions of GTK+ 2 and GTK+ 3 are installed on this machine?
Default Debian 7.4 Wheezy install via text installer on DVD with
additional packages installed. The output of a grep of gtk related
packages is given below:
# dpkg -l '*gtk*' | grep ^i
ii libcanberra-gtk3-0:amd64 0.28-6 amd64 GTK+ 3.0 helper for playing widget event sounds with libcanberra
ii libcanberra-gtk3-module:amd64 0.28-6 amd64 translates GTK3 widgets signals to event sounds
ii libgpod4-nogtk:amd64 0.8.2-7 amd64 library to read and write songs to an iPod
ii libgtk-3-0:amd64 3.4.2-7 amd64 GTK+ graphical user interface library
ii libgtk-3-bin 3.4.2-7 amd64 programs for the GTK+ graphical user interface library
ii libgtk-3-common 3.4.2-7 all common files for the GTK+ graphical user interface library
ii libgtk2.0-0:amd64 2.24.10-2 amd64 GTK+ graphical user interface library
ii libgtk2.0-bin 2.24.10-2 amd64 programs for the GTK+ graphical user interface library
ii libgtk2.0-common 2.24.10-2 all common files for the GTK+ graphical user interface library
ii libgtkmm-2.4-1c2a 1:2.24.2-1 amd64 C++ wrappers for GTK+ (shared libraries)
ii libjavascriptcoregtk-1.0-0 1.8.1-3.4 amd64 Javascript engine library for GTK+
ii libwebkitgtk-1.0-0 1.8.1-3.4 amd64 Web content engine library for GTK+
ii libwebkitgtk-1.0-common 1.8.1-3.4 all Web content engine library for GTK+ - data files
ii libwxgtk2.8-0:amd64 2.8.12.1-12 amd64 wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime)
ii pinentry-gtk2 0.8.1-1 amd64 GTK+-2-based PIN or pass-phrase entry dialog for GnuPG
ii python-gtk2 2.24.0-3+b1 amd64 Python bindings for the GTK+ widget set
> 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?
I don't have the GTK tab or option under System Settings -> Application
Appearance
Do remember this from earlier KDE use so I'll try to find out why it's
not there. Will try install of gtk3-engines-oxygen kde-config-gtk-style-
preview packages, which are not installed on my system (should they
be?).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/4
------------------------------------------------------------------------
On 2014-03-24T15:20:42+00:00 Mari-donkers-1 wrote:
Created attachment 241184
GTK configuration for KDE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/5
------------------------------------------------------------------------
On 2014-03-24T15:23:12+00:00 Mari-donkers-1 wrote:
(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-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
#
# 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.
#
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/6
------------------------------------------------------------------------
On 2014-03-24T17:16:27+00:00 Mari-donkers-1 wrote:
BTW: Eclipse Kepler with Java8 update patch works fine.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/7
------------------------------------------------------------------------
On 2014-03-28T10:55:44+00:00 Sravan Kumar Lakkimsetti wrote:
Hi,
According to the log we can see that both GTK2 and GTK3 libraries are
loaded and the gtk2 pi library loaded.
In luna eclipse should have started with GTK3 and GTK3 PI libraries by
default. Can you please let us know about the following
1. If there are any environment settings done before starting eclipse ?
2. Is this problem reproducible with Java 7?
Thanks
Sravan
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/8
------------------------------------------------------------------------
On 2014-03-28T12:06:09+00:00 Sravan Kumar Lakkimsetti wrote:
Also
Can please please try using a new workspace?
Please provide us the build id this can be obtained from help->about
eclipse
Thanks
Sravan
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/9
------------------------------------------------------------------------
On 2014-03-28T12:51:14+00:00 Mari-donkers-1 wrote:
(In reply to Sravan Kumar Lakkimsetti from comment #8)
> Hi,
>
> According to the log we can see that both GTK2 and GTK3 libraries are loaded
> and the gtk2 pi library loaded.
>
> In luna eclipse should have started with GTK3 and GTK3 PI libraries by
> default. Can you please let us know about the following
>
> 1. If there are any environment settings done before starting eclipse ?
> 2. Is this problem reproducible with Java 7?
>
> Thanks
> Sravan
1. tried running it from a clean account (so no specific environment
variables and also no workspace yet) and it still crashes
2. env. vars.: see 1. above; tried openjre7 from Debian respository,
Luna also crashes, see log below.
3. build version: I cannot determine this from the Eclipse GUI
Help->About because it crashes before the GUI is activated (I only see
the small startup flash window).
$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
mdo@vapulo:~/Downloads/Eclipse/4.4 (Luna)/eclipse$ ./eclipse
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:15330): GLib-GObject-WARNING **: cannot register existing type
`GdkDisplayManager'
(java:15330): GLib-CRITICAL **: g_once_init_leave: assertion `result !=
0' failed
(java:15330): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed
(java:15330): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(java:15330): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
`G_TYPE_CHECK_INSTANCE (instance)' failed
(java:15330): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(java:15330): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
`G_TYPE_CHECK_INSTANCE (instance)' failed
(java:15330): GLib-GObject-WARNING **: cannot register existing type
`GdkDisplay'
(java:15330): GLib-CRITICAL **: g_once_init_leave: assertion `result !=
0' failed
(java:15330): GLib-GObject-CRITICAL **: g_type_register_static:
assertion `parent_type > 0' failed
(java:15330): GLib-CRITICAL **: g_once_init_leave: assertion `result !=
0' failed
(java:15330): 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=0x00007f5db090c73f, pid=15330, tid=140040758400768
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 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_pid15330.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/10
------------------------------------------------------------------------
On 2014-03-28T13:06:18+00:00 Mari-donkers-1 wrote:
Found this bug report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=420180
but setting environment variable SWT_GTK3 to 1 does not make a
difference.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/11
------------------------------------------------------------------------
On 2014-03-28T14:19:09+00:00 Mari-donkers-1 wrote:
Have install Debian 7.4 (latest) 64-bit (amd64) into a VirtualBox
virtual machine. Downloaded Eclipse Luna and tried to execute:
1) with default openjdk6;
2) installed openjdk7-jre to try with java 7;
3) installed kde-config-gtk-style package and used Settings -> Application appearance -> GTK to check if GTK2 style set to Raleigh (it was already and GTK3 style is set to default; there's no Raleigh choice available for GTK3).
All tries failed. Will attach crash reports.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/12
------------------------------------------------------------------------
On 2014-03-28T14:20:07+00:00 Mari-donkers-1 wrote:
Created attachment 241381
VirtualBox clean Debian 7 64-bit install; Java 6
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/13
------------------------------------------------------------------------
On 2014-03-28T14:20:26+00:00 Mari-donkers-1 wrote:
Created attachment 241382
VirtualBox clean Debian 7 64-bit install; Java 7
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/14
------------------------------------------------------------------------
On 2014-03-28T14:20:45+00:00 Mari-donkers-1 wrote:
Created attachment 241383
VirtualBox clean Debian 7 64-bit install; Java 7; Raleigh GTK2
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/15
------------------------------------------------------------------------
On 2014-03-28T14:36:15+00:00 Mari-donkers-1 wrote:
(In reply to Mari Donkers from comment #12)
> Have install Debian 7.4 (latest) 64-bit (amd64) into a VirtualBox virtual
> machine. Downloaded Eclipse Luna and tried to execute:
>
> 1) with default openjdk6;
> 2) installed openjdk7-jre to try with java 7;
> 3) installed kde-config-gtk-style package and used Settings -> Application
> appearance -> GTK to check if GTK2 style set to Raleigh (it was already and
> GTK3 style is set to default; there's no Raleigh choice available for GTK3).
>
> All tries failed. Will attach crash reports.
BTW: Eclipse Kepler also works fine (in the virtual machine Debian 7 KDE
64-bit install).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/16
------------------------------------------------------------------------
On 2014-04-01T19:21:32+00:00 Mari-donkers-1 wrote:
So the problem is easily reproducible by doing a Debian 7.4 64-bit KDE
install in a VirtualBox environment, install of Java packages, download
of latest Eclipse Juno and attempt to start it.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/17
------------------------------------------------------------------------
On 2014-04-07T09:40:44+00:00 Sravan Kumar Lakkimsetti wrote:
>From the logs we find that GTK2 and GTK3 have been loaded. This is not
supposed to happen. Looks like due to some internal dependencies both
gtk2 and gtk3 are getting loaded
Can you please let us know Whether this problem occurs with environment
variable SWT_GTK3 set to 0?
For the comparision sake can you please attach the output of
lsof -p <pid>
for the JVM started by eclipse with SWT_GTK3 set to 0 and set to 1?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/18
------------------------------------------------------------------------
On 2014-04-12T09:52:23+00:00 Mari-donkers-1 wrote:
(In reply to Sravan Kumar Lakkimsetti from comment #18)
> From the logs we find that GTK2 and GTK3 have been loaded. This is not
> supposed to happen. Looks like due to some internal dependencies both gtk2
> and gtk3 are getting loaded
>
> Can you please let us know Whether this problem occurs with environment
> variable SWT_GTK3 set to 0?
THAT WORKS! Eclipse Luna starts normally when I first do the suggested:
export SWT_GTK3=0
> For the comparision sake can you please attach the output of
> lsof -p <pid>
> for the JVM started by eclipse with SWT_GTK3 set to 0 and set to 1?
Will attach output for it set to 0 (not for 1 because it crashes and then there's
no jvm running)
Thanks for workaround and the support!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/19
------------------------------------------------------------------------
On 2014-04-12T09:53:42+00:00 Mari-donkers-1 wrote:
Created attachment 241915
Requested output of lsof -p <jvm-pid>
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/20
------------------------------------------------------------------------
On 2014-04-13T10:03:27+00:00 Mari-donkers-1 wrote:
(In reply to Mari Donkers from comment #19)
> Will attach output for it set to 0 (not for 1 because it crashes and then
> there's no jvm running)
>
Will output for it set to 1 running under SolydK (i.e. a Debian Testing,
tested distribution) where it does not crash.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/21
------------------------------------------------------------------------
On 2014-04-13T10:08:46+00:00 Mari-donkers-1 wrote:
Created attachment 241930
SWT_GTK3-set-to-1_SolyK.txt
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/22
------------------------------------------------------------------------
On 2014-04-15T09:39:59+00:00 Sravan Kumar Lakkimsetti wrote:
Hi,
>From the logs it seems that gtk3 libraries are loaded but wrong version
platform interface(pi) library developed for eclipse is getting loaded.
There are two pi libraries libswt-pi and libswt-pi3. Whenever gtk3 is
loaded libswt-pi3 should get loaded. but it looks like this library is
not getting loaded.
One way to confirm is to check whether all the dependencies are
satisfied using the ldd command
the pi libraries are present at <eclipse
home>/configuration/org.eclipse.osgi/209/0/.cp/
send us the output of ldd libswt-pi3-gtk-<version>.so
This should reveal any missing dependencies
Also can you reproduce the problem with other JREs like Oracle JRE?
Thanks
Sravan
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/23
------------------------------------------------------------------------
On 2014-04-17T19:27:10+00:00 Mari-donkers-1 wrote:
(In reply to Sravan Kumar Lakkimsetti from comment #23)
> Hi,
>
> From the logs it seems that gtk3 libraries are loaded but wrong version
> platform interface(pi) library developed for eclipse is getting loaded.
>
> There are two pi libraries libswt-pi and libswt-pi3. Whenever gtk3 is loaded
> libswt-pi3 should get loaded. but it looks like this library is not getting
> loaded.
>
> One way to confirm is to check whether all the dependencies are satisfied
> using the ldd command
>
> the pi libraries are present at <eclipse
> home>/configuration/org.eclipse.osgi/209/0/.cp/
>
> send us the output of ldd libswt-pi3-gtk-<version>.so
>
> This should reveal any missing dependencies
Will add attachment.
>
> Also can you reproduce the problem with other JREs like Oracle JRE?
Yes, see earlier posts. Most of the error logs I added are for Oracle
JRE 8.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/24
------------------------------------------------------------------------
On 2014-04-17T19:27:34+00:00 Mari-donkers-1 wrote:
Created attachment 242107
LDD.txt
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/25
------------------------------------------------------------------------
On 2014-04-18T09:21:44+00:00 Sravan Kumar Lakkimsetti wrote:
(In reply to Mari Donkers from comment #25)
> Created attachment 242107 [details]
> LDD.txt
Than you for the update. From the ldd out put we can clearly see that
the glibc version is satisfied. The minimum version we require is glibc
2.14.
>From the prior crash log we can see that glibc 2.13 is installed.
Can you please upgrade glibc to atleast 2.14 and verify?
In the meanwhile you can use setting SWT_GTK3=0 as workaround. This
makes eclipse to use gtk2 instead of gtk3
Thanks
Sravan
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/26
------------------------------------------------------------------------
On 2014-04-18T17:56:19+00:00 Mari-donkers-1 wrote:
(In reply to Sravan Kumar Lakkimsetti from comment #26)
> (In reply to Mari Donkers from comment #25)
> > Created attachment 242107 [details]
> > LDD.txt
>
> Than you for the update. From the ldd out put we can clearly see that the
> glibc version is satisfied. The minimum version we require is glibc 2.14.
>
> From the prior crash log we can see that glibc 2.13 is installed.
>
> Can you please upgrade glibc to atleast 2.14 and verify?
No can do... It's not delivered with Debian Wheezy and installing it
from Debian testing or experimental sounds a bit fishy.
The page:
http://superuser.com/questions/537683/how-to-fix-lib-x86-64-linux-gnu-
libc-so-6-version-glibc-2-14-not-found/537694#537694
reads:
"Glibc is the library that everything depends on, so upgrading it can
have far-reaching implications. Although there's probably nothing wrong
with Debian's glibc 2.16 package, the fact that it's in the experimental
repository means it hasn't received as much testing."
Eclipse Luna should be able to run on Debian 7.4 Wheezy stable out of
the box because the stable distribution is used primarily by businesses
(because it's stable and low maintenance).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/27
------------------------------------------------------------------------
On 2014-04-18T18:23:58+00:00 Mari-donkers-1 wrote:
(In reply to Mari Donkers from comment #27)
> (In reply to Sravan Kumar Lakkimsetti from comment #26)
> > (In reply to Mari Donkers from comment #25)
> > > Created attachment 242107 [details]
> > > LDD.txt
> >
> > Than you for the update. From the ldd out put we can clearly see that the
> > glibc version is satisfied. The minimum version we require is glibc 2.14.
> >
> > From the prior crash log we can see that glibc 2.13 is installed.
> >
> > Can you please upgrade glibc to atleast 2.14 and verify?
>
> No can do... It's not delivered with Debian Wheezy and installing it from
> Debian testing or experimental sounds a bit fishy.
>
> The page:
>
> http://superuser.com/questions/537683/how-to-fix-lib-x86-64-linux-gnu-libc-
> so-6-version-glibc-2-14-not-found/537694#537694
>
> reads:
>
> "Glibc is the library that everything depends on, so upgrading it can have
> far-reaching implications. Although there's probably nothing wrong with
> Debian's glibc 2.16 package, the fact that it's in the experimental
> repository means it hasn't received as much testing."
>
> Eclipse Luna should be able to run on Debian 7.4 Wheezy stable out of the
> box because the stable distribution is used primarily by businesses (because
> it's stable and low maintenance).
That said, your suggestion *does work* (Eclipse Luna starts fine) when I
first install glibc 2.18, as instructed on the following page:
http://verahill.blogspot.nl/2014/03/562-pulling-in-glibc-214-from-
testing.html
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/28
------------------------------------------------------------------------
On 2014-04-18T22:37:03+00:00 Stephan wrote:
I'm seeing the same/similar crash.
Interestingly, for me it only happens in a runtime workbench!
I'm running Eclipse SDK I20130918-2000 on Kubuntu 12.04, works OK.
Inside the IDE I launch a runtime workbench with all platform bundles from the host. This runtime workbench crashes.
Due to various problems with GTK3 on this box I'm running with
SWT_GTK3=0, but in the log I see libgtk-3.so.0.400.2 loaded. I even
explicitly added SWT_GTK3=0 to the launch configuration's environment.
Is this variable not evaluated in a runtime workbench??
glibc is 2.15 NPTL 2.15
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/29
------------------------------------------------------------------------
On 2014-04-18T22:52:58+00:00 Stephan wrote:
(In reply to Stephan Herrmann from comment #29)
> I'm seeing the same/similar crash.
>
> Interestingly, for me it only happens in a runtime workbench!
>
> I'm running Eclipse SDK I20130918-2000 on Kubuntu 12.04, works OK.
> Inside the IDE I launch a runtime workbench with all platform bundles from
> the host. This runtime workbench crashes.
>
> Due to various problems with GTK3 on this box I'm running with SWT_GTK3=0,
> but in the log I see libgtk-3.so.0.400.2 loaded. I even explicitly added
> SWT_GTK3=0 to the launch configuration's environment. Is this variable not
> evaluated in a runtime workbench??
>
> glibc is 2.15 NPTL 2.15
All this works with I20140325-0830, so may not be relevant any more.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/30
------------------------------------------------------------------------
On 2014-05-11T18:09:59+00:00 Arunkumar-thondapu-i wrote:
*** Bug 434559 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/31
------------------------------------------------------------------------
On 2014-06-19T11:51:06+00:00 Sravan Kumar Lakkimsetti wrote:
Debian wheezy comes with glibc 2.13. For eclipse in gtk3 we need the
minimum version to be 2.14.
To resolve the problem please upgrade the glibc version to 2.14.
We will be closing this as wont fix as upgrading glibc will resolve the
problem
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/32
------------------------------------------------------------------------
On 2014-06-26T06:12:18+00:00 Arunkumar-thondapu-i wrote:
*** Bug 438174 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/33
------------------------------------------------------------------------
On 2014-06-26T09:26:58+00:00 Alejolp-w wrote:
Can you add a check for the glibc version?
I confirm that setting SWT_GTK3=0 solves this issue, not only on CDT but
also on JEE.
I know Debian Wheezy is somewhat old for today's standards, but it works
and I use it for work everyday. This issue can be fixed by adding a new
check on the platform code, to detect if glibc version is 2.13 then set
SWT_GTK3=0.
Thank you.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/34
------------------------------------------------------------------------
On 2014-06-26T11:01:21+00:00 Sravan Kumar Lakkimsetti wrote:
(In reply to Alejandro Santos from comment #34)
> Can you add a check for the glibc version?
>
> I confirm that setting SWT_GTK3=0 solves this issue, not only on CDT but
> also on JEE.
>
> I know Debian Wheezy is somewhat old for today's standards, but it works and
> I use it for work everyday. This issue can be fixed by adding a new check on
> the platform code, to detect if glibc version is 2.13 then set SWT_GTK3=0.
>
> Thank you.
Hi,
It will be difficult to make the change for debian wheezy as the glibc
used there is quite old. I understand setting the flag everytime you
need to start eclipse is slightly irritating. You can add the following
lines to eclipse.ini to make it permanent
--launcher.GTK_version
2
This will force eclipse to use GTK 2 always
Thanks
Sravan
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/35
------------------------------------------------------------------------
On 2014-06-26T11:59:05+00:00 Alejolp-w wrote:
(In reply to Sravan Kumar Lakkimsetti from comment #35)
>
> It will be difficult to make the change for debian wheezy as the glibc used
> there is quite old.
What I mean is that, when Eclipse detects an old version of GLIBC, force
the use of GTK2.
> I understand setting the flag everytime you need to
> start eclipse is slightly irritating. You can add the following lines to
> eclipse.ini to make it permanent
>
> --launcher.GTK_version
> 2
>
This change breaks my Eclipse launcher:
$ ./eclipse
Unrecognized option: --launcher.GTK_version
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/36
------------------------------------------------------------------------
On 2014-06-26T12:26:39+00:00 Alejolp-w wrote:
(In reply to Sravan Kumar Lakkimsetti from comment #35)
>
> --launcher.GTK_version
> 2
>
> This will force eclipse to use GTK 2 always
>
Never mind, I mixed the order on the eclipse.ini file (just noticed the
vmargs arguments). It works now.
Thanks!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/37
------------------------------------------------------------------------
On 2014-06-27T14:00:11+00:00 Arunkumar-thondapu-i wrote:
*** Bug 438342 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/38
------------------------------------------------------------------------
On 2014-06-27T16:59:04+00:00 Pwebster-ca wrote:
*** Bug 438424 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/39
------------------------------------------------------------------------
On 2014-07-01T11:37:42+00:00 Daniel-megert wrote:
*** Bug 438588 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/40
------------------------------------------------------------------------
On 2014-07-02T14:07:30+00:00 Pwebster-ca wrote:
*** Bug 438521 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/41
------------------------------------------------------------------------
On 2014-07-15T07:03:55+00:00 Arunkumar-thondapu-i wrote:
*** Bug 439436 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/42
------------------------------------------------------------------------
On 2014-07-23T08:22:21+00:00 Dars-vaeda wrote:
Can someone provide a full eclipse.ini with the suggested patch.
I can run eclipse by running the export command prior to the launch.
But adding "--launcher.GTK_version 2" does not work for me on Debian Wheezy with Gnome.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/43
------------------------------------------------------------------------
On 2014-07-23T08:50:37+00:00 Alejolp-w wrote:
(In reply to Dars Vaeda from comment #43)
> Can someone provide a full eclipse.ini with the suggested patch.
> I can run eclipse by running the export command prior to the launch.
> But adding "--launcher.GTK_version 2" does not work for me on Debian Wheezy
> with Gnome.
The option --launcher.GTK_version should be *before*
--launcher.appendVmargs
Mine for CDT is:
$ cat eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140603-1326
-product
org.eclipse.epp.package.cpp.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.GTK_version
2
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=256m
-Xms40m
-Xmx1536m
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/44
------------------------------------------------------------------------
On 2014-07-28T07:02:16+00:00 Dars-vaeda wrote:
Thx, I think the crucial part here was that the "2" is on a new line.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/45
------------------------------------------------------------------------
On 2014-08-18T17:20:18+00:00 Arunkumar-thondapu-i wrote:
*** Bug 441931 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/46
------------------------------------------------------------------------
On 2014-08-21T13:30:27+00:00 Arunkumar-thondapu-i wrote:
*** Bug 442212 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/47
------------------------------------------------------------------------
On 2014-09-02T09:57:30+00:00 Marksoccerman1 wrote:
I am running KALI
PRETTY_NAME="Kali GNU/Linux 1.0"
NAME="Kali GNU/Linux"
I would like to add a resolve that by adding the line:
--launcher.GTK_version
2
in the eclipse.ini form starting on the third line:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.GTK_version
2
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140603-1326
-product
org.eclipse.epp.package.standard.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
/usr/lib/jvm/jdk1.8.0_20/jre/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
allows eclipse to function nominally. Also notice I running jdk1.8.0_20 as well.
Thank you for your efforts and research.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/48
------------------------------------------------------------------------
On 2014-09-03T10:46:58+00:00 Arunkumar-thondapu-i wrote:
*** Bug 442741 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/49
------------------------------------------------------------------------
On 2014-09-11T09:51:11+00:00 Andreas Krueger wrote:
The bug title mentions "KDE". Not relevant, I had the same problem with
XFCE. Both workarounds solved the problem for me, i.e., either setting
the environment variable SWT_GTK3=0 or else adding the two lines
--launcher.GTK_version
2
to eclipse.ini.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/50
------------------------------------------------------------------------
On 2014-10-14T21:03:09+00:00 jenskapitza wrote:
SWT_GTK3=0 must be used in fluxbox too,
i've a mixed enviroment with gtk2 and gtk3
whezzy and sid/ubuntu 14.04
cp to .swt does not work
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/53
------------------------------------------------------------------------
On 2015-06-29T11:54:36+00:00 Norbert-lange wrote:
I have the same issue with Eclipse Mars and Wheezy 64bit.
(Setting the env variable fixes it)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/54
------------------------------------------------------------------------
On 2015-08-13T12:01:23+00:00 Arunkumar-thondapu-i wrote:
*** Bug 474849 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/55
------------------------------------------------------------------------
On 2015-11-13T00:38:22+00:00 Matt Parker wrote:
I just ran into this after upgrading kubuntu to 15.10. Forcing GTK2
works. Using or not using the oxygen theme doesn't seem to matter.
Version: Mars.1 Release (4.5.1)
Build id: 20150924-1200
Why is this bug marked as RESOLVED WONTFIX?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1379431/comments/57
** Changed in: eclipse-eclipsers
Status: Unknown => Won't Fix
** Changed in: eclipse-eclipsers
Importance: Unknown => Critical
** Bug watch added: Eclipse bugs #420180
https://bugs.eclipse.org/bugs/show_bug.cgi?id=420180
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1379431
Title:
Eclipse crashes very often because of problems with GTK
Status in Eclipse:
Won't Fix
Status in eclipse package in Ubuntu:
Confirmed
Bug description:
Especially when clicking buttons Eclipse crashes.
This is regardless of
- the Java version (tried openjava 7 and oracle java 7)
- the eclipse version (tried the ubuntu delivered 3.8 and 4.4 download from eclipse.org)
They say the cause is that eclipse loads a mix of GTK2 and GTK3 libs.
(cannot find the source now)
Solution: simply add the env var
export SWT_GTK3=1
Ubuntu 14.04.1 LTS
Package: eclipse
Architecture: all
Version: 3.8.1-5.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse-eclipsers/+bug/1379431/+subscriptions
References
