Bug 456714 – crash in CD/DVD Creator:

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 456714 - crash in CD/DVD Creator:


Summary:	crash in CD/DVD Creator:


Status:	RESOLVED DUPLICATE of bug 362598

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:	2007-07-13 20:11 UTC by art_killer
Modified:	2007-07-26 12:12 UTC

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

Description art_killer 2007-07-13 20:11:42 UTC

What were you doing when the application crashed?



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

Memory status: size: 106655744 vsize: 0 resident: 106655744 share: 0 rss: 32686080 rss_rlim: 0
CPU usage: start_time: 1184345422 rtime: 0 utime: 1235 stime: 0 cutime:1155 cstime: 0 timeout: 80 it_real_value: 0 frequency: 1

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 -1226639696 (LWP 4125)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 147873

Thread 1 (Thread -1226639696 (LWP 4125))

#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 g_type_check_instance
from /usr/lib/libgobject-2.0.so.0
#5 g_signal_handlers_disconnect_matched
from /usr/lib/libgobject-2.0.so.0
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#9 POA_Nautilus_MetafileMonitor__init
#10 POA_Nautilus_MetafileMonitor__init
#11 POA_Nautilus_MetafileMonitor__init
#12 POA_Nautilus_MetafileMonitor__init
#13 POA_Nautilus_MetafileMonitor__init
#14 nautilus_undo_transaction_unregister_object
#15 fm_directory_view_bump_zoom_level
#16 nautilus_clipboard_monitor_emit_changed
#17 nautilus_directory_async_state_changed
#18 nautilus_directory_async_state_changed
#19 nautilus_directory_async_state_changed
#20 nautilus_clipboard_monitor_emit_changed
#21 nautilus_clipboard_monitor_emit_changed
#22 nautilus_directory_async_state_changed
#23 nautilus_undo_transaction_unregister_object
#24 nautilus_file_get_volume
#25 nautilus_icon_container_request_update_all
#26 fm_directory_view_bump_zoom_level
#27 fm_directory_view_bump_zoom_level
#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 nautilus_file_get_uri
#34 nautilus_directory_async_state_changed
#35 nautilus_file_get_uri
#36 nautilus_directory_async_state_changed
#37 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#38 ??
#39 ??
#40 ??
#41 ??
from /usr/lib/libgthread-2.0.so.0
#42 ??
#43 ??
from /usr/lib/libglib-2.0.so.0
#44 ??
#45 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#46 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#47 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#48 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#49 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#50 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#51 POA_Nautilus_MetafileMonitor__init
#52 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#53 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-07-26 12:12:25 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 362598 ***