GNOME Bugzilla – Bug 547468
crash in Home Folder:
Last modified: 2008-10-27 09:30:03 UTC
What were you doing when the application crashed? Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25.11-97.fc9.i686 #1 SMP Mon Jul 21 01:31:09 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 97566720 vsize: 97566720 resident: 38703104 share: 20635648 rss: 38703104 rss_rlim: 4294967295 CPU usage: start_time: 1218543462 rtime: 7649 utime: 5258 stime: 2391 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb8062770 (LWP 2691)] [New Thread 0xb1fb9b90 (LWP 6849)] 0x00110416 in __kernel_vsyscall ()
+ Trace 205041
----------- .xsession-errors --------------------- Saved epg data : 2991 events (164 msecs) ICE default IO error handler doing an exit(), pid = 5499, errno = 11 ** (rhythmbox-metadata:6539): WARNING **: Unknown codec ID 86022, please add here (gnome-terminal:6608): Vte-WARNING **: Kein Handler für Kontrollsequenz »device-control-string« festgelegt. ** (nautilus:2691): CRITICAL **: nautilus_file_get_symbolic_link_target_uri: assertion `nautilus_file_is_symbolic_link (file)' failed Could not find the frame base for "IA__g_spawn_command_line_sync". Could not find the frame base for "next_async_callback_wrapper". Could not find the frame base for "complete_in_idle_cb". Could not find the frame base for "g_idle_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "g_cond_timed_wait_posix_impl". Could not find the frame base for "IA__g_spawn_sync". --------------------------------------------------
Looks like a re-manifestation of bug 435823 under GIO. May be related to bug 519743.
*** Bug 548555 has been marked as a duplicate of this bug. ***
From duplicate bug 548555: "Please note that this is when I mount an ISO-file with the archive mounter (right click on a iso) and then trying to view this mounted iso. It takes a couple of seconds and a crash occurs".
> From duplicate bug 548555: > “Please note that this is when I mount an ISO-file with the archive mounter” What's the “archive mounter”? I can not reproduce this issue when manually mounting an ISO with mount -o loop.
I believe "Archive Mounter" is related to libarchive gvfs backend?
If you right click on a iso-file you can choose "open with" > archive mounter This iso now appears as a mounted volume (to the left) When I try to view this mounted image Nautilus crashes. Standard for a double-click on a iso-file should probably be the archive-mounter. If you needs an iso... ;) http://cdimage.ubuntu.com/daily/current/
I get a similar crash as well when using the Archive Mounter (which apparently starts a gvfsd-archive process). This happens on Ubuntu 8.10 alpha, with gvfs 1.0.1-0ubuntu1, when mounting a tgz archive. The archive contains some symlinks in deep subfolders, and when navigating into the hierarchy, Nautilus reproducibly crashes. ~/.xsession-errors shows the crash like this: ** (nautilus:5812): CRITICAL **: nautilus_file_get_symbolic_link_target_uri: assertion `nautilus_file_is_symbolic_link (file)' failed *** glibc detected *** nautilus: free(): invalid pointer: 0xb7429140 *** ======= Backtrace: ========= The backtrace doesn't have much debug info, though. Before that part, there's lots of output apparently from gvfsd-archive (at least the PID matches): ** (process:5931): WARNING **: FIXME: follow symlinks send_reply(0x82ae958), failed=0 () backend_dbus_handler org.gtk.vfs.Mount:Enumerate Queued new job 0x82b6640 (GVfsJobEnumerate) ** (process:5931): WARNING **: FIXME: follow symlinks send_reply(0x82b6640), failed=0 () backend_dbus_handler org.gtk.vfs.Mount:QueryInfo Queued new job 0x82ae9a8 (GVfsJobQueryInfo) ** (process:5931): WARNING **: FIXME: follow symlinks send_reply(0x82ae9a8), failed=0 () backend_dbus_handler org.gtk.vfs.Mount:Enumerate Queued new job 0x82b7010 (GVfsJobEnumerate) send_reply(0x82b7010), failed=1 (Die Datei ist kein Ordner) backend_dbus_handler org.gtk.vfs.Mount:CreateDirectoryMonitor Queued new job 0x82afb50 (GVfsJobCreateMonitor) send_reply(0x82afb50), failed=1 (Vorgang wird vom Backend nicht unterstützt) backend_dbus_handler org.gtk.vfs.Mount:Enumerate Queued new job 0x82b70d8 (GVfsJobEnumerate) ** (process:5931): WARNING **: FIXME: follow symlinks send_reply(0x82b70d8), failed=0 () backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo Queued new job 0x82afb98 (GVfsJobQueryFsInfo) send_reply(0x82afb98), failed=0 () backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo Queued new job 0x82afc00 (GVfsJobQueryFsInfo) send_reply(0x82afc00), failed=0 () backend_dbus_handler org.gtk.vfs.Mount:CreateDirectoryMonitor Queued new job 0x82afc48 (GVfsJobCreateMonitor) send_reply(0x82afc48), failed=1 (Vorgang wird vom Backend nicht unterstützt) backend_dbus_handler org.gtk.vfs.Mount:Enumerate Queued new job 0x82b70d8 (GVfsJobEnumerate) ** (process:5931): WARNING **: FIXME: follow symlinks send_reply(0x82b70d8), failed=0 () The logged PID is for this process: ~$ ps -Af | grep 5931 oliver 5931 1 0 20:58 ? 00:00:01 /usr/lib/gvfs/gvfsd-archive file=file:///home/oliver/Desktop/Xlib.tgz Btw. the gvfsd-archive stays alive also after the Nautilus crash. gvfs-tree displays the archive content without crashing, but displays odd information for the symlinks (excerpt): | `-- xfree86.cfg |-- icons | |-- default | | `-- index.theme | |-- handhelds | | `-- cursors | | |-- 08e8e1c95fe2fc01f976f1e063a24ccd | | | [Die Datei ist kein Ordner] | | |-- X_cursor | | |-- arrow | | | [Die Datei ist kein Ordner] | | |-- based_arrow_down | | |-- based_arrow_up Here, 08e8e1c95fe2fc01f976f1e063a24ccd and arrow are symlinks to "left_ptr_watch" and "right_ptr", respectively. The "[Die Datei ist kein Ordner]" text could be translated as "The file is not a folder". gvfs-ls displays the archive contents correctly as well (excerpt): $ gvfs-ls -l archive://file%3A%2F%2F%2Fhome%2Foliver%2FDesktop%2FXlib.tgz/lib/X11/icons/handhelds/cursors/ 08e8e1c95fe2fc01f976f1e063a24ccd 0 (symlink) top_left_arrow 0 (symlink) tcross 0 (symlink) plus 0 (symlink) draft_small 0 (symlink) draft_large 0 (symlink) crosshair 0 (symlink) cross_reverse 0 (symlink) arrow 0 (symlink) xterm 1088 (regular) watch 1152 (regular)
Yup.. its still there. I can open a mini.iso but not a "full size". Nautilus-scripts works just fine http://www.ubuntugeek.com/mount-and-unmout-iso-images-without-burning-them.html Kernel loop untested.
2008-10-22 Alexander Larsson <alexl@redhat.com> * libnautilus-private/nautilus-file.c (nautilus_file_get_symbolic_link_target_uri/path): Don't assert on symbolic links always marked as symlinks. Some broken backends will give this (like the archive backend). Fixes crash in #547468
*** Bug 551346 has been marked as a duplicate of this bug. ***