Bug 416286 – crash in CD/DVD Creator: running google earth

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 416286 - crash in CD/DVD Creator: running google earth


Summary:	crash in CD/DVD Creator: running google earth


Status:	RESOLVED DUPLICATE of bug 389087

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:

Duplicates:	416287 416289 416290 416291 416292 416293 416294 434903 (view as bug list)
Depends on:
Blocks:

Reported:	2007-03-09 01:48 UTC by kevinchen00
Modified:	2007-06-22 13:42 UTC

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

Description kevinchen00 2007-03-09 01:48:12 UTC

What were you doing when the application crashed?
running google earth


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

Memory status: size: 485351424 vsize: 485351424 resident: 15753216 share: 10891264 rss: 15753216 rss_rlim: -1
CPU usage: start_time: 1173404836 rtime: 17 utime: 14 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496446928 (LWP 3726)]
(no debugging symbols found)
0x000000326720d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 117057

Thread 1 (Thread 46912496446928 (LWP 3726))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 strcmp
from /lib64/libc.so.6
#4 gtk_hsv_new
from /usr/lib64/libgtk-x11-2.0.so.0
#5 gtk_hsv_new
from /usr/lib64/libgtk-x11-2.0.so.0
#6 gtk_icon_info_get_type
from /usr/lib64/libgtk-x11-2.0.so.0
#7 gtk_icon_theme_lookup_icon
from /usr/lib64/libgtk-x11-2.0.so.0
#8 nautilus_icon_container_request_update_all
#9 nautilus_icon_container_request_update_all
#10 nautilus_icon_container_request_update_all
#11 fm_directory_view_bump_zoom_level
#12 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#13 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit
from /lib64/libgobject-2.0.so.0
#16 gtk_action_create_menu_item
from /usr/lib64/libgtk-x11-2.0.so.0
#17 gtk_ui_manager_new_merge_id
from /usr/lib64/libgtk-x11-2.0.so.0
#18 gtk_ui_manager_new_merge_id
from /usr/lib64/libgtk-x11-2.0.so.0
#19 gtk_ui_manager_new_merge_id
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_ui_manager_new_merge_id
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_ui_manager_new_merge_id
from /usr/lib64/libgtk-x11-2.0.so.0
#22 gtk_ui_manager_new_merge_id
from /usr/lib64/libgtk-x11-2.0.so.0
#23 gtk_ui_manager_new_merge_id
from /usr/lib64/libgtk-x11-2.0.so.0
#24 gtk_ui_manager_get_ui
from /usr/lib64/libgtk-x11-2.0.so.0
#25 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#26 g_main_context_check
from /lib64/libglib-2.0.so.0
#27 g_main_loop_run
from /lib64/libglib-2.0.so.0
#28 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#29 POA_Nautilus_MetafileMonitor__init
#30 __libc_start_main
from /lib64/libc.so.6
#31 g_cclosure_marshal_VOID__ENUM
#32 ??
#33 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Susana 2007-03-09 11:28:23 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Susana 2007-03-09 11:28:59 UTC

*** Bug 416287 has been marked as a duplicate of this bug. ***

Comment 3 Susana 2007-03-09 11:29:09 UTC

*** Bug 416289 has been marked as a duplicate of this bug. ***

Comment 4 Susana 2007-03-09 11:29:18 UTC

*** Bug 416290 has been marked as a duplicate of this bug. ***

Comment 5 Susana 2007-03-09 11:29:25 UTC

*** Bug 416291 has been marked as a duplicate of this bug. ***

Comment 6 Susana 2007-03-09 11:29:51 UTC

*** Bug 416293 has been marked as a duplicate of this bug. ***

Comment 7 Susana 2007-03-09 11:29:51 UTC

*** Bug 416292 has been marked as a duplicate of this bug. ***

Comment 8 Susana 2007-03-09 11:32:29 UTC

*** Bug 416294 has been marked as a duplicate of this bug. ***

Comment 9 Pedro Villavicencio 2007-05-02 00:33:16 UTC

*** Bug 434903 has been marked as a duplicate of this bug. ***

Comment 10 André Klapper 2007-06-22 13:42:13 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 389087 ***