Bug 510430 – crash in Computer: 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 510430 - crash in Computer: nautilus


Summary:	crash in Computer: nautilus


Status:	RESOLVED DUPLICATE of bug 459221

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:	2008-01-18 16:42 UTC by olivier
Modified:	2008-01-19 01:19 UTC

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

Description olivier 2008-01-18 16:42:02 UTC

Version: 2.18.3

What were you doing when the application crashed?
nautilus	


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 72380416 vsize: 72380416 resident: 22945792 share: 13750272 rss: 22945792 rss_rlim: 4294967295
CPU usage: start_time: 1200674124 rtime: 83 utime: 68 stime: 15 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226996048 (LWP 25597)]
(no debugging symbols found)
0xb7f797f2 in ?? () from /lib/ld-linux.so.2

+ Trace 185846

Thread 1 (Thread -1226996048 (LWP 25597))

#0 ??
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /lib/ld-linux.so.2
#5 raise
from /lib/i686/cmov/libc.so.6
#6 abort
from /lib/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 nautilus_navigation_window_show_sidebar
#11 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_handler_disconnect
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_combo_new
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_handler_disconnect
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_tree_model_row_deleted
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_list_store_remove
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_list_store_clear
from /usr/lib/libgtk-x11-2.0.so.0
#25 nautilus_navigation_window_show_sidebar
#26 nautilus_directory_schedule_dequeue_pending
#27 nautilus_directory_async_state_changed
#28 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#30 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#31 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main
#0 ??
from /lib/ld-linux.so.2

Comment 1 Cosimo Cecchi 2008-01-19 01:19:53 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 459221 ***