Bug 480932 – crash in CD/DVD Creator: Searching files on C: an...

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 480932 - crash in CD/DVD Creator: Searching files on C: an...


Summary:	crash in CD/DVD Creator: Searching files on C: an...


Status:	RESOLVED DUPLICATE of bug 363856

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-09-27 13:06 UTC by francescodarcangeli
Modified:	2007-09-28 15:03 UTC

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

Description francescodarcangeli 2007-09-27 13:06:11 UTC

What were you doing when the application crashed?
Searching files on C: and not using CD/DVD creator at all...


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

Memory status: size: 91058176 vsize: 0 resident: 91058176 share: 0 rss: 35717120 rss_rlim: 0
CPU usage: start_time: 1190850971 rtime: 0 utime: 6105 stime: 0 cutime:3564 cstime: 0 timeout: 2541 it_real_value: 0 frequency: 642

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

+ Trace 165900

Thread 1 (Thread -1226516816 (LWP 6564))

#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_file_get_uri
#5 nautilus_file_get_parent_uri
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 fm_directory_view_bump_zoom_level
#9 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#10 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#11 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#12 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#13 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#14 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#15 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#16 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#17 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#18 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#19 POA_Nautilus_MetafileMonitor__init
#20 fm_directory_view_bump_zoom_level
#21 fm_directory_view_bump_zoom_level
#22 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 nautilus_directory_async_state_changed
#28 nautilus_marshal_BOOLEAN__POINTER
#29 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#34 nautilus_marshal_BOOLEAN__POINTER
#35 nautilus_marshal_BOOLEAN__POINTER
#36 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#38 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#39 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 POA_Nautilus_MetafileMonitor__init
#42 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#43 ??
#0 __kernel_vsyscall

Comment 1 Cosimo Cecchi 2007-09-28 15:03:26 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 363856 ***