You are not logged in.

#1 2012-04-25 22:40:36

bnb2235
Member
Registered: 2011-02-13
Posts: 119

Nautilus segmentation fault with netfs

Hello,
This is more of a story than a request for help. Maybe it helps someone.
I was recently using "network" with gnome. With gonome 3.4, I used networkmanager rather than renaming /usr/share/gnome-shell/js/ui/status/network.js (new networkmanager dependency in gnome)
I don't think networkmanger itself caused any problems, but nautilus was not working well for me while network shares were mounted (maybe just the one mounted to my home directory) Anyway, I tweaked some of the settings with gnome-tweak-tool. On the desktop page, I turned off "Show mounted volumes on the desktop" (nautilus is not managing the desktop) With this setting, nautilus would not start

** (nautilus:7955): WARNING **: libpng14.so.14: cannot open shared object file: No such file or directory
(nautilus:7955): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_sort_key: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_is_shadowed: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_volume: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_default_location: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_file_is_native: assertion `G_IS_FILE (file)' failed
(nautilus:7955): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:7955): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:7955): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GMount'
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_default_location: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_icon: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_file_get_uri: assertion `G_IS_FILE (file)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_name: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_file_get_parse_name: assertion `G_IS_FILE (file)' failed
(nautilus:7955): Gtk-CRITICAL **: gtk_icon_theme_lookup_by_gicon: assertion `G_IS_ICON (icon)' failed
(nautilus:7955): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:7955): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:7955): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_default_location: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_icon: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_file_get_uri: assertion `G_IS_FILE (file)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_get_name: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_file_get_parse_name: assertion `G_IS_FILE (file)' failed
(nautilus:7955): Gtk-CRITICAL **: gtk_icon_theme_lookup_by_gicon: assertion `G_IS_ICON (icon)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_can_eject: assertion `G_IS_MOUNT (mount)' failed
(nautilus:7955): GLib-GIO-CRITICAL **: g_mount_can_unmount: assertion `G_IS_MOUNT (mount)' failed
Segmentation fault

With "Show mounted volumes on the desktop" turned on (not sure why this setting matters if nautilus is not managing the desktop), nautilus does start. When I mount or unmount any usb stick, nautilus blows up with segmentation fault. When I disconnect from the network (using networkmanager), I have no troubles with usb. For reference, my fstab looks like this:
nas:/pkg /var/cache/pacman/pkg nfs4 async 0 0
nas:/sync /var/lib/pacman/sync nfs4 async 0 0
nas:/bryan /home/bryan/Data nfs4 async 0 0

With these fstab settings, I have an entry "Data" under the places in nautilus (but no entry for pkg or sync). I guess this is because the Data mount is inside my home directory?

So I implemented a workaround. I created a folder at /.bryan, set the appropriate permissions and ownerships, created a symbolic link in /home/bryan (ln -s -T /.bryan Data) and changed my fstab (nas:/bryan /.bryan nfs4 async 0 0) I guess I could have instead created a bind mount, but the symbolic link was easy.

Now there is no entry under Network in naultilus places (desirable to me), and no more removable media popup in the bottom right corner of gnome desktop (since "Data" was considered removable media in my original configuration).

Nautilus is working fine in all cases now (at least what I have tested thus far). I guess there is a bug (or two) in nautilus to make this story possible, but at least there is a workaround...

I still don't understand why I get "libpng14.so.14: cannot open shared object file: No such file or directory" since my system is up to date and I think I followed all the instructions regarding this anouncement.

Thanks for reading :-)

Offline

#2 2012-04-27 11:16:36

alexdaums
Member
Registered: 2011-09-16
Posts: 4

Re: Nautilus segmentation fault with netfs

up

I have the same problem!

Last edited by alexdaums (2012-04-27 11:17:01)

Offline

#3 2012-05-07 18:52:51

surlyjake
Member
Registered: 2012-05-05
Posts: 1

Re: Nautilus segmentation fault with netfs

I was having the same problem. Newest package of nautilus (3.4.1-2) fixed it for me: https://projects.archlinux.org/svntogit … 10181cd8af.

Offline

Board footer

Powered by FluxBB