Bug 497458 – crash in Home Folder:

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 497458 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 364220

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-16 19:10 UTC by Cláudio Esperança
Modified:	2007-11-25 13:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Cláudio Esperança 2007-11-16 19:10:36 UTC

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.20.1 2007-10-22 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-gentoo-r1 #3 SMP Fri Nov 9 18:21:53 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: glass-icons

Memory status: size: 94019584 vsize: 94019584 resident: 30445568 share: 20242432 rss: 30445568 rss_rlim: 4294967295
CPU usage: start_time: 1195237446 rtime: 1092 utime: 1006 stime: 86 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d4baf0 (LWP 32581)]
[New Thread 0xb36ffb90 (LWP 7217)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 178187

Thread 1 (Thread 0xb6d4baf0 (LWP 32581))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 369
#3 IA__g_spawn_command_line_sync
at gspawn.c line 677
#4 run_bug_buddy
at gnome-breakpad.cc line 213
#5 check_if_gdb
at gnome-breakpad.cc line 283
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
#7 google_breakpad::ExceptionHandler::HandleException
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
#8 <signal handler called>
#9 __kernel_vsyscall
#10 *__GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#11 *__GI_abort
at abort.c line 88
#12 IA__g_logv
#13 IA__g_log
#14 IA__g_assert_warning
at gmessages.c line 552
#15 fm_tree_model_unref_node
at fm-tree-model.c line 1531
#16 IA__gtk_tree_model_unref_node
at gtktreemodel.c line 1372
#17 gtk_tree_model_sort_real_unref_node
at gtktreemodelsort.c line 1243
#18 IA__gtk_tree_model_unref_node
at gtktreemodel.c line 1372
#19 gtk_tree_row_reference_unref_path_helper
at gtktreemodel.c line 1859
#20 gtk_tree_row_reference_unref_path_helper
at gtktreemodel.c line 1858
#21 gtk_tree_row_reference_unref_path_helper
at gtktreemodel.c line 1858
#22 gtk_tree_row_reference_unref_path
at gtktreemodel.c line 1873
#23 IA__gtk_tree_row_reference_free
at gtktreemodel.c line 2100
#24 gtk_tree_selection_real_unselect_all
at gtktreeselection.c line 1043
#25 _gtk_tree_selection_internal_select_node
at gtktreeselection.c line 1318
#26 gtk_tree_view_real_set_cursor
at gtktreeview.c line 12542
#27 IA__gtk_tree_view_set_cursor_on_cell
at gtktreeview.c line 12670
#28 IA__gtk_tree_view_set_cursor
at gtktreeview.c line 12622
#29 show_selection_idle_callback
at fm-tree-view.c line 242
#30 g_idle_dispatch
at gmain.c line 4132
#31 IA__g_main_context_dispatch
at gmain.c line 2061
#32 g_main_context_iterate
at gmain.c line 2694
#33 IA__g_main_loop_run
at gmain.c line 2898
#34 IA__gtk_main
at gtkmain.c line 1146
#35 main
at nautilus-main.c line 556
#36 __libc_start_main
at libc-start.c line 227
#37 _start
#0 __kernel_vsyscall



----------- .xsession-errors (3026 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-11-25 13:08:28 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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