Bug 392822 – crash in CD/DVD Creator: I was browsing the file ...

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 392822 - crash in CD/DVD Creator: I was browsing the file ...


Summary:	crash in CD/DVD Creator: I was browsing the file ...


Status:	RESOLVED DUPLICATE of bug 371237

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-01-04 18:19 UTC by david_barger
Modified:	2007-01-04 21:52 UTC

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

Description david_barger 2007-01-04 18:19:48 UTC

What were you doing when the application crashed?
I was browsing the file system	


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

Memory status: size: 133890048 vsize: 0 resident: 133890048 share: 0 rss: 38649856 rss_rlim: 0
CPU usage: start_time: 1167412575 rtime: 0 utime: 65659 stime: 0 cutime:56137 cstime: 0 timeout: 9522 it_real_value: 0 frequency: 91

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 -1227278672 (LWP 4656)]
[New Thread -1260864608 (LWP 13737)]
[New Thread -1247749216 (LWP 12955)]
[New Thread -1323676768 (LWP 10596)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 99380

Thread 1 (Thread -1227278672 (LWP 4656))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 nautilus_file_ref
#11 fm_directory_view_bump_zoom_level
#12 fm_directory_view_bump_zoom_level
#13 POA_Nautilus_MetafileMonitor__init
#14 POA_Nautilus_MetafileMonitor__init
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 fm_directory_view_bump_zoom_level
#21 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 nautilus_file_get_uri
#27 nautilus_directory_async_state_changed
#28 nautilus_clipboard_monitor_emit_changed
#29 nautilus_clipboard_monitor_emit_changed
#30 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#31 nautilus_clipboard_monitor_emit_changed
#32 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#33 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#35 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#37 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib/libgnomevfs-2.so.0
#38 ??
#39 ??
#40 ??
#0 __kernel_vsyscall

Comment 1 Susana 2007-01-04 21:52:29 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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