It's coming to a year since I reported this issue. Below are the messages 
plaguing my syslog when Nautilus is started and when I press the items on the 
left are pressed. The look to be the same issues. I am using:
kernel 4.4.0-64-generic
nautilus 1:3.18.4.is.3.14.3-0ubuntu5.
libglib-perl  3:1.320-2 
libglib2.0-0:amd64 2.48.2-0ubuntu1
Can an importance be defined and someone fix them?
 
Mar 12 22:14:46 Eliot gnome-session[2264]: message repeated 5 times: [ 
(nautilus:2558): Gtk-CRITICAL **: gtk_container_foreach: assertion 
'GTK_IS_CONTAINER (container)' failed]
Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GIO-CRITICAL 
**: g_dbus_interface_skeleton_unexport: assertion 
'interface_->priv->connections != NULL' failed
Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GIO-CRITICAL 
**: g_dbus_interface_skeleton_unexport: assertion 
'interface_->priv->connections != NULL' failed
Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): Gtk-CRITICAL **: 
gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): 
GLib-GObject-WARNING **: invalid (NULL) pointer instance
Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 12 22:15:05 Eliot dbus[1432]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 12 22:15:05 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: 
nautilus_menu_provider_get_background_items: assertion 
'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Mar 12 22:15:05 Eliot systemd[1]: Starting Hostname Service...
Mar 12 22:15:05 Eliot dbus[1432]: [system] Successfully activated service 
'org.freedesktop.hostname1'
Mar 12 22:15:05 Eliot systemd[1]: Started Hostname Service.
Mar 12 22:15:13 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: 
nautilus_menu_provider_get_background_items: assertion 
'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Mar 12 22:15:15 Eliot gnome-session[2264]: message repeated 2 times: [ ** 
(nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: 
assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed]
Mar 12 22:15:16 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: 
nautilus_menu_provider_get_background_items: assertion 
'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1582496

Title:
  GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I submitted this question a week but did not receive an answer or
  advice to solving them. https://answers.launchpad.net/ubuntu/+source
  /gnome-session/+question/293479

  These failures are still plaguing my syslog every time I activate
  Nautilus.

  Appreciate help to resolve these failures.

  
  ============ Earlier question ============================
  After a recent updating, I notice these failures in the systemlogs. 

  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: 
(zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'object->ref_count > 0' failed
  May  9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed

  The last three failures appears whenever I activate nautilus.
  Nautilus will appear and work as usual.

  How can I resolve these failure notices?  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to