Bug 701029 - [abrt] epiphany-3.0.1-1.fc15: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Summary: [abrt] epiphany-3.0.1-1.fc15: Process /usr/bin/epiphany was killed by signal ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:14b1f9782502ab57bc96d6fee33...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-30 13:15 UTC by Javier Jardón
Modified: 2012-02-15 09:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-15 09:29:10 UTC
Type: ---


Attachments (Terms of Use)
File: event_log (20.10 KB, text/plain)
2011-04-30 13:15 UTC, Javier Jardón
no flags Details
File: build_ids (4.52 KB, text/plain)
2011-04-30 13:15 UTC, Javier Jardón
no flags Details
File: dsos (34.08 KB, text/plain)
2011-04-30 13:15 UTC, Javier Jardón
no flags Details
File: backtrace (60.53 KB, text/plain)
2011-04-30 13:15 UTC, Javier Jardón
no flags Details
File: maps (48.47 KB, text/plain)
2011-04-30 13:15 UTC, Javier Jardón
no flags Details

Description Javier Jardón 2011-04-30 13:15:30 UTC
abrt version: 2.0.1
executable: /usr/bin/epiphany
cmdline: epiphany
component: epiphany
uid: 500
crash_function: WebCore::FrameLoader::loadResourceSynchronously
kernel: 2.6.38.3-18.fc15.x86_64
package: epiphany-3.0.1-1.fc15
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
architecture: x86_64
username: jjardon
rating: 3
time: 1304167761
os_release: Fedora release 15 (Lovelock)

Text file: event_log, 20578 bytes
Text file: build_ids, 4633 bytes
Binary file: coredump, 1214066688 bytes
Text file: dsos, 34902 bytes
Text file: backtrace, 61978 bytes
Text file: maps, 49636 bytes

environ
-----
XDG_SESSION_ID=1
HOSTNAME=rhun.eregion
IMSETTINGS_INTEGRATE_DESKTOP=yes
SHELL=/bin/bash
TERM=dumb
HISTSIZE=1000
XDG_SESSION_COOKIE=b77201ddc0b027d49d856cef0000000d-1304067034.515946-1020029750
GNOME_KEYRING_CONTROL=/tmp/keyring-nmbOyw
IMSETTINGS_MODULE=IBus
USER=jjardon
USERNAME=jjardon
MAIL=/var/spool/mail/jjardon
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/jjardon/.local/bin:/home/jjardon/bin
DESKTOP_SESSION=gnome
QT_IM_MODULE=xim
PWD=/home/jjardon
XMODIFIERS=@im=ibus
GNOME_KEYRING_PID=1189
LANG=en_GB.utf8
GDM_LANG=en_GB.utf8
GDMSESSION=gnome
HISTCONTROL=ignoredups
HOME=/home/jjardon
SHLVL=1
LOGNAME=jjardon
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ykDpiDDakP,guid=52c989de7ce5e39cb8914ee900000021
'LESSOPEN=||/usr/bin/lesspipe.sh %s'
WINDOWPATH=1
XDG_RUNTIME_DIR=/run/user/jjardon
DISPLAY=:0
G_BROKEN_FILENAMES=1
XAUTHORITY=/var/run/gdm/auth-for-jjardon-PQdxnR/database
_=/usr/bin/gnome-session
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1197,unix/unix:/tmp/.ICE-unix/1197
SSH_AUTH_SOCK=/tmp/keyring-nmbOyw/ssh
GPG_AGENT_INFO=/tmp/keyring-nmbOyw/gpg:0:1
GJS_DEBUG_OUTPUT=stderr
'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
ORBIT_SOCKETDIR=/tmp/orbit-jjardon
DESKTOP_STARTUP_ID=gnome-shell-1283-rhun.eregion-epiphany-17_TIME44446665
GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/epiphany.desktop
GIO_LAUNCHED_DESKTOP_FILE_PID=10344

Comment 1 Javier Jardón 2011-04-30 13:15:33 UTC
Created attachment 495964 [details]
File: event_log

Comment 2 Javier Jardón 2011-04-30 13:15:36 UTC
Created attachment 495965 [details]
File: build_ids

Comment 3 Javier Jardón 2011-04-30 13:15:39 UTC
Created attachment 495966 [details]
File: dsos

Comment 4 Javier Jardón 2011-04-30 13:15:42 UTC
Created attachment 495967 [details]
File: backtrace

Comment 5 Javier Jardón 2011-04-30 13:15:44 UTC
Created attachment 495968 [details]
File: maps

Comment 6 Martin Stransky 2012-02-15 09:29:10 UTC
We're using mozilla crash reporter tool which reports crashes directly to mozilla crash database now, ABRT is no longer used for mozilla packages.

This is an automated bug change. If you can reproduce the crash reliably (you have testcase, page where it crashes or so), please reopen this bug and assign it directly to me.

Thanks.


Note You need to log in before you can comment on or make changes to this bug.