Bug 374200 – crash in Home Folder: Plantage de Nautilus dès...

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 374200 - crash in Home Folder: Plantage de Nautilus dès...


Summary:	crash in Home Folder: Plantage de Nautilus dès...


Status:	RESOLVED DUPLICATE of bug 373697

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:	2006-11-12 07:03 UTC by zigazou
Modified:	2006-11-12 13:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description zigazou 2006-11-12 07:03:28 UTC

What were you doing when the application crashed?
Plantage de Nautilus dès que je veux utiliser le bouton-menu en bas à gauche des fenêtres pour remonter dans l'arborescence.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 533422080 vsize: 533422080 resident: 40775680 share: 24715264 rss: 40775680 rss_rlim: -1
CPU usage: start_time: 1163314557 rtime: 259 utime: 233 stime: 26 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496478208 (LWP 26750)]
(no debugging symbols found)
0x00000031a8a0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 85698

Thread 1 (Thread 46912496478208 (LWP 26750))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_instance_cast
from /lib64/libgobject-2.0.so.0
#4 nautilus_directory_async_state_changed
#5 nautilus_directory_async_state_changed
#6 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#7 g_main_context_check
from /lib64/libglib-2.0.so.0
#8 g_main_loop_run
from /lib64/libglib-2.0.so.0
#9 POA_Nautilus_MetafileMonitor__init
#10 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#11 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /lib64/libgobject-2.0.so.0
#14 gtk_button_set_alignment
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 gtk_button_released
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_marshal_BOOLEAN__VOID
from /usr/lib64/libgtk-x11-2.0.so.0
#21 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#22 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#24 g_signal_emit
from /lib64/libgobject-2.0.so.0
#25 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#26 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#27 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#28 gdk_add_client_message_filter
from /usr/lib64/libgdk-x11-2.0.so.0
#29 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#30 g_main_context_check
from /lib64/libglib-2.0.so.0
#31 g_main_loop_run
from /lib64/libglib-2.0.so.0
#32 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#33 POA_Nautilus_MetafileMonitor__init
#34 __libc_start_main
from /lib64/libc.so.6
#35 g_cclosure_marshal_VOID__ENUM
#36 ??
#37 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-11-12 13:46:44 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 373697 ***