nautilus crashed with SIGSEGV in g_mount_spec_match_with_path()

StacktraceTop:
 items_equal (a=0x0, b=0x99bd348) at gmountspec.c:344
 g_mount_spec_match_with_path (mount=0x998bc30,
 g_daemon_vfs_get_file_for_uri (vfs=0x10,
 ?? () at gdaemonvfs.c:747
 g_daemon_file_read_finish (file=0x99bd360, res=0x0,

Thanks for the report Rickard, this report was filed with nautilus 2.29.92 we're wondering if this is still an issue with 2.30 on Lucid, could you please test the same and comment back? Thanks in advance.

Pedro: Yes, it seems so. Please see bug https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/558696 .

Known upstream as well, you can track it here: https://bugzilla.gnome.org/show_bug.cgi?id=511571

Flavio you seems to be able to reproduce this with latest, may you tell us a few easy steps on how to do it? Thanks.

I can't reproduce it with ubuntu fully up-to-date now (not that I ever knew how to trigger it, is was simply always triggered here on login).

there has been no such issue reported in years, assuming it doesn't exist in the current version of the code and closing

Well, I reported it 8 years ago...
/R

> 17 mars 2018 kl. 17:00 skrev Sebastien Bacher <email address hidden>:
>
> there has been no such issue reported in years, assuming it doesn't
> exist in the current version of the code and closing
>
> ** Changed in: nautilus (Ubuntu)
> Status: Triaged => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/528299
>
> Title:
> nautilus crashed with SIGSEGV in g_mount_spec_match_with_path()
>
> Status in Nautilus:
> Expired
> Status in nautilus package in Ubuntu:
> Invalid
>
> Bug description:
> Binary package hint: nautilus
>
> 10.04
> 1:2.29.91-0ubuntu1
>
> ProblemType: Crash
> Architecture: i386
> Date: Fri Feb 26 00:22:55 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/bin/nautilus
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
> Package: nautilus 1:2.29.91-0ubuntu1
> ProcCmdline: nautilus
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
> SegvAnalysis:
> Segfault happened at: 0xb0b639: mov 0x4(%eax),%ecx
> PC (0x00b0b639) ok
> source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
> destination "%ecx" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> ?? () from /usr/lib/libgvfscommon.so.0
> g_mount_spec_match_with_path ()
> ?? () from /usr/lib/gio/modules/libgvfsdbus.so
> ?? () from /usr/lib/gio/modules/libgvfsdbus.so
> ?? () from /usr/lib/gio/modules/libgvfsdbus.so
> Title: nautilus crashed with SIGSEGV in g_mount_spec_match_with_path()
> Uname: Linux 2.6.32-14-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> XsessionErrors: (polkit-gnome-authentication-agent-1:1664): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/528299/+subscriptions