Bug 388288 – crash in Home Folder: searching for files

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 388288 - crash in Home Folder: searching for files


Summary:	crash in Home Folder: searching for files


Status:	RESOLVED DUPLICATE of bug 365750

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:	2006-12-21 14:58 UTC by toni
Modified:	2006-12-21 15:49 UTC

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

Description toni 2006-12-21 14:58:07 UTC

What were you doing when the application crashed?
searching for files


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 112414720 vsize: 0 resident: 112414720 share: 0 rss: 34791424 rss_rlim: 0
CPU usage: start_time: 1166712662 rtime: 0 utime: 1648 stime: 0 cutime:1101 cstime: 0 timeout: 547 it_real_value: 0 frequency: 605

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226934608 (LWP 5288)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 95972

Thread 1 (Thread -1226934608 (LWP 5288))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 nautilus_file_get_uri
#5 nautilus_file_get_parent_uri
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 fm_directory_view_bump_zoom_level
#9 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#10 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#11 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#12 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#13 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#14 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#15 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#16 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#17 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#18 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#19 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#20 POA_Nautilus_MetafileMonitor__init
#21 fm_directory_view_bump_zoom_level
#22 fm_directory_view_bump_zoom_level
#23 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 nautilus_directory_async_state_changed
#29 nautilus_marshal_BOOLEAN__POINTER
#30 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#31 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#35 nautilus_marshal_BOOLEAN__POINTER
#36 nautilus_marshal_BOOLEAN__POINTER
#37 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#38 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#39 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#40 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#41 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#42 POA_Nautilus_MetafileMonitor__init
#43 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#44 ??
#0 __kernel_vsyscall

Comment 1 Susana 2006-12-21 15:49:54 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 365750 ***