Description of problem: 1. Launch eclipse, pydev was installed 2. Navigate to a py file, and press enter to open it 3. problem happened Version-Release number of selected component: java-1.7.0-openjdk-headless-1.7.0.71-2.5.3.0.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: java -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms512m -Xmx1024m -jar /home/chen/android-eclipse/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar -os linux -ws gtk -arch x86_64 -showsplash /home/chen/android-eclipse/eclipse//plugins/org.eclipse.platform_4.2.2.v201302041200/splash.bmp -launcher /home/chen/android-eclipse/eclipse/eclipse -name Eclipse --launcher.library /home/chen/android-eclipse/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807/eclipse_1502.so -startup /home/chen/android-eclipse/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar --launcher.overrideVmargs -exitdata d328022 -product com.android.ide.eclipse.adt.package.adtproduct -vm /usr/bin/java -vmargs -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms512m -Xmx1024m -jar /home/chen/android-eclipse/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar crash_function: pthread_join executable: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre-abrt/bin/java kernel: 3.16.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 pthread_join at /lib64/libpthread.so.0 #1 ContinueInNewThread0 at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/amd64/jli/libjli.so #2 ContinueInNewThread at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/amd64/jli/libjli.so #3 JLI_Launch at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/amd64/jli/libjli.so
Created attachment 948397 [details] File: backtrace
Created attachment 948398 [details] File: cgroup
Created attachment 948399 [details] File: core_backtrace
Created attachment 948400 [details] File: dso_list
Created attachment 948401 [details] File: environ
Created attachment 948402 [details] File: limits
Created attachment 948403 [details] File: maps
Created attachment 948404 [details] File: open_fds
Created attachment 948405 [details] File: proc_pid_status
Created attachment 948406 [details] File: var_log_messages
There is not enough information in the stack trace. Can you reproduce this issue? If so, how can we do it on our end?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.