nautilus crashed with SIGSEGV immediately after start up

StacktraceTop:nautilus_desktop_update_metadata_from_gconf (file=0xa2c48e0,
nautilus_desktop_set_metadata_string (file=0xa2c48e0,
nautilus_desktop_directory_file_set_metadata (
nautilus_file_set_metadata (file=0xa2c48e0,
save_spatial_data (slot=0xa2bb000)

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=589520

Bug persists in Karmic alpha 3.

I do not experience this crash with Compiz disabled.

I am experiencing this bug in alpha 3 every time I boot.

I don't know if it is related, but every time I boot now, it tries to map my Windows partition and needs me to type in my password.

This is the last part of my strace on nautilus, sda1 is my Vista partition (I AM working on getting rid of it ;)):

open("/dev/sda", O_RDWR|O_NONBLOCK|O_LARGEFILE) = -1 EACCES (Permission denied)
open("/dev/sr0", O_RDWR|O_NONBLOCK|O_LARGEFILE) = 24
ioctl(24, SG_IO, {'S', SG_DXFER_FROM_DEV, cmd[6]=[12, 00, 00, 00, 24, 00], mx_sb_len=19, iovec_count=0, dxfer_len=36, timeout=0, flags=0, data[36]=["\5\200\0052[\0\0\0ATAPI DVD A DH20A3P "...], status=00, masked_status=00, sb[0]=[], host_status=0, driver_status=0, resid=0, duration=0, info=0}) = 0
close(24) = 0
sched_get_priority_min(SCHED_OTHER) = 0
sched_get_priority_max(SCHED_OTHER) = 0
mmap2(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0xb5120000
mprotect(0xb5120000, 4096, PROT_NONE) = 0
clone(child_stack=0xb5920414, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xb5920bd8, {entry_number:6, base_addr:0xb5920b70, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0xb5920bd8) = 14772
futex(0xb76cb790, FUTEX_WAKE_PRIVATE, 1) = 1
open("/dev/sda1", O_RDWR|O_NONBLOCK|O_LARGEFILE) = -1 EACCES (Permission denied)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++

Experienced this on Karmic AMD64 after latest update, 2.6.31-6-generic #25-Ubuntu SMP Fri Aug 14 16:28:28 UTC 2009 x86_64, crash file attached

Seb, there's a patch in the upstream bug which is said to help. Can you please look into applying it?

http://bugzilla-attachments.gnome.org/attachment.cgi?id=141645

The bug has persisted into alpha4

I experienced this bug in Jaunty right now..

Happening every time I boot into Karmic

Stop sending me this crap.

On Sun, Aug 30, 2009 at 11:34 AM, DougieFresh4U <email address hidden> wrote:

> Happening every time I boot into Karmic
>
> --
> nautilus crashed with SIGSEGV immediately after start up
> https://bugs.launchpad.net/bugs/403549
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Nautilus: New
> Status in “nautilus” package in Ubuntu: Fix Committed
> Status in nautilus in Ubuntu Karmic: Fix Committed
>
> Bug description:
> Binary package hint: nautilus
>
> On Alpha 2 of Karmic Koala. Immediately after the computer had started up,
> a crash notification appeared for nautilus.
> Using an Acer Aspire One.
>
> ProblemType: Crash
> Architecture: i386
> Date: Thu Jul 23 00:42:19 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/nautilus
> Package: nautilus 1:2.27.4-0ubuntu2
> ProcCmdline: nautilus
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
> SegvAnalysis:
> Segfault happened at: 0x8197c56: mov (%ecx),%eax
> PC (0x08197c56) ok
> source "(%ecx)" (0x00000000) not located in a known VMA region (needed
> readable region)!
> destination "%eax" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> Title: nautilus crashed with SIGSEGV
> Uname: Linux 2.6.31-3-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>

--
R.L.Buie

I was experiencing this bug on every login. It seems I got rid of it by manually cleaning up my gconf database. Unfortunately I did loads of changes at once, so I can't say which one was the champion. What I did was removing old keys that were not assosiated with a schema anymore, including (but not limited to) /apps/nautilus/. I also reset several entries to their default values. After next login, to my surprise nautilus didn't crash anymore.

Maybe somebody suffering from this bug wants to do some gconf cleanup in smaller steps to be able to tell which key or value was the bad guy.

The bug has persisted into alpha5 and it is happening every time I boot into Karmic alpha 5.
Laptop ASUS Z53E

Same here fresh install of A5 on Asus A7K laptop.

This bug was fixed in the package nautilus - 1:2.27.92-0ubuntu1

---------------
nautilus (1:2.27.92-0ubuntu1) karmic; urgency=low

  * New upstream version:
    - Fix crash on logout (lp: #403549)
    - Translation updates
    - Always show app icon in open with popup menu
    - fix duplicate id in ui file
    - Fix warning in new power manager inhibiting
  * debian/patches/91_git_change_fix_inhibit_issue.patch,
    debian/patches/92_git_change_fix_preferences_crash.patch:
    - those changes are in the new version
  * debian/patches/90_relibtoolize.patch:
    - new version update

 -- Sebastien Bacher <email address hidden> Mon, 07 Sep 2009 13:43:53 +0200

Works fine in my Packard Bell dot now

Vlada Krunic, don't just set bugs to another status without commenting on why you do that.

Just experiences this bug after boot-up in Karmic Beta, 64 bit.

Just upgraded to Karmic, and this has happened twice now.

Just experiences this bug after boot-up in Karmic, 64 bit.

If this is still a problem for you, please leave a comment on the upstream bugtracker at https://bugzilla.gnome.org/show_bug.cgi?id=589520. Thanks.