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 467222 - crash in Home Folder: used the search-function...
crash in Home Folder: used the search-function...
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-16 07:07 UTC by Tobias Bradtke
Modified: 2007-08-21 20:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Tobias Bradtke 2007-08-16 07:07:57 UTC
What were you doing when the application crashed?
used the search-function in nautilus


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 219824128 vsize: 219824128 resident: 69165056 share: 48353280 rss: 69165056 rss_rlim: 4294967295
CPU usage: start_time: 1187241842 rtime: 24033 utime: 6430 stime: 17603 cutime:611 cstime: 65 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 -1208187168 (LWP 3419)]
[New Thread -1453061232 (LWP 6137)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 2 (Thread -1453061232 (LWP 6137))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strstr
    from /lib/libc.so.6
  • #5 ??
  • #6 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??


----------- .xsession-errors (1669 sec old) ---------------------
Executing reader on sql 'INSERT INTO photos (time, directory_path, name, description, default_version_id)        VALUES (958234407, '/home/webwurst/Bilder/Fotos/2000-05-13 Marens und Stefans Geburtsta
open uri = file:///home/webwurst/Bilder/Fotos/2000-05-13 Marens und Stefans Geburtstagsfeier/DCP_2377.JPG
Executing reader on sql 'UPDATE photos SET description = '',                       default_version_id = 1,                   time = 958234407               WHERE id = 170'
Executing reader on sql 'DELETE FROM photo_tags WHERE photo_id = 170'
Executing reader on sql 'DELETE FROM photo_versions WHERE photo_id = 170'
open uri = file:///home/webwurst/Bilder/Fotos/2000-05-13 Marens und Stefans Geburtstagsfeier/DCP_2378.JPG
Executing reader on sql 'INSERT INTO photos (time, directory_path, name, description, default_version_id)        VALUES (958234413, '/home/webwurst/Bilder/Fotos/2000-05-13 Marens und Stefans Geburtsta
open uri = file:///home/webwurst/Bilder/Fotos/2000-05-13 Marens und Stefans Geburtstagsfeier/DCP_2378.JPG
Executing reader on sql 'UPDATE photos SET description = '',                       default_version_id = 1,                   time = 958234413               WHERE id = 171'
Executing reader on sql 'DELETE FROM photo_tags WHERE photo_id = 171'
Executing reader on sql 'DELETE FROM photo_versions WHERE photo_id = 171'
open uri = file:///home/webwurst/Bilder/Fotos/2000-05-13 Marens und Stefans Geburtstagsfeier/DCP_2379.JPG
Executing reader on sql 'INSERT INTO photos (time, directory_path, name, description, default_version_id)        VALUES (958234421, '/home/webwurst/Bilder/Fotos/2000-05-13 Marens und Stefans Geburtsta
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-08-21 20:23:04 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 454799 ***