Bug 457202 – crash in Open 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 457202 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 445429

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-15 20:56 UTC by DunKrS
Modified:	2007-07-16 15:59 UTC

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

Description DunKrS 2007-07-15 20:56:40 UTC

Version: 2.18.1

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 84447232 vsize: 84447232 resident: 19726336 share: 11939840 rss: 19726336 rss_rlim: 4294967295
CPU usage: start_time: 1184532902 rtime: 114 utime: 104 stime: 10 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 -1208690976 (LWP 3064)]
(no debugging symbols found)
0x00fb6402 in __kernel_vsyscall ()

+ Trace 148232

Thread 1 (Thread -1208690976 (LWP 3064))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#10 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#11 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#13 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
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 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnomevfs-2.so.0
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#32 g_cclosure_marshal_VOID__ENUM
from /lib/libpthread.so.0
#33 ??
#34 g_cclosure_marshal_VOID__ENUM
from /lib/libpthread.so.0
#35 ??
#36 ??
#37 g_cclosure_marshal_VOID__ENUM
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 ---------------------
This can cause subtle evils like #48423
(nautilus:3064): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3064): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3064): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3064): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3064): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3064): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3064): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
--------------------------------------------------

Comment 1 Damien Durand 2007-07-16 15:59:10 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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