Bug 497366 – crash in File Browser: haciendo una busqueda

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 497366 - crash in File Browser: haciendo una busqueda


Summary:	crash in File Browser: haciendo una busqueda


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:	2007-11-16 13:05 UTC by emujica
Modified:	2007-11-16 16:13 UTC

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

Description emujica 2007-11-16 13:05:51 UTC

Version: 2.18.3

What were you doing when the application crashed?
haciendo una busqueda


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 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 191561728 vsize: 191561728 resident: 75325440 share: 41205760 rss: 75325440 rss_rlim: 4294967295
CPU usage: start_time: 1195185326 rtime: 116639 utime: 29331 stime: 87308 cutime:404 cstime: 60 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 -1208908064 (LWP 12749)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 178114

Thread 1 (Thread -1208908064 (LWP 12749))

#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 ??
#17 ??
#18 ??
#19 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /lib/libgobject-2.0.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#23 g_signal_emit
from /lib/libgobject-2.0.so.0
#24 nautilus_directory_emit_done_loading
#25 ??
#26 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /lib/libgobject-2.0.so.0
#28 ??
from /lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#30 g_signal_emit
from /lib/libgobject-2.0.so.0
#31 nautilus_search_engine_finished
#32 ??
#33 ??
from /lib/libglib-2.0.so.0
#34 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#35 ??
from /lib/libglib-2.0.so.0
#36 g_main_loop_run
from /lib/libglib-2.0.so.0
#37 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#38 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
closing
closing
** (gtkpod:16458): WARNING **: Acción desconocida (1024) en la lista de reproducción inteligente. Será ignorada.
** (gtkpod:16458): CRITICAL **: file misc_conversion.c: line 214 (ST_to_T): should not be reached
(nautilus:12749): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
warning: .dynamic section for "/usr/lib/libgnome-desktop-2.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 palfrey 2007-11-16 16:13:49 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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