Bug 449985 – crash in Computer: send this error

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 449985 - crash in Computer: send this error


Summary:	crash in Computer: send this error


Status:	RESOLVED DUPLICATE of bug 436873

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	449986 (view as bug list)
Depends on:
Blocks:

Reported:	2007-06-22 08:17 UTC by joy
Modified:	2007-06-22 11:13 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description joy 2007-06-22 08:17:48 UTC

Version: 2.18.1

What were you doing when the application crashed?
send this error


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 504070144 vsize: 504070144 resident: 25821184 share: 19787776 rss: 25821184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182499890 rtime: 54 utime: 47 stime: 7 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 46912514886144 (LWP 9176)]
[New Thread 1157658960 (LWP 9186)]
[New Thread 1147169104 (LWP 9185)]
(no debugging symbols found)
0x0000003214e0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 142838

Thread 1 (Thread 46912514886144 (LWP 9176))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_utf8_find_prev_char
from /lib64/libglib-2.0.so.0
#4 g_markup_parse_context_parse
from /lib64/libglib-2.0.so.0
#5 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnome-desktop-2.so.2
#6 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnome-desktop-2.so.2
#7 gnome_bg_create_pixmap
from /usr/lib64/libgnome-desktop-2.so.2
#8 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libeel-2.so.2
#9 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libeel-2.so.2
#10 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#11 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /lib64/libgobject-2.0.so.0
#14 gtk_widget_realize
from /usr/lib64/libgtk-x11-2.0.so.0
#15 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#18 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#19 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#21 g_signal_emit
from /lib64/libgobject-2.0.so.0
#22 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#23 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#25 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#26 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#28 g_signal_emit
from /lib64/libgobject-2.0.so.0
#29 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#30 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#31 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#32 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#33 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#35 g_signal_emit
from /lib64/libgobject-2.0.so.0
#36 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#37 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#38 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#39 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#40 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#41 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#42 g_signal_emit
from /lib64/libgobject-2.0.so.0
#43 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#44 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#45 ??
#46 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#47 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#48 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#49 g_signal_emit
from /lib64/libgobject-2.0.so.0
#50 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#51 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#52 ??
#53 ??
#54 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#55 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#56 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#57 g_signal_emit
from /lib64/libgobject-2.0.so.0
#58 gtk_widget_show
from /usr/lib64/libgtk-x11-2.0.so.0
#59 nautilus_window_show_window
#60 ??
#61 ??
#62 ??
#63 ??
#64 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#65 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#66 g_main_loop_run
from /lib64/libglib-2.0.so.0
#67 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#68 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-06-22 11:12:23 UTC

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

Comment 2 André Klapper 2007-06-22 11:13:12 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 436873 ***