Bug 499365 – crash in Home Folder: halt

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


Summary:	crash in Home Folder: halt


Status:	RESOLVED DUPLICATE of bug 436071

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-24 15:47 UTC by arnopps
Modified:	2007-11-24 18:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description arnopps 2007-11-24 15:47:18 UTC

What were you doing when the application crashed?
halt


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 85467136 vsize: 85467136 resident: 30842880 share: 20213760 rss: 30842880 rss_rlim: 4294967295
CPU usage: start_time: 1195926361 rtime: 107 utime: 95 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208875296 (LWP 2841)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 179469

Thread 1 (Thread -1208875296 (LWP 2841))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 nautilus_file_compare_for_sort
#6 fm_icon_view_compare_files
#7 ??
#8 ??
#9 ??
from /lib/libglib-2.0.so.0
#10 ??
from /lib/libglib-2.0.so.0
#11 ??
from /lib/libglib-2.0.so.0
#12 ??
from /lib/libglib-2.0.so.0
#13 ??
from /lib/libglib-2.0.so.0
#14 ??
#15 ??
#16 ??
#17 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /lib/libgobject-2.0.so.0
#19 ??
from /lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#21 g_signal_emit
from /lib/libgobject-2.0.so.0
#22 nautilus_directory_emit_done_loading
#23 ??
#24 ??
#25 ??
from /usr/lib/libgnomevfs-2.so.0
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
from /lib/libglib-2.0.so.0
#32 ??
from /lib/libpthread.so.0
#33 ??
#34 ??
from /lib/libpthread.so.0
#35 ??
#36 ??
#37 ??
from /usr/lib/libgnomevfs-2.so.0
#38 ??
#39 ??
#40 ??
#41 g_slice_alloc
from /lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (14 sec old) ---------------------
(nautilus:2962): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(nautilus:2841): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:2841): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2841): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
** (nautilus:2841): CRITICAL **: nautilus_information_panel_set_uri: assertion `initial_title != NULL' failed
(nautilus:2841): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2841): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2841): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
--------------------------------------------------

Comment 1 Susana 2007-11-24 18:39:51 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 436071 ***