Ubuntu
nautilus package

nautilus crashed with SIGSEGV in nautilus_desktop_update_metadata_from_gconf()

Bug #424663 reported by Steven Myers on 2009-09-05

This bug report is a duplicate of: Bug #403549: nautilus crashed with SIGSEGV immediately after start up. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: nautilus

Karmic Upgrade Resulted.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Sep 4 22:35:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.27.91-0ubuntu3
ProcCmdline: nautilus
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.51-generic
SegvAnalysis:
Segfault happened at: 0x81986a6 <nautilus_desktop_update_metadata_from_gconf+214>: mov (%ecx),%eax
PC (0x081986a6) 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:
nautilus_desktop_update_metadata_from_gconf (file=0x95830e0,
nautilus_desktop_set_metadata_string (file=0x95830e0,
nautilus_desktop_directory_file_set_metadata (
nautilus_file_set_metadata (file=0x95830e0,
nautilus_spatial_window_save_scroll_position (
Title: nautilus crashed with SIGSEGV in nautilus_desktop_update_metadata_from_gconf()
Uname: Linux 2.6.28-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags:

Revision history for this message

Steven Myers (stevenmyers) wrote on 2009-09-05:

usr_lib_nautilus.txt Edit (281 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-05: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #403549, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.