epiphany 2.28.0 crashes when actions is clicked

[Clara]

Binary package hint: epiphany

epiphany browser webkit based 2.28.0 crashes when you clic on actions in the edit menu. It occurs in ubuntu 9.10 karmic koala after installing extensions 2.28.0-1 from synaptic.

[Clara (claracagigal)]

I attachad what i obtain when i run epiphany from console and click on "edit, actions": clara@clara1:~$ epiphany

(epiphany-browser:7024): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.22.2/gobject/gsignal.c:2270: signal `ge-context-menu' is invalid for instance `0xa488010'

(epiphany-browser:7024): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.22.2/gobject/gsignal.c:2270: signal `ge_context_menu' is invalid for instance `0xa120278'

** (epiphany-browser:7024): WARNING **: Unable to load UI file /usr/share/epiphany-extensions/glade/actions-editor.glade: Nombre de elemento raíz no válido: «glade-interface»

** (epiphany-browser:7024): CRITICAL **: ephy_dialog_get_controls: assertion `info != NULL' failed

(epiphany-browser:7024): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(epiphany-browser:7024): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(epiphany-browser:7024): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(epiphany-browser:7024): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(epiphany-browser:7024): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(epiphany-browser:7024): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(epiphany-browser:7024): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(epiphany-browser:7024): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(epiphany-browser:7024): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(epiphany-browser:7024): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(epiphany-browser:7024): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(epiphany-browser:7024): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(epiphany-browser:7024): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(epiphany-browser:7024): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_tree_view_set_model: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_tree_view_append_column: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_tree_view_set_search_column: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_tree_selection_set_mode: assertion `GTK_IS_TREE_SELECTION (selection)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_tree_selection_count_selected_rows: assertion `GTK_IS_TREE_SELECTION (selection)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed

(epiphany-browser:7024): Gtk-CRITICAL **: gtk_...

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Clara (claracagigal)]

I have tried to send the crash report of epiphany when i click on
actions in ubuntu karmic, file named :
_usr_bin_epiphany-browser.1000.crash, following the advice of your mail.
But i can't because i have now installed epiphany 2.29.3 release (with
this release the problem persists: when click on actions epiphany
crashes) and when i try to send the report a window appears saying
"impossible to send the file, this is not a genuine ubuntu package".
I have tried to send an e-mail to the reply -to- address adjoining the
file but it has 15 Mb and unless i compress it to 11 Mb with gzip,
evolution says to me that i have exceeded the capacity.
So i don't know how i can send the crash report file.

El mié, 09-12-2009 a las 19:17 +0000, Pedro Villavicencio escribió:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. However, your crash report is either missing or
> challenging to deal with as a ".crash" file. Please follow these
> instructions to have apport report a new bug about your crash that can
> be dealt with by the automatic retracer.
>
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart.
>
> If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
> If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
>
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently. Thanks in advance for your cooperation and understanding.
>
> ** Changed in: epiphany-browser (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: epiphany-browser (Ubuntu)
> Status: New => Invalid
>

[Clara (claracagigal)]

I send to you the crash report of epiphany splitted in 4 parts

[Clara (claracagigal)]

I send to you the crash report of epiphany splitted in 4 parts: part 2

[Clara (claracagigal)]

I send to you the crash report of epiphany splitted in 4 parts: part 3

[Clara (claracagigal)]

I send to you the crash report of epiphany splitted in 4 parts: part 4

[Ben Bacarisse (launchpad-bsb)]

I was attempting to report this when ubuntu-bug showed this identical problem. I will attach the output of gdb session made after installing epiphany-browser-dbg but I don't know if the correct action is to re-open this bug or file a new one.

I was getting timeout using ubuntu-bug so I don't know if I will be able to do it that way.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of Epiphany Browser is available in both Lucid and Maverick and we are wondering if this is still reproducible in any of those versions, May you please test and give us of feedback about it? Thanks in advance.

[Ben Bacarisse (launchpad-bsb)]

This bug appears to be fixed for me in version 2.30.2. It may have been fixed before tha version but i was only recently prompted to try.

[Pedro Villavicencio (pedro)]

closing the bug, thank you.