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 385713 - crash in Search for Files...:
crash in Search for Files...:
Status: RESOLVED INCOMPLETE
Product: gnome-utils
Classification: Deprecated
Component: gsearchtool
unspecified
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-14 03:53 UTC by sabitha.syifa
Modified: 2007-01-12 13:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description sabitha.syifa 2006-12-14 03:53:43 UTC
What were you doing when the application crashed?



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

Memory status: size: 1667072 vsize: 0 resident: 1667072 share: 0 rss: 548864 rss_rlim: 0
CPU usage: start_time: 1166064644 rtime: 0 utime: 124 stime: 0 cutime:0 cstime: 0 timeout: 124 it_real_value: 0 frequency: 18470

Backtrace was generated from '/usr/bin/gnome-search-tool'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Comment 1 Susana 2006-12-14 12:48:56 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Also, unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Susana 2007-01-12 13:49:33 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!