Bug 631453 – crash in File Browser: I was closing nautilus

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 631453 - crash in File Browser: I was closing nautilus


Summary:	crash in File Browser: I was closing nautilus


Status:	RESOLVED DUPLICATE of bug 619808

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.30.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-10-05 16:40 UTC by oscar.getstring
Modified:	2010-10-05 19:20 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description oscar.getstring 2010-10-05 16:40:01 UTC

Version: 2.30.1

What were you doing when the application crashed?
I was closing nautilus


Distribution: Unknown
Gnome Release: 2.30.2 2010-07-17 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.35.2-local #1 SMP PREEMPT Fri Aug 20 00:08:23 IST 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaGilouche
Icon Theme: gnome-brave
GTK+ Modules: gnomebreakpad

Memory status: size: 269426688 vsize: 269426688 resident: 42856448 share: 28323840 rss: 42856448 rss_rlim: 18446744073709551615
CPU usage: start_time: 1286263870 rtime: 3311 utime: 2653 stime: 658 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0xaa5bbb70 (LWP 13121)]
0xb7761424 in __kernel_vsyscall ()

+ Trace 224018

Thread 1 (Thread 0xb6640760 (LWP 12984))

#0 __kernel_vsyscall
#1 waitpid
at ../sysdeps/unix/syscall-template.S line 82
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gspawn.c line 386
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gspawn.c line 700
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 tags_view_add_tags_cb
at tracker-tags-view.c line 411
#7 callback_with_gptrarray
at tracker.c line 364
#8 org_freedesktop_Tracker1_Resources_sparql_query_async_callback
at tracker-resources-glue.h line 81
#9 ??
from /usr/lib/libdbus-glib-1.so.2
#10 ??
from /lib/libdbus-1.so.3
#11 ??
from /lib/libdbus-1.so.3
#12 dbus_connection_dispatch
from /lib/libdbus-1.so.3
#13 ??
from /usr/lib/libdbus-glib-1.so.2
#14 g_main_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 1960
#15 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2513
#16 g_main_context_iterate
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2591
#17 IA__g_main_loop_run
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2799
#18 IA__gtk_main
at /build/buildd-gtk+2.0_2.20.1-1+b1-i386-jmql5R/gtk+2.0-2.20.1/gtk/gtkmain.c line 1219
#19 main
at nautilus-main.c line 544


	Inferior 1 [process 12984] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (22 sec old) ---------------------
open_browser = False
Create Settings object...
Reading configuration from GConf...
Loaded configuration: 
ask_confirmation = False
show_notification = True
preset = paste.debian.net
open_browser = False
Create Settings object...
Reading configuration from GConf...
Loaded configuration: 
ask_confirmation = False
show_notification = True
preset = paste.debian.net
open_browser = False
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2010-10-05 19:20:58 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 619808 ***