Gtk & Glib CRITICAL messages at startup (regression)

[jimav]

Every time nautilus starts it emits several "CRITICAL" assertion error messages. This is a regression (didn't happen in Ubuntu 14.10)

$ nautilus

(nautilus:4543): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(nautilus:4543): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:4543): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 27 10:17:38 2015
GsettingsChanges:
 b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified', 'where']"
 b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed']"
InstallationDate: Installed on 2013-08-06 (659 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Hao Hu (haohu94)]

I can confirm this still happens in 15.10.

[MCE (mau-castro)]

I find a way to overcome the problem.

Just run:

1. sudo gdk-pixbuf-query-loaders --update-cache
2. And then restart Nautilus.

See more info at https://bbs.archlinux.org/viewtopic.php?id=197793

I am using 15.10 and had the issue.

[jimav (james-avera)]

If that reflects the underlying problem (out of date pixmaps or something), then the installer for nautilus should perform this action automatically so users will not see the bug.

[RD976 (rdear976)]

Identical problem still exists in 16.04.

"sudo gdk-pixbuf- ..." does not overcome the problem. ("command not found')

[André Desgualdo Pereira (desgua)]

After installing `libgdk-pixbuf2.0-dev` I was able to run `sudo gdk-pixbuf-query-loaders --update-cache` but it doesn't fix the problem.

[Sebastien Bacher (seb128)]

Do you still see that problem in newer versions?

[jimav (james-avera)]

The GTK warning no longer happes for me on Ubuntu 18.04.01. However a different message is written to the terminal at startup:

Initializing nautilus-image-converter extension

(unrelated)

[Sebastien Bacher (seb128)]

That other message looks like not an error but normal info from a plugin you installed, closing since the initial problem is resolved