Version-Release number of selected component: java-1.7.0-openjdk-1.7.0.9-2.3.7.0.fc18 Additional info: backtrace_rating: 3 cmdline: /usr/bin/java -Dosgi.requiredJavaVersion=1.5 -Dhelp.lucene.tokenizer=standard -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /home/aryana/Documents/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar -os linux -ws gtk -arch x86_64 -showsplash /home/aryana/Documents/eclipse//plugins/org.eclipse.platform_4.2.1.v201209141800/splash.bmp -launcher /home/aryana/Documents/eclipse/eclipse -name Eclipse --launcher.library /home/aryana/Documents/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813/eclipse_1502.so -startup /home/aryana/Documents/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar --launcher.overrideVmargs -exitdata 5c000d -product org.eclipse.epp.package.jee.product -vm /usr/bin/java -vmargs -Dosgi.requiredJavaVersion=1.5 -Dhelp.lucene.tokenizer=standard -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /home/aryana/Documents/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar core_backtrace: crash_function: gdk_x_error executable: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre/bin/java kernel: 3.7.9-205.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 gdk_x_error at /lib64/libgdk-x11-2.0.so.0 #4 handle_error at xcb_io.c:212 #5 handle_response at xcb_io.c:324 #6 _XReadEvents at xcb_io.c:425 #7 _cairo_xlib_shm_surface_flush at cairo-xlib-surface-shm.c:696 #8 *INT_cairo_surface_flush at cairo-surface.c:1510 #9 INT_cairo_surface_flush at cairo-surface.c:1500 #10 _cairo_xlib_surface_discard_shm at cairo-xlib-surface.c:369 #11 _cairo_xlib_surface_finish at cairo-xlib-surface.c:401 #12 _cairo_surface_finish at cairo-surface.c:1007
Created attachment 704961 [details] File: backtrace
Created attachment 704962 [details] File: build_ids
Created attachment 704963 [details] File: cgroup
Created attachment 704964 [details] File: dso_list
Created attachment 704965 [details] File: environ
Created attachment 704966 [details] File: limits
Created attachment 704967 [details] File: maps
Created attachment 704968 [details] File: open_fds
Created attachment 704969 [details] File: proc_pid_status
Created attachment 704970 [details] File: var_log_messages
Error seems to have originated in GTK2: #37 0x00000030f3086268 in gtk_widget_unparent () from /lib64/libgtk-x11-2.0.so.0 Re-assigning.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.