Bug 380953 – crash in CD/DVD Creator: Deleting a folder... Not...

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 380953 - crash in CD/DVD Creator: Deleting a folder... Not...


Summary:	crash in CD/DVD Creator: Deleting a folder... Not...


Status:	RESOLVED DUPLICATE of bug 364335

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-30 16:46 UTC by floydiansteve
Modified:	2006-11-30 18:16 UTC

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

Description floydiansteve 2006-11-30 16:46:38 UTC

What were you doing when the application crashed?
Deleting a folder... Not sure why the CD burning application was even running.


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

Memory status: size: 108519424 vsize: 0 resident: 108519424 share: 0 rss: 29204480 rss_rlim: 0
CPU usage: start_time: 1164899248 rtime: 0 utime: 25210 stime: 0 cutime:24053 cstime: 0 timeout: 1157 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 -1226414416 (LWP 4483)]
[New Thread -1322497120 (LWP 7876)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 90588

Thread 1 (Thread -1226414416 (LWP 4483))

#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_clipboard_monitor_emit_changed
#5 nautilus_clipboard_monitor_emit_changed
#6 nautilus_directory_async_state_changed
#7 nautilus_directory_async_state_changed
#8 nautilus_directory_ref
#9 nautilus_directory_ref
#10 nautilus_directory_ref
#11 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#12 ??
#13 ??
#14 ??
#15 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#16 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 POA_Nautilus_MetafileMonitor__init
#22 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#23 ??
#0 __kernel_vsyscall

Comment 1 Germán Poo-Caamaño 2006-11-30 18:16:38 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 364335 ***