As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: epiphany-browser (Ubuntu)
Status: Needs Info => Rejected
--
[a
** Changed in: epiphany-browser (Ubuntu)
Importance: Undecided => Medium
--
[apport] epiphany crashed with SIGSEGV in raise()
https://launchpad.net/bugs/82447
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
if you still have the complete crash file to /var/crash you can apport-
unpack it somewhere and use gdb on the CoreDump to get a debug
backtraceAffects
--
[apport] epiphany crashed with SIGSEGV in raise()
https://launchpad.net/bugs/82447
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.co
Sure, will do it. I hope the bug gets triggered again.
--
[apport] epiphany crashed with SIGSEGV in raise()
https://launchpad.net/bugs/82447
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thank you for your bug. The backtrace is not useful though and you did
send the CoreDump with the bug which makes it not really useful. Could
you get a backtrace with firefox-dbg and epiphany-browser-dbgsym
installed?
** Changed in: epiphany-browser (Ubuntu)
Assignee: (unassigned) => Ubuntu D
