Bug 370090 – crash in CD/DVD Creator: I didn't even know anyth...

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 370090 - crash in CD/DVD Creator: I didn't even know anyth...


Summary:	crash in CD/DVD Creator: I didn't even know anyth...


Status:	RESOLVED DUPLICATE of bug 351713

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-11-03 16:19 UTC by redhat9_0me
Modified:	2006-11-03 16:22 UTC

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

Description redhat9_0me 2006-11-03 16:19:25 UTC

What were you doing when the application crashed?
I didn't even know anything crashed.  


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (9 sec old) ---------------------
** (gnome-terminal:15369): WARNING **: No handler for control sequence `device-control-string' defined.
** (gnome-terminal:15369): WARNING **: No handler for control sequence `device-control-string' defined.
** (gnome-terminal:15369): WARNING **: No handler for control sequence `device-control-string' defined.
** (gnome-terminal:15369): WARNING **: No handler for control sequence `device-control-string' defined.
** (gnome-terminal:15369): WARNING **: No handler for control sequence `device-control-string' defined.
** (gnome-terminal:15369): WARNING **: No handler for control sequence `device-control-string' defined.
** (gnome-terminal:15369): WARNING **: No handler for control sequence `device-control-string' defined.
Xlib: unexpected async reply (sequence 0xe)!
--------------------------------------------------

Memory status: size: 105435136 vsize: 0 resident: 105435136 share: 0 rss: 14757888 rss_rlim: 0
CPU usage: start_time: 1162570585 rtime: 0 utime: 36 stime: 0 cutime:31 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208943872 (LWP 15329)]
(no debugging symbols found)
0x00796402 in __kernel_vsyscall ()

+ Trace 82414

Thread 1 (Thread -1208943872 (LWP 15329))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/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_file_get_uri
#6 nautilus_file_get_uri
#7 nautilus_file_has_volume
#8 nautilus_icon_container_request_update_all
#9 fm_directory_view_bump_zoom_level
#10 nautilus_file_ref
#11 nautilus_file_ref
#12 nautilus_icon_container_request_update_all
#13 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#14 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#15 g_main_context_check
from /lib/libglib-2.0.so.0
#16 g_main_loop_run
from /lib/libglib-2.0.so.0
#17 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#18 POA_Nautilus_MetafileMonitor__init
#19 __libc_start_main
from /lib/i686/nosegneg/libc.so.6
#20 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-11-03 16:22: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 351713 ***