Bug 416130 – crash in Computer: Nothing

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 416130 - crash in Computer: Nothing


Summary:	crash in Computer: Nothing


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:

Depends on:
Blocks:

Reported:	2007-03-08 17:38 UTC by anurup
Modified:	2007-03-08 18:16 UTC

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

Description anurup 2007-03-08 17:38:59 UTC

What were you doing when the application crashed?
Nothing


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: 404439040 vsize: 404439040 resident: 13701120 share: 9564160 rss: 13701120 rss_rlim: -1
CPU usage: start_time: 1173375677 rtime: 21 utime: 16 stime: 5 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 46912496446912 (LWP 3182)]
(no debugging symbols found)
0x00000030e6a0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 116931

Thread 1 (Thread 46912496446912 (LWP 3182))

#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_get_icon_sizes
from /usr/lib64/libgtk-x11-2.0.so.0
#8 gtk_window_get_default_icon_list
from /usr/lib64/libgtk-x11-2.0.so.0
#9 gtk_window_get_default_icon_list
from /usr/lib64/libgtk-x11-2.0.so.0
#10 gtk_window_new
from /usr/lib64/libgtk-x11-2.0.so.0
#11 POA_Nautilus_MetafileMonitor__init
#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_widget_realize
from /usr/lib64/libgtk-x11-2.0.so.0
#17 POA_Nautilus_MetafileMonitor__init
#18 POA_Nautilus_MetafileMonitor__init
#19 POA_Nautilus_MetafileMonitor__init
#20 g_cclosure_marshal_VOID__ENUM
#21 POA_Nautilus_MetafileMonitor__init
#22 POA_Nautilus_MetafileMonitor__init
#23 __libc_start_main
from /lib64/libc.so.6
#24 g_cclosure_marshal_VOID__ENUM
#25 ??
#26 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Pedro Villavicencio 2007-03-08 18:16:45 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 ***