nautilus crashed with SIGSEGV in open64()

[Shane]

Binary package hint: nautilus

I'm running karmic with all the latest updates. This has been happening for at least a week. It happens every time, I can't get nautilus to start. If it's any help, the same started happening with Epiphany after the same update (see #422283).

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 3 23:23:44 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.91-0ubuntu3
ProcCmdline: nautilus trash:
ProcEnviron:
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x7f75a46b954d <open64+29>: mov %rdi,0x8(%rsp)
 PC (0x7f75a46b954d) ok
 source "%rdi" ok
 destination "0x8(%rsp)" (0x7f759cbb5fe8) in non-writable VMA region: 0x7f759cbb5000-0x7f759cbb6000 ---p None
SegvReason: writing VMA None
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 open64 () from /lib/libc.so.6
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () 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 open64()
Uname: Linux 2.6.31-9-generic x86_64
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:open64 () from /lib/libc.so.6
safe_open (tree=<value optimized out>,
meta_tree_init (tree=0x21766f0) at metatree.c:431
meta_tree_init (tree=0x21766f0) at metatree.c:509
meta_tree_init (tree=0x21766f0) at metatree.c:509

[Bryan Quigley (bryanquigley)]

Anybody debugging this? / Anyone found a workaround? (mine currently is using dolphin)

It's still an issue for me and deleting .nautilus and .gvfs did not help.

[Chris Coulson (chrisccoulson)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=600057

[Christian Kellner (gicmo)]

It looks like your metadata store is got corrupted, leading to an infinite loop in the code.

FIX:
The fix here is to remove the metadata storage, located in: ~/.local/share/gvfs-metadata. BEFORE you do that, could you please send me (or attach) the file "~/.local/share/gvfs-metadata/home" for better analysis what is going on here.

[Bryan Quigley (bryanquigley)]

Sorry, somewhat recently this bug went away. I was trying KDE, and LXDE, maybe one of them reset what was causing the issue. Didn't notice until recently that nautilus wasn't crashing.. I'm attaching home in the hope that it might still have a record of what happened.

Feel free to close the report if there is no useful information, as I am not receiving an error anymore. Thanks!

[pothos (pothos)]

Hello!
I have the same problem, my nautilus and epiphany (without "-p") are not working after a poweroff while having much apps running. Deleting epiphany-settings doesn't work, nautilus can't start even after the update yesterday.

[Pedro Villavicencio (pedro)]

this has been fixed upstream at : http://git.gnome.org/cgit/gvfs/commit/?id=6592ecb3b95146b84072cf276eb98fba324b11ad

[dupont-denis (dupont-denis)]

Hi,
 I followed the instructions of Christian Kellner.
I copied the file ~/.local/share/gvfs-metadata/home and renamed it home_before
then I deleted all in the ~/.local/share/gvfs-metadata directory and restarted nautilus
here is the new ~/.local/share/gvfs-metadata/home renamed home_after.
on the command line window I saw error comments recorded as the attached file at_launching

All this was done with a new freshly compiled nautilus (./configure make make install) without parameters. I will reinstall nautilus from synaptic and repost something.

I activated also the aport system and joined the crash file.

Notic that if I launch the nautilus from the root account (sudo nautilus) everything is fine !!

I repost because I can attach only one file !

Denis Dupont

[dupont-denis (dupont-denis)]

home_after

[dupont-denis (dupont-denis)]

after reinstallation of nautilus and everything related from synaptic, I have on the command line:
denis@consult:~/nautilus/nautilus-2.28.1$ nautilus

(nautilus:6211): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

nautilus doesn't appear
I delete all files in directory ~/.local/share/gvfs-metadata and relaunch nautilus
denis@consult:~/nautilus/nautilus-2.28.1$ nautilus

(nautilus:6287): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
denis@consult:~/nautilus/nautilus-2.28.1$
and nautilus appear ok.

[Bryan Quigley (bryanquigley)]

I believe this has been fixed, is anyone still getting this bug?

[dupont-denis (dupont-denis)]

Than you so much Bryan,

Everything seems fine !

Denis

On Mon, Jan 24, 2011 at 6:48 AM, Bryan Quigley <email address hidden> wrote:

> I believe this has been fixed, is anyone still getting this bug?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/424043
>
> Title:
> nautilus crashed with SIGSEGV in open64()
>
> Status in GVFS:
> Fix Released
> Status in “gvfs” package in Ubuntu:
> Fix Committed
>
> Bug description:
> Binary package hint: nautilus
>
> I'm running karmic with all the latest updates. This has been
> happening for at least a week. It happens every time, I can't get
> nautilus to start. If it's any help, the same started happening with
> Epiphany after the same update (see #422283).
>
> ProblemType: Crash
> Architecture: amd64
> CrashCounter: 1
> Date: Thu Sep 3 23:23:44 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/nautilus
> Package: nautilus 1:2.27.91-0ubuntu3
> ProcCmdline: nautilus trash:
> ProcEnviron:
> LANG=en_IE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
> SegvAnalysis:
> Segfault happened at: 0x7f75a46b954d <open64+29>: mov
> %rdi,0x8(%rsp)
> PC (0x7f75a46b954d) ok
> source "%rdi" ok
> destination "0x8(%rsp)" (0x7f759cbb5fe8) in non-writable VMA region:
> 0x7f759cbb5000-0x7f759cbb6000 ---p None
> SegvReason: writing VMA None
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> open64 () from /lib/libc.so.6
> ?? () from /usr/lib/gio/modules/libgvfsdbus.so
> ?? () 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 open64()
> Uname: Linux 2.6.31-9-generic x86_64
> UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev
> sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gvfs/+bug/424043/+subscribe
>