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 491081 - crash in Home Folder: Searching a file in my p...
crash in Home Folder: Searching a file in my p...
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-10-28 14:38 UTC by oge1d
Modified: 2007-10-28 22:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description oge1d 2007-10-28 14:38:36 UTC
What were you doing when the application crashed?
Searching a file in my personal folder


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 92663808 vsize: 92663808 resident: 34951168 share: 23941120 rss: 34951168 rss_rlim: 4294967295
CPU usage: start_time: 1193580097 rtime: 4878 utime: 4499 stime: 379 cutime:0 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208404256 (LWP 2850)]
[New Thread -1231922288 (LWP 3403)]
[New Thread -1274020976 (LWP 3103)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1231922288 (LWP 3403))

  • #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 ---------------------
(nautilus:2850): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:2850): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:2850): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:2850): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:2850): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:2850): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:2850): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:2850): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-28 22:02:56 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 ***