abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: epiphany http://www.octranspo1.com/routes/ component: epiphany crash_function: malloc_consolidate executable: /usr/bin/epiphany global_uuid: 7ff2ec444b57f050db958151195ef4d2aa140ec4 kernel: 2.6.32.11-99.fc12.x86_64 package: epiphany-2.28.2-1.fc12 rating: 4 reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1.Just started Epiphay. It opened on the designated site for a second then crashed 2. 3.
Created attachment 414038 [details] File: backtrace
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. reboot machine ("reboot" as root) 2. let update of 1:java-1.6.0-openjdk-plugin-1.6.0.0-38.b18.fc12.x86_64 complete 3. start epiphany 4. let choose "recover" session. 5. watch epiphany crash
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.open epiphany 2.go to website with an image 3.click on image file to view Comment ----- this was a problem for a while, then it fixed itself, then it came back. This machine should be running the latest patches, etc.
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Move window 2. 3. Comment ----- Moved window
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. start epiphany 2. type http://www.3com.com/ in the address bar 3. watch epiphany crash
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.was in wikipedia, clicked link to a PDF file 2. 3.
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Browse Liferay-based web application (Liferay is JEE Portal software) 2. boom 3.
*** Bug 592685 has been marked as a duplicate of this bug. ***
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Go to planet gnome 2. 3. Comment ----- Went to planet gnome
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.go to skill.se 2. 3.
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Start epiphany 2. Point to page (internal page to our network) 3. Crash, in what I think is the stage where a Java applet is loaded (page html is already displayed at that moment)
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Connect to IBM Java remote management applet with epiphany 2. observe the crash 3. Comment ----- Launch IBM remote management tool
Package: epiphany-2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. link to this page with epiphany: http://66.46.93.197/epiphany-crash/ 2. that's it. 3. there is no three. Comment ----- The page shows three ways to embed an SVG image. It's a test. I suspect that epiphany doesn't like one of them, at all. There is a referenced image in the SVG that isn't present on the server. In fact it's a bad link anyway. (xlink:href="file:///home/rick/ih.png") That could have something to do with it. See the very last element in the SVG source for the embedded SVG image.
Looks like a crash in the icetea java plugin
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
My test now passes (see comment 13) with the same version of Epiphany. don't know what changed. Note that this bug is a re-assignment of the one I posted. don't remember what it was other than it caused epiphany to crash.
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.