Bug 514747 – 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 514747 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 436071

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:

Depends on:
Blocks:

Reported:	2008-02-06 13:08 UTC by pars5555
Modified:	2008-02-07 09:21 UTC

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

Description pars5555 2008-02-06 13:08:09 UTC

Version: 2.18.3

What were you doing when the application crashed?



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

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 104992768 vsize: 104992768 resident: 49844224 share: 21880832 rss: 49844224 rss_rlim: 4294967295
CPU usage: start_time: 1202221003 rtime: 2011 utime: 1498 stime: 513 cutime:1 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208613152 (LWP 3494)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 188284

Thread 1 (Thread -1208613152 (LWP 3494))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 nautilus_file_compare_for_sort
#6 fm_icon_view_compare_files
#7 ??
#8 ??
#9 ??
from /lib/libglib-2.0.so.0
#10 ??
from /lib/libglib-2.0.so.0
#11 ??
from /lib/libglib-2.0.so.0
#12 ??
from /lib/libglib-2.0.so.0
#13 ??
from /lib/libglib-2.0.so.0
#14 ??
from /lib/libglib-2.0.so.0
#15 ??
from /lib/libglib-2.0.so.0
#16 ??
from /lib/libglib-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /lib/libgobject-2.0.so.0
#22 ??
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#24 g_signal_emit
from /lib/libgobject-2.0.so.0
#25 nautilus_directory_emit_done_loading
#26 ??
#27 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /lib/libgobject-2.0.so.0
#29 ??
from /lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#31 g_signal_emit
from /lib/libgobject-2.0.so.0
#32 nautilus_search_engine_finished
#33 ??
#34 ??
from /lib/libglib-2.0.so.0
#35 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#36 ??
from /lib/libglib-2.0.so.0
#37 g_main_loop_run
from /lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libgnome-window-settings.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libpanel-applet-2.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libmetacity-private.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libpoppler-glib.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Gianluca Borello 2008-02-07 09:21:35 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 436071 ***