GNOME Bugzilla – Bug 326650
Nautilus Search Crash
Last modified: 2006-01-11 22:32:55 UTC
Distribution: Unknown Package: nautilus Severity: Normal Version: GNOME2.12.0 2.12.0 Gnome-Distributor: SUSE Synopsis: Nautilus Search Crash Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.0 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Nautilus Search crashes on the start of a search Steps to reproduce the crash: 1. Open search for files 2. Enter criteria 3. Click search Expected Results: Find the file How often does this happen? Everytime Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1092583648 (LWP 13715)] [New Thread 1118792624 (LWP 13726)] [Thread debugging using libthread_db enabled] [New Thread 1092583648 (LWP 13715)] [New Thread 1118792624 (LWP 13726)] [Thread debugging using libthread_db enabled] [New Thread 1092583648 (LWP 13715)] [New Thread 1118792624 (LWP 13726)] [New Thread 1118526384 (LWP 13725)] [New Thread 1118260144 (LWP 13724)] [New Thread 1117993904 (LWP 13723)] [New Thread 1117727664 (LWP 13722)] [New Thread 1117461424 (LWP 13721)] [New Thread 1117195184 (LWP 13720)] [New Thread 1116928944 (LWP 13719)] [New Thread 1116662704 (LWP 13718)] [New Thread 1116396464 (LWP 13717)] [New Thread 1113979824 (LWP 13716)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 65137
Thread 1 (Thread 1092583648 (LWP 13715))
------- Bug created by bug-buddy at 2006-01-11 20:01 ------- Unknown version 2.12.0 in product nautilus. Setting version to "2.12.x".
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 320389 ***