Bug 407978 – 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 407978 - crash in CD/DVD Creator:


Summary:	crash in CD/DVD Creator:


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:	2007-02-14 19:43 UTC by squinty
Modified:	2007-02-14 20:39 UTC

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

Description squinty 2007-02-14 19:43:02 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: 118415360 vsize: 0 resident: 118415360 share: 0 rss: 34852864 rss_rlim: 0
CPU usage: start_time: 1171472959 rtime: 0 utime: 1746 stime: 0 cutime:1536 cstime: 0 timeout: 210 it_real_value: 0 frequency: 332

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

+ Trace 110762

Thread 1 (Thread -1226881360 (LWP 4817))

#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 POA_Nautilus_MetafileMonitor__init
#29 POA_Nautilus_MetafileMonitor__init
#30 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#31 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#35 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib/libgnomevfs-2.so.0
#36 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#37 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.3
#38 dbus_server_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.2
#39 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#40 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#41 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 POA_Nautilus_MetafileMonitor__init
#44 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#45 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-02-14 20:39: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 362346 ***