After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 723988 - Epiphany 3.11.4 crashes during opening link from external application
Epiphany 3.11.4 crashes during opening link from external application
Status: RESOLVED DUPLICATE of bug 723725
Product: epiphany
Classification: Core
Component: General
3.11.x
Other Linux
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-02-09 23:36 UTC by Maciej (Matthew) Piechotka
Modified: 2014-02-09 23:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Maciej (Matthew) Piechotka 2014-02-09 23:36:34 UTC 
[New LWP 4863]
[New LWP 4870]
[New LWP 4878]
[New LWP 4876]
[New LWP 4865]
[New LWP 4867]
[New LWP 4993]
[New LWP 4868]
[New LWP 4997]
[New LWP 4871]
[New LWP 4869]
[New LWP 4886]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: File "/usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6.0.18-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
	add-auto-load-safe-path /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6.0.18-gdb.py
line to your configuration file "/home/mpiechotka/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/mpiechotka/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"
Core was generated by `epiphany'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 233151

Thread 1 (Thread 0x7f715d68f940 (LWP 4863))

  • #0 g_type_check_instance_cast
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gobject/gtype.c line 4009
  • #1 page_created_cb
    at ephy-web-view.c line 665
  • #2 ffi_call_unix64
    at /var/tmp/portage/dev-libs/libffi-3.0.13-r1/work/libffi-3.0.13/src/x86/unix64.S line 76
  • #3 ffi_call
    at /var/tmp/portage/dev-libs/libffi-3.0.13-r1/work/libffi-3.0.13/src/x86/ffi64.c line 522
  • #4 g_cclosure_marshal_generic
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gobject/gclosure.c line 1454
  • #5 g_closure_invoke
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gobject/gclosure.c line 777
  • #6 signal_emit_unlocked_R
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gobject/gsignal.c line 3556
  • #7 g_signal_emit_valist
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gobject/gsignal.c line 3312
  • #8 g_signal_emit
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gobject/gsignal.c line 3368
  • #9 web_extension_page_created
    at ephy-embed-shell.c line 160
  • #10 emit_signal_instance_in_idle_cb
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gio/gdbusconnection.c line 3739
  • #11 g_main_dispatch
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/glib/gmain.c line 3068
  • #12 g_main_context_dispatch
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/glib/gmain.c line 3643
  • #13 g_main_context_iterate
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/glib/gmain.c line 3714
  • #14 g_main_context_iteration
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/glib/gmain.c line 3775
  • #15 g_application_run
    at /var/tmp/portage/dev-libs/glib-2.39.3/work/glib-2.39.3/gio/gapplication.c line 1685
  • #16 main
    at ephy-main.c line 488 






Comment 1


Maciej (Matthew) Piechotka





          2014-02-09 23:42:10 UTC
        



Strange - I was sure I marked it as duplicate during the similar stacktrace search.

*** This bug has been marked as a duplicate of bug 723725 ***