Bug 516449 – crash in Open Folder:

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 516449 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 439977

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:	516450 (view as bug list)
Depends on:
Blocks:

Reported:	2008-02-14 14:00 UTC by alexandre.munoz
Modified:	2008-02-15 10:14 UTC

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

Description alexandre.munoz 2008-02-14 14:00:57 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 440008704 vsize: 440008704 resident: 23543808 share: 17457152 rss: 23543808 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202997515 rtime: 25 utime: 22 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 46912496348704 (LWP 12523)]
[New Thread 1105209680 (LWP 12528)]
[New Thread 1094719824 (LWP 12527)]
[New Thread 1084229968 (LWP 12524)]
(no debugging symbols found)
0x0000003c9980d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 189184

Thread 1 (Thread 46912496348704 (LWP 12523))

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

Comment 1 André Klapper 2008-02-15 01:46:09 UTC

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

Comment 2 Cosimo Cecchi 2008-02-15 10:14:45 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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