abrt 1.0.4 detected a crash. architecture: i686 Attached file: backtrace cmdline: epiphany comment: tried to save a website component: epiphany executable: /usr/bin/epiphany kernel: 2.6.31.12-174.2.3.fc12.i686.PAE package: epiphany-2.28.2-1.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault) release: Fedora release 12 (Constantine) How to reproduce ----- 1.open www.techcrunch.com 2.ctrl-s to save it 3.boom
Created attachment 386989 [details] File: backtrace
How to reproduce ----- 1. Epiphany browser : open http://fr.wikipedia.org/wiki/Composition_d'un_sinogramme 2. Save as Comment ----- Epiphant crashed but saved properly the page. (I can open it locally with another browser.) Nevertheless the crash may be reproduced easily - at least, on my PC.
How to reproduce ----- 1. When save a visited html page 2. 3.
Thread 1 (Thread 11922): #0 0x00000000 in ?? () No symbol table info available. #1 0x00bb20b9 in replace_async_thread (res=<value optimized out>, object=<value optimized out>, cancellable=<value optimized out>) at gfile.c:5094 stream = <value optimized out> error = 0x0 #2 0x00bd1bda in run_in_thread (job=<value optimized out>, c=<value optimized out>, _data=<value optimized out>) at gsimpleasyncresult.c:676 simple = 0x9147360 [GSimpleAsyncResult] source = <value optimized out> #3 0x00bc6054 in io_job_thread (data=<value optimized out>, user_data=<value optimized out>) at gioscheduler.c:182 job = 0x9143030 result = <value optimized out> #4 0x007b90e7 in g_thread_pool_thread_proxy (data=<value optimized out>) at gthreadpool.c:265 task = 0x9143030 pool = 0x90f54e8 #5 0x007b7a50 in g_thread_create_proxy (data=<value optimized out>) at gthread.c:635 thread = 0x9281920 __PRETTY_FUNCTION__ = "g_thread_create_proxy" #6 0x0071fab5 in start_thread (arg=<value optimized out>) at pthread_create.c:297 __res = <value optimized out> __ignore1 = 1 __ignore2 = 150993920 now = <value optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {7540724, 0, 4001536, -1398479928, 1457347636, -51538067}, mask_was_saved = 0}}, priv = {pad = { 0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = <value optimized out> pagesize_m1 = <value optimized out> freesize = <value optimized out> #7 0x00eb3dce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 No locals. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 577594 has been marked as a duplicate of this bug. ***
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.