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 535538 - Nautilus crashes during file search
Nautilus crashes during file search
Status: RESOLVED DUPLICATE of bug 363856
Product: nautilus
Classification: Core
Component: File Search Interface
2.16.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-29 17:26 UTC by Jason Graham
Modified: 2008-05-30 12:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Jason Graham 2008-05-29 17:26:16 UTC
Steps to reproduce:
1. Have Beagle daemon running
2. Perform file search using Nautilus search interface.
3. 


Stack trace:
Distribution: CentOS release 5 (Final)
Gnome Release: 2.16.0 2007-02-18 (CentOS)
BugBuddy Version: 2.16.0

Memory status: size: 479232000 vsize: 479232000 resident: 37945344 share: 17989632 rss: 37945344 rss_rlim: -1
CPU usage: start_time: 1212081304 rtime: 2663 utime: 1489 stime: 1174 cutime:7 cstime: 2 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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47626962924080 (LWP 29713)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x000000344560d9ff in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47626962924080 (LWP 29713))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 nautilus_file_get_uri
  • #4 nautilus_file_get_parent_uri
  • #5 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #6 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #7 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #8 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #9 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #10 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #11 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #12 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #13 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #14 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #15 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #16 POA_Nautilus_MetafileMonitor__init
  • #17 fm_directory_view_bump_zoom_level
  • #18 fm_directory_view_bump_zoom_level
  • #19 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #20 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #23 nautilus_marshal_BOOLEAN__POINTER
  • #24 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #25 g_signal_override_class_closure
    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 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #29 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #32 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #33 g_signal_override_class_closure
    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 beagle_request_get_type
    from /usr/lib64/libbeagle.so.0
  • #37 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #38 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #40 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #41 POA_Nautilus_MetafileMonitor__init
  • #42 __libc_start_main
    from /lib64/libc.so.6
  • #43 g_cclosure_marshal_VOID__ENUM
  • #44 ??
  • #45 ??
  • #0 waitpid
    from /lib64/libpthread.so.0


Other information:
Please note that the crash associated with the afore mentioned file search occurs with the Nautilus search utility and not the Beagle search utility; there seems to be a conflict with the two utilities. Also, the Nautilus file search utility performs as expected when the Beagle daemon is not running.
Comment 1 Cosimo Cecchi 2008-05-30 12:15:02 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 363856 ***