nautilus crashed with SIGSEGV in nautilus_icon_container_search_entry_flush_timeout()

Bug #811347 reported by Cristian Aravena Romero
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Move files in nautilus and crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Jul 15 21:42:59 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: nautilus -n
ProcEnviron:
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4c026e <nautilus_icon_container_search_entry_flush_timeout+14>: mov 0x390(%rax),%rdi
 PC (0x004c026e) ok
 source "0x390(%rax)" (0xaaaaaaaaaaaaae3a) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_icon_container_search_entry_flush_timeout (container=0x1fa6650) at nautilus-icon-container.c:4947
 g_timeout_dispatch (source=0x7f015017a9e0, callback=<value optimized out>, user_data=<value optimized out>) at /build/buildd/glib2.0-2.29.10/./glib/gmain.c:3946
 g_main_dispatch (context=0x1bfbbb0) at /build/buildd/glib2.0-2.29.10/./glib/gmain.c:2473
 g_main_context_dispatch (context=0x1bfbbb0) at /build/buildd/glib2.0-2.29.10/./glib/gmain.c:3046
 g_main_context_iterate (context=0x1bfbbb0, block=<value optimized out>, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.29.10/./glib/gmain.c:3124
Title: nautilus crashed with SIGSEGV in nautilus_icon_container_search_entry_flush_timeout()
UpgradeStatus: Upgraded to oneiric on 2011-07-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Duplicated Bug #804133 ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.