Bug 375301 – crash in Computer: trying to mount the cd d...

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 375301 - crash in Computer: trying to mount the cd d...


Summary:	crash in Computer: trying to mount the cd d...


Status:	RESOLVED DUPLICATE of bug 362302

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-14 21:50 UTC by brian.fife
Modified:	2006-11-14 21:54 UTC

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

Description brian.fife 2006-11-14 21:50:39 UTC

What were you doing when the application crashed?
trying to mount the cd drive


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: 137490432 vsize: 0 resident: 137490432 share: 0 rss: 26017792 rss_rlim: 0
CPU usage: start_time: 1163540862 rtime: 0 utime: 257 stime: 0 cutime:230 cstime: 0 timeout: 27 it_real_value: 0 frequency: 3

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 -1209021696 (LWP 2488)]
(no debugging symbols found)
0x006b9402 in __kernel_vsyscall ()

+ Trace 86504

Thread 1 (Thread -1209021696 (LWP 2488))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 nautilus_file_ref
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 gtk_combo_new
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_combo_box_set_active_iter
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_combo_box_set_active_iter
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit
from /lib/libgobject-2.0.so.0
#21 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_menu_shell_append
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_menu_reorder_child
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /lib/libgobject-2.0.so.0
#28 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#30 g_signal_emit
from /lib/libgobject-2.0.so.0
#31 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#35 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#36 g_main_context_check
from /lib/libglib-2.0.so.0
#37 g_main_loop_run
from /lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 POA_Nautilus_MetafileMonitor__init
#40 __libc_start_main
from /lib/libc.so.6
#41 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-11-14 21:54:31 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 362302 ***