Bug 418590 – crash in CD/DVD Creator: Surfing the web with fir...

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 418590 - crash in CD/DVD Creator: Surfing the web with fir...


Summary:	crash in CD/DVD Creator: Surfing the web with fir...


Status:	RESOLVED DUPLICATE of bug 365638

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-03-15 14:36 UTC by john
Modified:	2007-03-17 14:29 UTC

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

Description john 2007-03-15 14:36:23 UTC

What were you doing when the application crashed?
Surfing the web with firefox.  As far as I can tell nothing is crashing but I am getting one of these bug reporting tool boxes every few minutes.


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

Memory status: size: 48304128 vsize: 0 resident: 48304128 share: 0 rss: 13357056 rss_rlim: 0
CPU usage: start_time: 1173962032 rtime: 0 utime: 92 stime: 0 cutime:84 cstime: 0 timeout: 8 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 -1226508624 (LWP 5267)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 118834

Thread 1 (Thread -1226508624 (LWP 5267))

#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 nautilus_directory_async_state_changed
#10 nautilus_directory_async_state_changed
#11 nautilus_directory_async_state_changed
#12 nautilus_directory_async_state_changed
#13 nautilus_undo_transaction_unregister_object
#14 nautilus_directory_async_state_changed
#15 POA_Nautilus_MetafileMonitor__init
#16 POA_Nautilus_MetafileMonitor__init
#17 fm_directory_view_bump_zoom_level
#18 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#19 g_object_set
from /usr/lib/libgobject-2.0.so.0
#20 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#21 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_object_new
from /usr/lib/libgobject-2.0.so.0
#23 fm_directory_view_bump_zoom_level
#24 nautilus_undo_transaction_unregister_object
#25 POA_Nautilus_MetafileMonitor__init
#26 POA_Nautilus_MetafileMonitor__init
#27 nautilus_clipboard_monitor_emit_changed
#28 nautilus_directory_async_state_changed
#29 nautilus_directory_async_state_changed
#30 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#31 ??
#32 ??
#33 ??
#34 ??
from /usr/lib/libgthread-2.0.so.0
#35 ??
#36 ??
from /usr/lib/libglib-2.0.so.0
#37 ??
#38 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#39 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#40 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#41 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#42 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#43 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#44 POA_Nautilus_MetafileMonitor__init
#45 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#46 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-03-17 14:29:01 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 365638 ***