abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/bin/javaws /home/eduardo/Descargas/tmp.jnlp component: java-1.6.0-openjdk executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/javaws kernel: 2.6.32.9-70.fc12.i686 package: java-1.6.0-openjdk-1:1.6.0.0-36.b17.fc12 rating: 3 reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/javaws was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Try to run a jnpl file 2. 3.
Created attachment 403084 [details] File: backtrace
Created attachment 404219 [details] Goes the jnpl file that causes the bug. In attachment i send de jnlp file that cause the bug. The java net application comes from secure internet site, but i do not remember in this moment the url of the site.
I run the tmp.jnpl file in another machine with debian testing (squeeze) and run ok. The file is a molecular workbench software with the name: "Electrostatic maze game" with the following url: http://mw2.concord.org/public/student/game/electrostatic_maze5.cml Information about molecular workbench may be found in the following url: http://mw2.concord.org/public/about.cml In DEBIAN the system thats run ok is: Vendor: Sun Microsystems Inc. Version: 1.6.0_18 Location: /usr/lib/jvm/java-6-openjdk/jre Number of Processors: 4 Maximum Memory Allocated: 124 MB Total Memory Used: 48 MB Free Memory: 22 MB But the machine where i run the application is not the same machine of the bug. The problem may be to try run the jnlp file from the web browser.
One url that have a link to the electric maze game from intertet is: http://mw.concord.org/modeler1.3/mirror/electrostatics/mazegame.html I going to tree the link from firefox in the machina that gives the bub.
An other link that run the electric maze game from the internet directly is: http://mw2.concord.org/public/student/game/electrostatic_maze5.html
This bug looks like it it might have been fixed with the latest java-1.6.0-openjdk packages (using Icedtea6 version 1.8.1). Can you still reproduce the problem with the latest version?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.