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


Summary:	crash in CD/DVD Creator:


Status:	RESOLVED DUPLICATE of bug 366699

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:

Duplicates:	435761 437221 (view as bug list)
Depends on:
Blocks:

Reported:	2007-04-20 17:52 UTC by ahmedsaadmohammed
Modified:	2007-06-21 03:28 UTC

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

Description ahmedsaadmohammed 2007-04-20 17:52:17 UTC

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 173875200 vsize: 0 resident: 173875200 share: 0 rss: 31473664 rss_rlim: 0
CPU usage: start_time: 1177088244 rtime: 0 utime: 2759 stime: 0 cutime:2073 cstime: 0 timeout: 686 it_real_value: 0 frequency: 10

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 -1208591616 (LWP 2630)]
[New Thread -1233937520 (LWP 3851)]
(no debugging symbols found)
0x00660402 in __kernel_vsyscall ()

+ Trace 129345

Thread 1 (Thread -1208591616 (LWP 2630))

#0 __kernel_vsyscall
#1 waitpid
from /lib/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/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /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 /lib/libgobject-2.0.so.0
#13 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /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 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 g_main_context_check
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 POA_Nautilus_MetafileMonitor__init
#28 __libc_start_main
from /lib/libc.so.6
#29 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: plugin_get_value 1 (1)
** Message: plugin_get_value 2 (2)
** (nautilus:2630): WARNING **: destroyed file still being monitored
(gnome-panel:2628): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed
(gnome-panel:2628): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed
** ERROR **: file nautilus-directory-background.c: line 621 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
** (bug-buddy:6986): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Comment 1 palfrey 2007-04-27 14:49:02 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 palfrey 2007-05-04 11:23:04 UTC

*** Bug 435761 has been marked as a duplicate of this bug. ***

Comment 3 Pedro Villavicencio 2007-05-09 21:07:48 UTC

*** Bug 437221 has been marked as a duplicate of this bug. ***

Comment 4 Karsten Bräckelmann 2007-06-21 03:28:50 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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