Bug 390286 – crash in CD/DVD Creator: Nautilus Starting to bro...

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 390286 - crash in CD/DVD Creator: Nautilus Starting to bro...


Summary:	crash in CD/DVD Creator: Nautilus Starting to bro...


Status:	RESOLVED DUPLICATE of bug 362346

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-12-28 09:33 UTC by Nicolas Martin
Modified:	2006-12-28 11:27 UTC

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

Description Nicolas Martin 2006-12-28 09:33:39 UTC

What were you doing when the application crashed?
Nautilus
Starting to browse a Windows network (link smb:///) and then, clicked on the "Back" button. 
=> Nautilus crashed, saying it cannot access the CD/DVD creation window. 
Note : I was not using at that time the CD/DVD creation window


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 123011072 vsize: 0 resident: 123011072 share: 0 rss: 35991552 rss_rlim: 0
CPU usage: start_time: 1167296232 rtime: 0 utime: 1638 stime: 0 cutime:1529 cstime: 0 timeout: 109 it_real_value: 0 frequency: 9

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226451280 (LWP 4874)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 97489

Thread 1 (Thread -1226451280 (LWP 4874))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/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_directory_async_state_changed
#11 fm_directory_view_bump_zoom_level
#12 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#13 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 fm_directory_view_bump_zoom_level
#19 fm_directory_view_bump_zoom_level
#20 nautilus_clipboard_monitor_emit_changed
#21 nautilus_directory_async_state_changed
#22 nautilus_directory_async_state_changed
#23 nautilus_undo_transaction_unregister_object
#24 nautilus_file_get_volume
#25 POA_Nautilus_MetafileMonitor__init
#26 POA_Nautilus_MetafileMonitor__init
#27 POA_Nautilus_MetafileMonitor__init
#28 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#33 _gtk_action_emit_activate
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#35 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#39 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#40 gtk_tool_button_new_from_stock
from /usr/lib/libgtk-x11-2.0.so.0
#41 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#42 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#43 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#44 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#45 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#46 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#47 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#48 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#49 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#51 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#54 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#55 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#56 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#57 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#58 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#59 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#60 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#61 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#62 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#63 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#64 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#65 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#66 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#67 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#68 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#69 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#70 POA_Nautilus_MetafileMonitor__init
#71 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#72 ??
#0 __kernel_vsyscall

Comment 1 Susana 2006-12-28 11:27:27 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 362346 ***