GNOME Bugzilla – Bug 737091
Segmentation fault at the opening
Last modified: 2014-09-21 20:51:16 UTC
I'm running ubuntu 14.10 Utopic Unicorn with gnome-staging ppa activated (1). This means that I've the version 3.12.1-0ubuntu1~utopic1. To reproduce the bug : - Try to launch the application from the start menu What happened : no window appear What is expected : totem window should appear. When I'm trying to launch totem in a terminal I get the following messages : sebastien@utopic:~$ totem (totem:6359): GLib-GObject-WARNING **: The property GtkTreeView:rules-hint is deprecated and shouldn't be used anymore. It will be removed in a future version. (totem:6359): Gtk-CRITICAL **: Error building template class 'TotemMainToolbar' for an instance of type 'TotemMainToolbar': Template parent type `GtkBox' does not match instance parent type `GtkHeaderBar'. (totem:6359): Gtk-CRITICAL **: gtk_widget_set_no_show_all: assertion 'GTK_IS_WIDGET (widget)' failed (totem:6359): Gtk-CRITICAL **: gtk_widget_set_no_show_all: assertion 'GTK_IS_WIDGET (widget)' failed (totem:6359): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:6359): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:6359): Gtk-CRITICAL **: gtk_stack_add_named: assertion 'GTK_IS_STACK (stack)' failed (totem:6359): Gtk-CRITICAL **: gtk_stack_add_named: assertion 'GTK_IS_STACK (stack)' failed (totem:6359): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:6359): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:6359): GLib-GObject-CRITICAL **: g_object_bind_property_full: assertion 'G_IS_OBJECT (source)' failed (totem:6359): GLib-GObject-CRITICAL **: g_object_bind_property_full: assertion 'G_IS_OBJECT (source)' failed Erreur de segmentation (core dumped) (1) https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 729479 ***