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


Summary:	crash in CD/DVD Creator:


Status:	RESOLVED DUPLICATE of bug 320020

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-08-22 21:48 UTC by spookyguy
Modified:	2007-08-22 22:00 UTC

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

Description spookyguy 2007-08-22 21:48:11 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: 53096448 vsize: 0 resident: 53096448 share: 0 rss: 15699968 rss_rlim: 0
CPU usage: start_time: 1187804881 rtime: 0 utime: 146 stime: 0 cutime:136 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

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

+ Trace 157220

Thread 1 (Thread -1227307344 (LWP 6334))

#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 nautilus_directory_async_state_changed
#5 nautilus_directory_async_state_changed
#6 nautilus_undo_transaction_unregister_object
#7 nautilus_directory_async_state_changed
#8 POA_Nautilus_MetafileMonitor__init
#9 POA_Nautilus_MetafileMonitor__init
#10 fm_directory_view_bump_zoom_level
#11 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set
from /usr/lib/libgobject-2.0.so.0
#13 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_object_new
from /usr/lib/libgobject-2.0.so.0
#16 POA_Nautilus_MetafileMonitor__init
#17 nautilus_undo_transaction_unregister_object
#18 POA_Nautilus_MetafileMonitor__init
#19 POA_Nautilus_MetafileMonitor__init
#20 nautilus_undo_transaction_unregister_object
#21 nautilus_clipboard_monitor_emit_changed
#22 nautilus_directory_async_state_changed
#23 nautilus_icon_container_request_update_all
#24 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 POA_Nautilus_MetafileMonitor__init
#30 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#31 ??
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2007-08-22 22:00:08 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 320020 ***