epiphany-browser crashed with SIGSEGV in g_closure_invoke()

[Lecomte François]

Binary package hint: epiphany-browser

1) Karmic amd64. The system is up-to-date. No external repositories.
2) epiphany-browser 2.28.0-4ubuntu1 with epiphany-extensions 2.28.0-1
3&4) I wanted to quit epiphany while the extensions window was open. Apport detected that it crashed instead of quitting. (that’s not a big issue for me. ;-) )

ProblemType: Crash
Architecture: amd64
Date: Sat Oct 10 10:24:51 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/epiphany-browser
NonfreeKernelModules: fglrx
Package: epiphany-browser 2.28.0-4ubuntu1
ProcCmdline: epiphany-browser
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
SegvAnalysis:
 Segfault happened at: 0x7fb4cb3a4e1d: mov 0x20(%rax),%rdi
 PC (0x7fb4cb3a4e1d) ok
 source "0x20(%rax)" (0x00210fe0) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: epiphany-browser
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit_by_name ()
Title: epiphany-browser crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:ephy_actions_extension_finalize (object=0x1ea3140)
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
g_signal_emit_by_name ()

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Victor Vargas (kamus)]

Please could you check if this issue is still affecting you under latest release 2.30.2-1ubuntu1 included in Ubuntu Lucid?

[Pedro Villavicencio (pedro)]

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!.