epiphany-gecko crashed with SIGSEGV

[[e-mail]]

Binary package hint: epiphany-browser

Simply open Epiphany and paste the following URL: http://beta.flowgram.com/f/p.html#2qi3k8eicrfgkv

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Jun 25 11:20:09 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/epiphany-gecko
NonfreeKernelModules: nvidia
Package: epiphany-gecko 2.22.2-0ubuntu0.8.04.2
PackageArchitecture: i386
ProcCmdline: epiphany-browser
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: epiphany-browser
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so
 ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so
 ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so
 ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so
Title: epiphany-gecko crashed with SIGSEGV
Uname: Linux 2.6.24-19-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner users video

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[[e-mail] (schickb)]

The crash in in /usr/lib/flashplugin-nonfree/libflashplayer.so which doesn't have symbols. But I installed symbols and got a backtrace for everything up to that point.

[Pedro Villavicencio (pedro)]

re assigning to flashplugin-nonfree

[Michele Mangili (mangilimic)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!