You are not logged in.
Hi,
I'm running Xubuntu 14.04 (x64) and I upgraded Xfce from 4.10 to 4.12 (through adding "xubuntu-dev/xfce-4.12" ppa). After that, Eclipse became instable and crashes under several circumstances (e.g. creating new project).
In the terminal, it shows the following error message:
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 28725 error_code 3 request_code 3 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
After downgrading back to 4.10, the instability disappeared and eclipse worked fine again.
I tried both eclipse 3.8 (from Xubuntu repositories) and eclipse 4.4 from the website. I also tried different jdk versions (1.7, 1.8).
At the beginning I thought it was an incompatibility between xubuntu 14.04 and xfce 4.12, but recently I found someone who has the exact same issue running Xubuntu 15.04 which comes with xfce 4.12 preinstalled: Three different Eclipse versions all crash with BadWindow on 15.04
Is this issue related to xfce 4.12 at all? Is there anything I can do to solve this issue? Is it a bug?
Last edited by Mario89 (2015-05-03 11:10:32)
Offline
same problem here. Actually eclipse ( luna 4.4 sr2 ) crashes every-single-time i try to start it.
Running Slackware-current x86_64, custom kernel 4.0 on a Dell xps lx502 (Optimus nvidia/intel hybrid ) running on the intel GPU, strace'ing eclipse stops on "nvidia/wayland" ???
...//...
close(7) = 0
open("/lib64/libnvidia-egl-wayland.so.", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib64/tls/libnvidia-egl-wayland.so.", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib64/libnvidia-egl-wayland.so.", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
munmap(0x7fa43c00f000, 234514) = 0
exit_group(1) = ?
+++ exited with 1 +++
/java7/bin/java -version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
eclipse outputs a window with:
JVM terminated. Exit code=1
/java7/bin/java
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /opt/eclipse_jee_4.4//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /opt/eclipse_jee_4.4//plugins/org.eclipse.platform_4.4.2.v20150204-1700/splash.bmp
-launcher /opt/eclipse_jee_4.4/eclipse
-name Eclipse
--launcher.library /opt/eclipse_jee_4.4//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20150204-1316/eclipse_1607.so
-startup /opt/eclipse_jee_4.4//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.appendVmargs
-exitdata b20015
-product org.eclipse.epp.package.java.product
-vm /java7/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /opt/eclipse_jee_4.4//plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
and the terminal outputs:
/opt/eclipse_jee_4.4/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.
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 6432 error_code 3 request_code 3 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
( switching WM to blackbox, eclipse runs fine )
any ideas ?... need more info ?
Last edited by brethel (2015-05-05 07:04:34)
Offline
I run eclipse on Xfce and don't experience the crashes. However, I have an intel video card. Given the information both of you have outlined above, perhaps a bug report is in order. At least to give the xfwm developers notice of the issue.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Online
I've created a bug report: https://bugzilla.xfce.org/show_bug.cgi?id=11893
Offline
UPDATE: after a
tar cjvf myXFCE_confs_bkp.tar.bz2 $HOME/.config/xfce4
rm -rf $HOME/.config/xfce4
ecliipse is starting fine on xfce 4.12; surely there was some garbage on my configs... then, while reconfiguring my enviroment, when i set "Kiwi" as window manager theme; eclipse's startup crashes again; using blackbird theme now, and it starts up nicely, but crashes "at random" ( so it seems ).
Last edited by brethel (2015-05-11 00:47:52)
Offline
[ Generated in 0.008 seconds, 7 queries executed - Memory usage: 542.06 KiB (Peak: 543.34 KiB) ]